SAP Fiori Licensing Explained: What's Included in S/4HANA and What Costs Extra

SAP Fiori is not just a UI framework — it is a licensing layer that enterprises consistently misunderstand. When SAP introduced Fiori as the standard user experience for S/4HANA, it bundled certain Fiori apps within the existing named user licence structure. But not all Fiori apps are bundled. Some require separate entitlements. Some require specific user types. And some trigger additional charges that were not visible in the original S/4HANA licence negotiation. For enterprises mid-way through their S/4HANA migration or already running on RISE with SAP, understanding what is — and is not — included in the SAP Fiori licensing model is directly relevant to your compliance position and your renewal negotiation.

This article explains exactly how SAP licences Fiori access, which apps are free with your existing S/4HANA entitlement, which cost extra, and how to protect yourself commercially before your next contract renewal.

SAP Fiori is the browser-based UX framework that serves as the primary interface for S/4HANA. It replaced the legacy SAP GUI for most standard business transactions and introduced a tile-based, role-driven launchpad that surfaces relevant apps based on a user's function and authorisation profile. The licensing question — frequently misunderstood — is not about the Fiori technology itself, but about the applications that Fiori surfaces and the infrastructure required to run them.

The core principle is this: Fiori access rights follow the underlying licence entitlement of the application being accessed. If a user is a Professional licence holder who has the right to access an S/4HANA Purchase Order transaction, they can access it via Fiori just as they could via SAP GUI. The Fiori interface does not add a licence cost for embedded S/4HANA apps — the cost was already embedded in the user type.

The Embedded vs Extended App Distinction

Where the licensing model becomes more complex is the distinction between embedded Fiori apps (those running natively on the S/4HANA server) and extended Fiori apps (those hosted on SAP BTP). SAP's product development over the past four years has moved an increasing number of new Fiori applications from the embedded model to BTP-hosted deployments. This means that accessing a new generation of Fiori apps may require active BTP service entitlements — specifically the SAP Launchpad Service or, in the newer commercial model, SAP Work Zone. Neither of these is automatically included in a standard S/4HANA licence.

All standard SAP Fiori apps that are delivered as part of the S/4HANA application server are included in the named user licence for S/4HANA. This covers the core transactional Fiori apps — purchasing, finance, HR self-service tiles that map to existing S/4HANA modules — as long as the user accessing them holds the appropriate named user type for the underlying business function.

There is no separate Fiori licence fee for using the Fiori Launchpad as a technology. The launchpad is a component of the S/4HANA deployment. Running FIORI_CLIENT authorisations on a user does not itself generate a licence cost. The cost is determined by what the user does through Fiori — the business transactions they execute.

The "Included" Trap: Scope Creep Between Releases

A practical problem arises between S/4HANA release cycles. Apps that were embedded in earlier S/4HANA releases sometimes move to BTP-hosted versions in later support packages. An enterprise running S/4HANA 2021 may have all their Fiori apps embedded and licence-included. When they upgrade to S/4HANA 2023 or 2024, some of those apps may have been rearchitected as BTP-hosted services — requiring BTP entitlements that were not part of the original commercial agreement. SAP does not always proactively flag this change, and discovery tends to happen at audit or upgrade time.

The following Fiori scenarios consistently generate additional licence costs that enterprises are surprised to discover:

SAP Business Technology Platform has become the preferred deployment platform for new Fiori application development. This architectural shift — driven by SAP's cloud strategy — means that custom Fiori apps built by customers or partners, as well as an increasing number of standard SAP Fiori apps, are running on BTP infrastructure rather than directly on the S/4HANA application server.

The Consumption Model Problem

BTP uses a consumption-based credit model. Enterprises receive a block of BTP credits as part of their RISE with SAP bundle or as a standalone BTP subscription, and those credits are consumed by the BTP services they use. SAP Launchpad Service — the BTP service that hosts the Fiori Launchpad for BTP-hosted apps — consumes these credits at a rate determined by the number of active users and the frequency of access.

The problem is that 70% of enterprises with BTP entitlements don't have clear visibility into which of their Fiori apps are consuming BTP credits and at what rate. When those credits run out, SAP flags a consumption gap — which either results in an additional purchase or, if discovered during an audit, a back-licence claim. Our detailed guide to SAP BTP licensing covers this consumption model in depth.

