The Fusion module list, and the metric behind every line
Oracle Fusion Applications group dozens of cloud modules into five buyer facing pillars, ERP, HCM, SCM, CX, and EPM, each module its own subscription line with its own quantity and metric. Knowing which module sits where is the first step; knowing the metric behind each one, what it costs for a year, and which modules typically go unused is what turns the list into a budget you can defend, and across our reviews the module list was never the problem. The subscription mapped to it was.
Prepared by Redress Compliance · August 8, 2026 · Oracle advisory. Based on 20 to 30 Oracle Fusion estate reviews run 2024 to 2025.
Executive summary
Five pillars, not four, and the forgotten one arrives as a change order. ERP, HCM, SCM, CX, and EPM: EPM is the pillar buyers forget to scope, and it arrives later as a change order priced without competition.
The metric decides the bill rather than the module, ERP and CX counting named users, HCM counting the whole workforce, and a specific set of ERP and SCM modules counting transactions, and the authoritative statement of what each module counts is Oracle's metric descriptions document.
Not the sales deck, which is where every scoping argument eventually lands.
The HCM arithmetic is brutal because it prices payroll, not usage. 5,000 employees on a combined $40 per employee per month runs to $2.4 million a year at list, driven by headcount rather than the 400 people in HR: Global Human Resources is the floor everything stands on, with Talent.
Payroll per legislative jurisdiction, and Workforce Management pricing on top, almost always per employee.
Growth and acquisitions raise the bill with no link to usage at all, the same Hosted Employee mechanics that make the metric the negotiation and the definition the leverage.
Half the estates paid full rate for modules never activated.
In about half the Fusion estates we reviewed, modules bought in the original bundle were never activated.
Yet renewed at full rate every year, with Sourcing the recurring example in ERP and the planning add ons in SCM: the activation audit against the subscription lines is the fastest recovery in the estate.
The pricing discipline compounds it, because buyers who priced each pillar separately against published module pricing before the quote landed 10 to 20 percent lower on the bundle, and discounts of 40 to 70 percent are normal on enterprise deals.
The ratchet and the missing reduction right complete the pattern. Quantities add mid term in a day and reduce only at renewal, only with a written reduction right negotiated at the first order, and not one estate we reviewed held one, while every one of them assumed they did.
The scoping method that defends the budget: the module view over the pillar view, each line priced against its indicative band, Financials at $400 to $650 per user per month, Purchasing at $350 to $550, Sourcing at $200 to $400 and often unused, with the documentation library.
Not the sales description, verifying what each module actually contains.
The five pillars, and where each bill grows
| Pillar | Core module | Typical metric | What makes the bill grow |
|---|---|---|---|
| ERP | Financials | Hosted Named User | Prerequisite modules and user creep in shared services |
| HCM | Global Human Resources | Hosted Employee | Headcount and acquisitions, with no link to usage |
| SCM | Inventory Management | Hosted Named User or consumption | Planning add ons and transaction volume bands |
| CX | Sales | Hosted Named User | Marketing priced apart, and service seat growth |
| EPM | Planning and Budgeting | Hosted Named User, role based | Viewer counts in budget season, and extra services |
The boundaries hide the scoping errors.
SCM mixes user metrics and consumption metrics inside one pillar, which is where the errors cluster; CX's boundary is Marketing, since Eloqua and Unity are separate products with their own metrics, confirmed inside or outside the bundle before signature.
And ERP's Risk Management sells as a separate line most buyers assume is included.
Inventory Management is the SCM foundation almost everything else assumes, and the operating model, not the suite catalog, decides which planning and logistics lines deserve their own subscription.
The module view, with indicative bands
| Module | Metric | Indicative list band | Goes unused? |
|---|---|---|---|
| Financials | Hosted Named User | $400 to $650 per user per month | Rarely |
| Purchasing | Hosted Named User | $350 to $550 per user per month | Rarely |
| Sourcing | Hosted Named User | $200 to $400 per user per month | Often |
| Project Financials and Billing | Hosted Named User | Priced per project role | Sometimes |
| Global Human Resources | Hosted Employee | Part of the combined per employee rate | Rarely |
| Talent, Payroll, Workforce Management | Hosted Employee, per jurisdiction for Payroll | Stacked on the GHR floor | By module |
The Oracle Fusion SaaS brief
The pillar map, the metric definitions, the module scoping method, and the renewal calendar worked on a representative estate.
Get the white paper →The scoping method, metric document first
The bands are orientation for a first budget, not a quote: Oracle republishes its pricing, 40 to 70 percent discounts are normal on enterprise deals, and your ordering document governs over any published figure, which makes the method matter more than the numbers.
Scope from the metric descriptions document, the authoritative list of what carries a separate line and what each metric counts; verify module contents in the documentation library before accepting the sales description.
Price each pillar separately against published module pricing before the bundle quote arrives, the discipline that landed 10 to 20 percent lower; and negotiate the written reduction right at the first order, because the ratchet only loosens where the paper says so.
The subscription mechanics above the module list, the term right, the hosted against active metrics, and the renewal as the only leverage moment, run in the Fusion Cloud applications guide, the ERP pricing depth in the Cloud ERP pricing guide.
And the base against add on arithmetic in the modules and add ons analysis.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across Fusion reviews, 2024 to 2025
Across roughly 20 to 30 Oracle Fusion estates Fredrik Filipsson reviewed in 2024 and 2025, the module list itself was never the problem. The subscription mapped to it was:
Bought in the original bundle, never turned on, renewed at full rate every year.
Landed by buyers who priced each pillar against published module pricing first.
The reduction right finding repeats from every Fusion review because the assumption is universal and the paper never supports it: additions process in a day, reductions process only at renewal with a negotiated right.
And the estate that discovers its unactivated modules mid term holds that discovery until the anniversary.
The activation audit therefore runs before renewal preparation, module by module against the subscription lines, because every never activated module is a line to cut, every under adopted one a quantity to reduce.
And the renewal that arrives with that audit done negotiates the bundle instead of renewing it.
Your first five moves
- Pull the metric descriptions document for every subscribed module, the authoritative statement the sales deck is not.
- Audit activation against the subscription lines, where half the estates found modules renewing unused at full rate.
- Price each pillar separately before any bundle quote, the 10 to 20 percent discipline.
- Scope EPM at the start, because the forgotten pillar arrives later as an uncompetitive change order.
- Negotiate the written reduction right at the first order, the term no estate held and all assumed. The Oracle practice runs the scoping with you.
Frequently asked questions
What are the Oracle Fusion pillars?
Five: ERP with Financials, Procurement, Projects, and Risk Management; HCM with Global Human Resources, Talent, Payroll, and Workforce Management; SCM with Inventory as the foundation plus planning and logistics lines; CX with Sales, Service, and Customer Data Management.
And EPM with Planning and Budgeting.
EPM is the one buyers forget to scope, and it returns later as a change order.
How are Oracle Fusion modules priced?
Each module is its own subscription line with its own metric and quantity: ERP and CX modules mostly on Hosted Named Users, indicative bands like Financials at $400 to $650 per user per month, HCM on Hosted Employees across the workforce, and specific ERP and SCM modules on transaction volumes.
Discounts of 40 to 70 percent are normal on enterprise deals, and the ordering document governs over any published figure.
Why is Oracle Fusion HCM so expensive?
Because it prices payroll, not usage: the Hosted Employee metric counts the whole workforce, so 5,000 employees on a combined $40 per employee per month run to $2.4 million a year at list, driven by headcount rather than the 400 people in HR.
Growth and acquisitions raise the bill automatically, with Payroll typically a separate line per legislative jurisdiction stacking on the Global HR floor.
Which Fusion modules go unused?
In about half the estates we reviewed, modules bought in the original bundle were never activated yet renewed at full rate every year, with Sourcing the recurring ERP example and the planning add ons the SCM one.
The activation audit against subscription lines is the fastest recovery available, run before renewal so the unused lines are cut rather than renewed.
Can you reduce Oracle Fusion module quantities?
Only at renewal, and only with a written reduction right negotiated at the first order: additions process mid term in a day, and not one estate we reviewed held the reduction right, though every one assumed it did.
The right gets drafted explicitly at signature, because the default paper is a one way ratchet and the anniversary is the only date it can move.
What document defines Oracle Fusion metrics?
Oracle's metric descriptions document for Fusion offerings, the authoritative list of which modules carry separate lines and exactly what each metric counts, with the documentation library verifying what a module actually contains.
Scoping from those sources rather than the sales deck, and pricing each pillar separately before the bundle quote, landed buyers 10 to 20 percent lower in our reviews.
