Oracle Fusion modules, pillar by pillar. And the metric that prices each line.

Oracle Fusion groups dozens of cloud modules into five pillars: ERP, HCM, SCM, CX and EPM. Each module is its own subscription line, and its metric, more than the module itself, decides what you pay.

What are the Oracle Fusion modules, pillar by pillar?

Oracle Fusion Applications group dozens of cloud modules into five pillars: ERP, HCM, SCM, CX and EPM. Each module is its own subscription line on your ordering document, with its own quantity and its own metric. Oracle sells and renews line by line, so the lines beneath a pillar matter far more than its name.

• ERP. Financials, Procurement (including Purchasing and Sourcing), Projects with Project Financials and Billing, and Risk Management.
• HCM. Global Human Resources as the base, with Talent, Payroll and Workforce Management layered on top.
• SCM. Inventory Management as the foundation, plus planning and logistics lines.
• CX. Sales, Service and Customer Data Management, with Marketing sold as separate products.
• EPM. Planning and Budgeting, sold through the EPM Standard and EPM Enterprise cloud services alongside the close, consolidation and reporting processes.

Why is EPM the pillar buyers forget?

Planning often runs as a separate finance project from the ERP selection, so EPM drops out of the first scope. It returns later as a change order, and Oracle prices it with no competing bid on the table. Viewer counts then climb every budget season, because the planning metric counts named users by role.

Price Planning and Budgeting in the first negotiation, even if you sign for it later, and write that rate into the order as a held price. Our EPM Cloud guide covers the services in each edition.

Where do the pillar boundaries hide scoping errors?

Most scoping errors sit at a pillar's edge, where a module looks included and is not, or where two metrics meet.

• SCM metrics. The pillar mixes user metrics and consumption metrics, so one quote can carry named user lines next to transaction volume bands. Errors cluster here, as our note on SCM metrics shows.
• SCM foundation. Inventory Management is the base almost every other SCM line assumes. Let your operating model decide which planning and logistics lines earn their own subscription, whatever the suite catalog offers. See the inventory and manufacturing dependencies.
• CX and Marketing. Eloqua and Unity are separate products with their own metrics. Confirm in writing whether each sits inside or outside the bundle before signature.
• ERP and Risk Management. Risk Management sells as a separate line. Most buyers assume it comes with Financials.

How is each Oracle Fusion module licensed?

Each Fusion module carries one of a few metric types. ERP and CX modules mostly count named users, HCM counts the whole workforce, and a specific set of ERP and SCM modules count transactions.

• Hosted Named User. Oracle defines this as an individual you authorize to access the service, whether or not that person is using it at any given time. A shared services clerk who logs in twice a year counts the same as a daily user. When Oracle measures usage, it counts active user accounts holding the privilege each module requires, so role assignments drive the number.
• Hosted Employee. All full time, part time and temporary employees, plus agents, contractors and consultants who have access to, use of, or are tracked by the programs. Oracle's measurement counts each person once a month, whatever the person type, and leaves out workers whose only person type is Retiree or Not Managed by HR. The size of your HR team plays no part. Our comparison of Hosted Named User versus Hosted Employee shows where each suits a buyer.
• Transaction volumes. Specific ERP and SCM modules are priced in volume bands. The bill rises when volume crosses into the next band, whatever your user count.

Which Oracle document defines what each module counts?

Oracle's metric descriptions document for Fusion offerings is the authoritative source. It lists which modules carry a separate line and exactly what each metric counts, and every scoping argument we have seen ends up back at it, whatever the sales deck said.

Check what a module contains in Oracle's documentation library before you accept the sales description, and save a dated copy of the definitions in force when you sign. The rules above the module list, from the term right to hosted versus active metrics and the renewal as the one point where terms change, are in our Fusion Cloud applications guide.

What do Oracle Fusion modules cost per user per month?

ERP modules list at a few hundred dollars per named user per month, and HCM modules at a combined rate per employee. The table gives the indicative list bands we use for a first budget. Treat them as orientation, since they are not a quote.

Oracle republishes its pricing, and the current Fusion Cloud Service Global Price List is dated September 10, 2026. Discounts of 40 to 70 percent are normal on enterprise deals. Your ordering document governs over any published figure, so the scoping method matters more than any band.

For ERP pricing in more depth, see the Cloud ERP pricing guide. The modules and add ons analysis works through base subscriptions against add on lines.

Worked example: what does a midsize ERP order cost?

Say you sign 200 Financials users, 80 Purchasing users and 30 Sourcing users. We use monthly rates inside the indicative bands and a 55 percent discount, which sits within the normal range.

What does an unused module cost over a subscription term?

If Sourcing is never activated, the order above pays $48,600 a year for it. Over a three year term that comes to $145,800 net, or $324,000 at list, for a module no one opens. Sourcing is the ERP line we most often find in that state.

Why is Oracle Fusion HCM so expensive?

Fusion HCM prices your whole workforce, whatever your HR team's usage. The Hosted Employee metric counts every employee, so the bill follows headcount. At a combined $40 per employee per month, 5,000 employees come to $2.4 million a year at list.

That figure is the same whether the 400 people in HR use the system every day or rarely. Spread across those 400 users, it works out to $6,000 each per year at list. Oracle's argument for the metric is that every worker is a record in the system and can use employee self service.

