Accenture issued this one, not Oracle

Accenture announced that Combe Inc. has unified its global operations on Oracle Fusion Applications. The release went out over Business Wire on September 28, 2026 at 07:59 Eastern with no byline, and it credits Accenture Edge with the work. Oracle supplies only the supporting quote, which makes this a services reference.

A sourcing note before any of this reaches a slide. The primary Business Wire page returns an access error to automated retrieval, so our facts come from a syndication carrying the same wire copy rather than from the original posting. Nothing below goes past what that copy states.

What it states is narrow. Combe consolidated country-specific legacy systems onto Oracle Fusion Cloud ERP and uses Oracle Fusion Cloud SCM for demand and supply planning. Two people besides the Oracle spokesperson are quoted in the release, but their comments came back truncated on our later retrieval passes and one job title never appeared in the readable body, so we are not quoting either. Background on the suite sits on the Oracle Fusion Cloud hub.

The customer profile is the recognisable part

Combe is family-owned, founded in 1949 and now run by its third generation. Its brands include Just For Men, Vagisil, Astroglide and Virtue. For an architect, that profile carries more information than the product names do, because it explains how the estate got the shape it had.

Seventy-odd years of growth across borders usually produces country-level autonomy in systems. A subsidiary bought a local accounting package because it handled local tax filing. Another kept whatever the distributor it acquired already ran. Each choice was defensible on the day, and none was made with a group data model in mind.

The pressure to consolidate arrives from the group rather than from the countries. Someone at head office asks for one stock cover number across brands, or one gross margin by category, and the answer takes a fortnight and a spreadsheet nobody else can rebuild. That is the same pattern behind a move from thirty-five systems down to one, and it is the moment the programme gets funded.

Finance and planning on one data model

The combination named in the release is the part with architectural weight. Finance on Fusion Cloud ERP and demand and supply planning on Fusion Cloud SCM means the planning engine and the ledger draw on the same item master, the same organisation structure and the same cost data. Reconciling a separate planning system against a general ledger is work that otherwise runs every period, forever.

The hard part of a consolidation of this kind sits underneath that. Somebody had to square local statutory requirements with one global model. Chart of accounts, tax determination, electronic invoicing formats, inventory valuation rules and statutory reporting all differ by country, and each one is a candidate for a local exception that quietly restores the divergence the programme was funded to remove.

The suite choice is the easy decision by comparison. Which vendor wins matters far less than who is allowed to refuse a country's request for a local variant. If you are early in the same argument, an ERP master data governance starter will do more for you than another product comparison, and what Oracle Fusion Cloud actually is covers the scope of the suite itself.

What the release leaves out

There is no go-live date. There is no phase description, no count of the countries involved and no statement that the programme has finished. A reader cannot tell whether finance went live last quarter with planning still in design, or whether the whole estate has been running on Fusion for a year.

There is also no measured outcome of any kind. No close time, no forecast accuracy, no service level, no cost. Customer references usually carry at least one number, however carefully chosen, and this one carries none. Take it as evidence that the deal happened, and nothing firmer.

Natalia Rachelson, Senior Vice President of Applications Development at Oracle, says that "by bringing finance and supply chain processes and data together on Oracle Fusion Applications, a single system of record, Combe can use embedded AI and Fusion Agentic Applications to help its teams automate more of the work required to respond and rethink its operating model." Read the tense. Combe can use those capabilities. The sentence attaches agentic features to the deployment as a future option, and reports nothing Combe has done with them.

The question to put to your own sponsor

A consolidation story with no dates and no numbers still tells you something. It tells you the pattern is survivable, and that a family group with decades of local autonomy can land finance and planning on one foundation. It tells you nothing about the cost, the duration, or what broke on the way.

Set it next to a sixteen-country cutover that went live on a single date, which at least discloses the scope and the cutover approach. Those two facts are the difference between a story you can argue from and one you can only cite.

So take one question into the first workshop of your own programme. Which country's statutory requirements did the global template get built from, which countries hold a standing exception to it today, and who signs off the next exception after go-live. A team that cannot answer all three is still assuming the single model rather than designing it.