How we counted
Oracle publishes a What's New book for each product area every quarter. For 26C, the SCM side spans six books: Procurement, Inventory Management (which includes Costing and Logistics), Manufacturing, Maintenance, Demand Management and Order Management. Each book lists every feature with two classifications that most readers skip: an enablement column (what you must do before the feature does anything) and a scale column (how big the change is). We read all six books, all 189 features, across 32 sub-modules, and classified every one.
One honest note before the findings: these numbers cover SCM only. Financials, HCM and CX have their own books, so the true size of a full 26C update on your instance is larger than anything below. And as always, verify behavior in your own test instance; your configuration changes what you will see.
Finding one: 59 features arrive switched on
The enablement column is the closest thing Oracle gives you to a risk rating, and here is how 26C SCM splits:
| Enablement | Features | What it means for you |
|---|---|---|
| None (delivered enabled) | 59 | Live the day your instance updates. Users see these without warning |
| Setup required | 79 | Dormant until someone configures them. Safe, but also easy to forget the value they carry |
| Potential setup | 20 | Works out of the box, behaves differently once configured |
| Opt-in | 27 | Nothing happens unless you switch it on. Your schedule, your choice |
| REST API / Visual Builder | 4 | Developer-facing surface, invisible to end users |
Six of the 59 auto-enabled items are bug-fix bundles, which still leaves 53 functional changes that turn themselves on. That is the number quarterly-update planning should start from, because it defines what your users will notice on the Monday after the update weekend. The features most teams debate, the opt-ins, are actually the smallest slice of the wave at 14 percent.
This is why "we skipped the release notes this quarter" is a decision you make on your users' behalf without telling them. If you want the 59 in one filtered view, the 26C Briefing Deck lets you filter by enablement and mark each card read or priority.
Finding two: half of 26C is Redwood
93 of the 189 features carry the Redwood label. Read that again: the Redwood user experience is not a future migration project sitting in a slide deck. It is arriving now, screen by screen, one quarterly wave at a time, and in 26C it is 49 percent of everything Oracle shipped for SCM.
The pattern inside those 93 features is consistent: existing pages rebuilt as Redwood pages, sometimes with the classic page still available, sometimes not. Every one of those swaps silently invalidates a little of your training material, your screenshots and your users' muscle memory. Teams that treat Redwood as one big future cutover are absorbing it unplanned, a dozen screens per quarter.
If Redwood is landing on your desk, walk the Redwood survival route: personalization inventory, task-based testing, training waves, in that order.
Finding three: AI is now one feature in seven
27 of the 189 features are AI features. Two of them are also among the eight largest changes in the entire wave: the Negotiation Surrogate Response Assistant in Sourcing, an agent that drafts supplier responses on behalf of suppliers who reply outside the system, and the Order Exception Assistant enhancements in Order Management.
The signal for consultants is clear. AI stopped being a keynote topic and became a line item in the enablement column, with the same setup, testing and governance questions as any other feature. The client question is no longer "should we look at AI" but "which of these 27 do we switch on, and how do we test an agent." If that question is coming your way, start in the AI Agents wing, where the decision patterns live.
Where the wave lands, book by book
| What's New book | Features | Share of wave |
|---|---|---|
| Order Management | 43 | 23% |
| Procurement | 42 | 22% |
| Inventory, Costing & Logistics | 41 | 22% |
| Manufacturing | 30 | 16% |
| Demand Management | 18 | 10% |
| Maintenance | 15 | 8% |
Order Management, Procurement and Inventory carry two thirds of the wave between them. If your role lives in one of these areas, the module home pages collect the release view together with the flows and fixes for your desk: Procurement, Inventory, Cost Management.
The eight features that are projects, not checkboxes
Oracle marks scale for each feature, and only eight of the 189 are tagged as larger-scale changes. These are the ones that deserve a named owner and a test plan rather than a glance:
| Area | Feature |
|---|---|
| Sourcing | AI Agent: Negotiation Surrogate Response Assistant |
| Manufacturing | Separate operation to track rework in discrete work orders (Redwood) |
| Manufacturing | Kanban planning for just-in-time material replenishment |
| Maintenance | Clock in and clock out of work order operations |
| Maintenance | Create and manage follow-up work orders (Redwood) |
| Maintenance | Edit work orders from My Maintenance Work (Redwood) |
| Order Management | Manage order promising demands from external source systems (Redwood) |
| Order Management | AI Agent: Order Exception Assistant enhancements |
Note what this list is made of: three Maintenance features (a fifth of that small book is large-scale change, the highest density of any area), two AI agents, and Redwood everywhere. The themes of the wave in miniature.
What a sane 26C review looks like
You do not need to read 189 features. You need a triage order:
| Step | Do this | Why |
|---|---|---|
| 1 | Review the 59 delivered-enabled features for your modules | Your users meet these first, prepared or not |
| 2 | Regression-test your critical flows in the test environment during the preview window | Auto-enabled changes are where update-weekend surprises come from |
| 3 | Put the 27 opt-ins on your own roadmap | They wait for you. Evaluate them when it suits the business, not the calendar |
| 4 | Treat the 8 larger-scale features as mini projects | Owner, test plan, training, rollout date |
We built the whole chain for exactly this: the Briefing Deck to triage all 189 cards by module and enablement, the 26C Gauntlet to test whether your setup survives the wave in eleven questions, and the Test Kit with executable cases, preconditions, steps and expected results, ready to track pass and fail. Start at Release HQ.
Questions we keep hearing
How many features are in Oracle Fusion 26C for SCM?
189, across six What's New books and 32 sub-modules, per Oracle's official readiness documents. Financials and HCM are counted separately in their own books.
Do quarterly updates really enable features automatically?
Yes. In this wave, 59 features list no enablement action, which means they arrive on. That is the part of the update you cannot defer, which is why it should be reviewed first.
Is Redwood optional in 26C?
Feature by feature, sometimes. As a direction, no. When half a wave carries the Redwood label, the practical question becomes pacing your adoption, not avoiding it.
Where do these numbers come from?
From Oracle's public 26C What's New documents on docs.oracle.com, read and classified by us in July 2026. Counts can shift slightly as Oracle revises documents during the quarter, so treat the shape as stable and the exact digits as a snapshot. And always confirm behavior in your own instance.