• Global Human Resources. The floor every other HCM module stands on, and the base of the combined per employee rate.
• Talent and Workforce Management. Priced on top of that floor, almost always per employee.
• Payroll. Oracle sells it as a separate service for each country, so it adds a line per legislative jurisdiction.

How do growth and acquisitions change the HCM bill?

Headcount growth raises the bill with no change in usage. Say the same company acquires a business with 1,200 employees and loads them into its Fusion HR records. The count rises to 6,200, and the annual list cost rises by $576,000 to $2,976,000.

Because the metric drives the cost, the definition is where the HCM negotiation happens. Our HCM Cloud licensing guide goes further, but three asks cover most of it:

• Who counts. Define the contractor and consultant populations in the order, and list the worker types excluded, so a vendor managed workforce that Fusion merely tracks is not counted by default.
• Acquisition timing. Ask for acquired employees to enter the count at the next renewal date.
• Payroll countries. License Payroll only for the jurisdictions you run in Fusion, and price the next country before you need it.

What have we seen in Oracle Fusion reviews in 2024 and 2025?

Across roughly 20 to 30 Oracle Fusion subscriptions Fredrik Filipsson reviewed in 2024 and 2025, the module list itself was never the problem. The subscription mapped to it was, in the same few ways each time.

• Modules bought and never switched on. In about half the reviews, modules from the original bundle had never been activated yet renewed at full rate every year. Sourcing in ERP and the planning add ons in SCM were the recurring examples.
• Separate pricing paid off. Buyers who priced each pillar separately against published module pricing, before Oracle's quote arrived, landed 10 to 20 percent lower on the bundle.
• No reduction right. Not one of the customers we reviewed held a written right to reduce quantities at renewal. Every one of them assumed they had it.

Our Oracle SaaS renewal briefing puts inactive modules at 18 to 32 percent of a typical bundle, which is why we settle scope before we discuss price. That figure counts modules inside a bundle, while the finding above counts customers.

Additions go through in a day. Reductions wait for renewal, and only if the order already allows them.

Why doesn't a mid term discovery save money straight away?

Fusion quantities only ratchet upward during a term. Reductions process at renewal, and only with a written right negotiated at the first order, so a customer that finds unactivated modules in month 8 of a 36 month term keeps paying for them for the remaining 28 months.

Why we advise against taking the full pillar bundle for its discount

The usual advice is to buy the whole pillar bundle, because Oracle's deepest discount sits there. We disagree, because in the reviews above the bundle is exactly where the never activated lines came from, and the headline discount applied to those idle lines as well.

Price each pillar and module separately against published pricing before the quote lands. Then sign only the lines you will run in the first year, with held prices for the rest, and fewer idle lines reach the renewal.

How do you find unused Fusion modules before renewal?

Run an activation audit: compare every subscription line on your ordering documents with what is enabled and used in the service. It is the fastest recovery available, because every never activated module is a line to cut and every under adopted one is a quantity to reduce.

Pull all five on the same day and file the extracts with the renewal papers. A role assignment does not prove use, and an enabled offering can sit idle for years, so treat transaction counts as the deciding evidence. Start with Sourcing and the SCM planning add ons.

What will Oracle's account team say, and how should you reply?

Four lines come up at most Fusion renewals. Each reply below keeps the discussion on your subscription lines and away from the headline discount.

• "The bundle price only holds if you take the full pillar." Ask for the per module prices behind the bundle in writing, then set them against your own separate pricing.
• "You can reduce quantities at renewal." Ask which clause of your order gives that right. If Oracle cannot point to one, ask for it to be added before you sign.
• "EPM can come later at the same discount." Ask for that discount and the per user rate to be written into this order as a held price for the full term.
• "Low adoption is a rollout issue, and our services team can help." An adoption plan does not change what you renew. Ask for the idle line to come off, or to be swapped for a module you will run.

Our notes on Fusion ERP negotiation and the Fusion SaaS renewal guide cover the sequence and timing around these conversations.

Which contract terms should you ask for in a Fusion order?

Ask for these terms at the first order, while Oracle still wants the signature. Once the order is signed, each one has to be traded for something else.

• A written reduction right. The right to reduce quantities or drop named modules at each renewal. Without it, the default paper works as a one way ratchet.
• A renewal cap. An escalator cap of 0 to 3 percent that survives the term, so it binds the renewal price as well as the first term.
• Held prices for additions. The same per unit rate for added quantities and for named future modules, EPM included, for the whole term.
• Definitions fixed at signature. A reference to the metric descriptions version in force when you sign, with any populations excluded from the Hosted Employee count listed by name.
• Swap rights. The right to exchange an unactivated module for another of equal value in the same pillar.

What to do next

1. Get the definitions. Pull the metric descriptions document for every subscribed module, and keep a dated copy of the version in force at signature.
2. Audit activation. Check every subscription line against enabled offerings, role holders and twelve months of transactions.
3. Price separately. Price each pillar against Oracle's published module pricing before any bundle quote arrives.
4. Scope EPM now. Put Planning and Budgeting into the first negotiation with a held rate, even if you sign for it later.
5. Write the protections in. Negotiate the reduction right, the escalator cap and held prices at the first order.
6. Get support. Our Oracle practice runs the scoping and the renewal negotiation with you.

Frequently asked questions