Oracle Fusion Cloud and Redwood

Oracle Fusion Cloud modules that almost no one uses to their full potential

Oracle Fusion Cloud almost always includes more functionality than gets turned on. Which modules are most often underused and how to tell if that is you.

· 5 min read

A company that already has Oracle Fusion Cloud rarely asks “what are we missing?” It asks why the system feels more expensive than it should, or why certain reports are still built in spreadsheets despite having an ERP that, in theory, already handles them.

The answer usually lies in the licensing, not the system: the company bought more than it turned on, and no one revisited that gap after launch.

This is a different article from the ones that explain what Oracle Fusion Cloud is or who it is for. It is written for those who already have it running and want to know whether they are getting the value they are already paying for, not for those still evaluating whether to buy it.

Why Oracle Fusion Cloud always includes more than gets turned on

Implementations are planned to go live with the essentials working: closing the month, paying and collecting, keeping inventory under control. Everything else is left for “a second phase” that, in practice, almost never arrives, because the project team has already left and the internal team has day-to-day operations on its plate.

The result is a system that is paid for in full month after month but used at a fraction of its capacity. It is not a product flaw: it is what you would expect when no one goes back to review what was left half done, especially if the partner that did the implementation is no longer involved in day-to-day operations.

On top of that, Oracle releases new features within these modules in every quarterly update. A company that went live three or four years ago has, without knowing it, more recent functionality available under the same license that was never turned on because no one went back to look at what each update brought.

Four frequently underused modules

They show up more often than you would expect at companies that have been running Oracle Fusion Cloud for some time.

  • Procurement beyond the basic purchase order: sourcing, contract management and supplier evaluation are almost always licensed, but are used only to generate the purchase order, without the rest of the flow.
  • Project Management outside the formal projects area: project cost control and billing that other departments could use, not just the one that manages construction or implementations.
  • Custom-configured Financials reports and dashboards, when the team keeps exporting to spreadsheets to build the same numbers every month.
  • Inventory planning beyond fixed minimums and maximums: safety stock by days of coverage or statistical, and minimums and maximums that recalculate on their own.

In all three cases the pattern repeats: the functionality exists, it is paid for, and no one configured it after launch because there was no urgent reason to. The list is not exhaustive; it changes depending on which modules each company has licensed. But the pattern behind it almost always repeats: what was configured for launch stays, and what was planned for “later” is rarely picked up unless someone puts it back on the table.

How to know what your company is paying for and not using

The most direct way is to compare two lists: the modules and features included in your licensing contract, and those your team actually uses every day. The difference between the two is exactly what you are paying for without benefiting from it.

That comparison is almost never done by one person, because the contract was signed by someone in finance or procurement, and day-to-day use is known by the operations team. Bringing both views together, even in a single meeting, is usually enough to see the gap clearly.

It is the same exercise that was done at Cenmex, which had Oracle Fusion Cloud since 2019 with its supply chain not aligned to its real operation, to the point of using the system almost as a database and considering dropping it altogether. Instead of reimplementing, the team reviewed which already-paid functionality was not being used, identified the gaps against Oracle's standard, and prioritized what to configure first. The company ended up renewing licenses and remediating the flow across all its plants, without needing a new implementation project.

The cost of not turning them on versus the cost of a review

Not turning on what you already pay for has a cost that is almost never counted: team hours spent building by hand what the system could automate, decisions made with reports that take days to reconcile, and a license that grows in price every year without usage growing with it.

A utilization review is cheaper and faster than any reimplementation project, because it does not touch what already works: it only turns on what is already paid for, prioritized by impact.

It is worth comparing the two paths honestly. Reimplementing means redefining processes, migrating data and training users, with the risk of reproducing in the new system the same gaps the old one had. Reviewing utilization starts from what already works and fills in only what is missing, with a scope you can measure before starting.

Where to start

By putting your licensing contract next to what your team configures and uses today. If the gap is noticeable, that is the first place to look for value, before thinking about any new project.

Tell us which modules your company has licensed, which of them are barely touched, and which reports are still built by hand outside the system.

Facing something similar?

Tell us which system you run and what it can't do for you today. The first conversation is about understanding your situation.

Request an assessment
Cover of the CETERiS guide From Excel to ERP (in Spanish)

Free guide · 24 pages · In Spanish

From Excel to ERP: how to tell if it's time

What we'd tell you in a first assessment meeting, in writing: how to know whether you need an ERP, what it costs in estimated ranges and how to migrate without disrupting operations. Currently available in Spanish; English edition coming soon.

  • The 7 signs you've outgrown spreadsheets
  • What an ERP costs and what drives the price
  • The 5 most expensive mistakes
  • A checklist to decide whether it's time
Download the guide (Spanish)Free. Delivered to your inbox.