Custom Fiori Apps and Digital Access

Custom Fiori apps deserve special attention. Any custom app built on BTP — regardless of whether it uses the Fiori UX — that interacts with S/4HANA via OData or BAPI calls to create business documents is subject to SAP's Digital Access licensing model. The nine document types that trigger Digital Access charges (Delivery Order, Transfer Order, Production Order, Purchase Order, Sales Order, Invoice, Service Order, Goods Movement, and Billing Document) are highly relevant to custom Fiori development. Every integration that creates these documents via API rather than named user interaction needs to be assessed against your Digital Access entitlement. See our guide to SAP Digital Access licensing for full details.

One of the most common misconceptions we encounter is the assumption that SAP Work Zone — SAP's digital workplace product for building employee portals and intelligent intranets — is simply "a better version of the Fiori Launchpad" and therefore included in the S/4HANA licence.

It is not. SAP Work Zone is a separately priced subscription product, licensed on a per-user basis. It is built on BTP, uses the Launchpad Service as a foundation, and can surface Fiori tiles — but it also includes additional capabilities around process integration, third-party app cards, Microsoft Teams integration, and workflow orchestration. Those additional capabilities are what SAP is charging for.

For most enterprises whose Fiori need is simply a clean, browser-based interface to S/4HANA transactions, the standard embedded Fiori Launchpad is sufficient. Work Zone becomes relevant only when you are building a genuinely integrated digital workplace that goes beyond S/4HANA. If a SAP sales rep is proposing Work Zone as part of your S/4HANA journey without a specific business case, treat it as commercial upselling, not a technical requirement.

Not all S/4HANA user types carry the same Fiori access rights. Understanding which Fiori apps each named user type is permitted to access is fundamental to ensuring your licence entitlement matches your deployment reality.

• Professional (Pxx): Full access to all Fiori apps within the licensed application scope. Can execute transactional Fiori apps, analytical apps, and process flows. The most expensive and most capable user type.
• Limited Professional (Lxx): Access restricted to a pre-defined set of business processes. Fiori apps outside the Limited Professional scope require a Professional licence upgrade. Significant licence savings are available for users who genuinely only perform limited business functions.
• Employee (ESS): Access to Employee Self-Service Fiori apps — leave requests, timesheets, personal data. Cannot access operational or analytical S/4HANA transactions. This is a significant optimisation opportunity: users currently holding Professional licences solely for ESS access can often be reclassified to the cheaper Employee type.
• Developer: Required for any user building, testing, or configuring Fiori apps — not for business users accessing completed apps. Common miscategorisation involves giving functional consultants who "test Fiori" a Developer licence when they should hold a Professional licence.

The reclassification opportunity around Employee Self-Service Fiori apps is one of the most consistently overlooked quick wins in SAP licence optimisation. We routinely find that 10-15% of an enterprise's Professional licence population genuinely only performs ESS activities and can be reclassified with no operational impact. For large organisations, this can represent hundreds of thousands of euros in annual savings. For a detailed breakdown of all SAP user types, see our guide to SAP named user types.

Every S/4HANA renewal or new contract should address the Fiori licensing model explicitly. The following are non-negotiable asks that any competent SAP licensing adviser should be putting on the table:

• Written confirmation of embedded Fiori app scope: A schedule listing which Fiori apps are covered by your named user licences, and what happens if SAP reclassifies embedded apps to BTP-hosted in future releases.
• BTP credit allocation for Fiori Launchpad Service: If any of your Fiori apps currently or prospectively require the BTP Launchpad Service, you need a defined credit allocation that covers your user population without additional purchase.
• Work Zone free tier or exclusion: If SAP is proposing Work Zone as part of a bundled RISE or S/4HANA package, negotiate a defined scope for Work Zone use and a free tier that covers basic Fiori Launchpad access for existing user populations.
• Digital Access exclusion for internal custom apps: Custom Fiori apps built for internal use — where all users are named users already licensed in the system — should be carved out of the Digital Access measurement scope in your contract.

These are protections that SAP does not include by default. They must be negotiated. If you are approaching an S/4HANA renewal without independent SAP licensing advice, you are negotiating with one side's playbook — SAP's. Read our SAP contract negotiation guide for a comprehensive framework for enterprise buyers.