o9 vs OMP vs SAP IBP — the buyer's guide the vendors won't write

There is a comparison that gets written every quarter and is wrong every time. It lines the three platforms up in a feature matrix, scores each row, sums the columns, and declares a winner. No serious buyer should trust that table, because the feature matrix is the part of the decision that matters least.

All three are Leaders in the current (2025) Gartner Magic Quadrant. All three can run an enterprise planning process end to end. The question is almost never "which one has demand sensing" — they all claim it. The question is which one fits your ERP backbone, your industry's planning physics, your data maturity, and the amount of config-and-consultant weight your organisation can actually absorb. Get those four right and the platform very nearly picks itself.

This is a different comparison from the SAP IBP / o9 / Kinaxis one, and deliberately so. Kinaxis belongs in the conversation when concurrent planning — propagating a change across demand, supply, and finance simultaneously — is your differentiator. OMP belongs in this one because it solves a different problem: hard, finite-capacity scheduling for process manufacturers. If your planning problem is a chemicals plant or a paper line rather than a fast-cycle distribution network, OMP is the name the Kinaxis comparison leaves out.

The verdict, up front

Choose SAP IBP if you are on (or committed to) S/4HANA and you value one coherent data spine from plan to execution more than you value best-of-breed optimisation.

Choose OMP (Unison) if you are a process or CPG manufacturer where finite-capacity scheduling and hard production constraints are the planning problem.

Choose o9 if you are multi-ERP and heterogeneous, and you want an ERP-agnostic planning brain layered above execution, with rapid scenario modelling across commercial and operational teams.

Everything below is the evidence and the gotchas behind those three sentences.

The three platforms, without the brochure

SAP IBP is the execution-coupled incumbent — the successor to APO, re-platformed onto HANA's in-memory database and sold as separate modules: Demand, Inventory, Response & Supply, S&OP, Control Tower, Demand-Driven Replenishment. Its real advantage is plumbing. When your ERP is S/4HANA and your master data already lives in SAP, the integration argument is genuine and the data flows near-real-time into procurement, production, and fulfilment. The honest read is that IBP most often wins as the path of least resistance for SAP houses — not because it out-plans the other two. Coherence has real value, and that is a legitimate reason to buy. Just name it for what it is rather than dressing it up as optimisation superiority.

OMP (Unison Planning) is the process-industry specialist, and the narrowest of the three by deliberate design. Its operations-research roots go back to 1985, and — unusually — it evolved from OMP Plus into Unison Planning without fragmenting through acquisitions. That coherence is a real architectural strength: one common planning model across horizons and roles, rather than a stitched-together suite. In chemicals, life sciences, metals, paper and film, packaging, tyres, and building products, OMP goes deeper on the planning physics — finite scheduling, hard constraints — than either competitor. Outside those industries, the fit thins out fast, and that is the trade you are accepting.

o9 Solutions is the AI-first "Digital Brain" challenger, built on a graph data model — the Enterprise Knowledge Graph — that sits above execution systems and is ERP-agnostic. It is the most architecturally modern of the three, and the independent reviewer least friendly to any of them still calls o9 "plainly more serious than most AI-flavored planning vendors." The asterisk: that same reviewer notes o9 behaves "like a large suite company that markets ahead of what it publicly explains." Believe the data model. Discount the agentic-AI sizzle until you have watched it work in your configuration, not the demo tenant. One more signal worth reading correctly — o9 dropped to Visionary in the 2024 Gartner Magic Quadrant and returned to Leader in 2025. That round trip is a reminder not to over-index on any single year's dot.

Figure

Where each one is genuinely strong — and genuinely weak

No platform is good at everything, and the demo will not volunteer the gaps. Here they are.

SAP IBP. Strong on finance-integrated S&OP, governance templates, and tight linkage into S/4HANA execution. Weak in three places practitioners feel daily. First, Excel is the interface for the overwhelming majority of a planner's time, and the add-in is occasionally slow or unstable; master-data management has poor UX, with dozens of master-data objects per domain and consistency errors that often surface only after you save, as an error file rather than inline validation. Second, disaggregation and what-if are weaker than they were in APO — a regression long-time users notice. Third, performance degrades and infrastructure cost climbs once data exceeds memory. SAP's answer to the Excel problem, Planner Workspaces, is promising, but adoption is still evolving — do not assume it is the lived reality on a given 2026 deployment.

OMP (Unison). Strong where it counts for process industry: the deepest finite-capacity scheduling and constraint handling of the three. The weaknesses are interface friction (multiple screens to assemble a full picture; reviewers consistently say the UI takes real time to learn), a limited managerial / planning-leadership view, and several features — RDD forecasting, demand sensing, exception-based planning — that users flag as not yet fully mature. Early implementations have also drawn complaints about communication gaps between business and tool terminology. And the narrowness cuts both ways: outside process and CPG, the case gets harder to make.

o9. Best-in-class scenario modelling and what-if — this is the most consistently praised capability across the three, and the right reason to shortlist it. The recurring complaints are implementation complexity and a shortage of certified talent (the number-one issue in reviews), cost that buyers describe as prohibitive for smaller organisations, glitches with slow resolution, and limited public discussion of model portability outside the o9 shell — config-heavy deployments create real lock-in. Treat the agentic and GenAI roadmap claims as things to validate in a paid proof-of-concept, not as shipped fact.

There is a layer beneath all of this that no vendor markets. The single independent reviewer who graded all three on optimisation transparency scores them in the low fives out of ten — and none of the three publishes its solver formulations or probabilistic semantics. The translation for a buyer is blunt: all three are configuration-first black boxes on the underlying maths. If you need inspectable, code-owned decision logic your team can version and audit, none of these three is your tool — that is a different, model-first category. If you want broad packaged coverage with a familiar enterprise procurement model, all three qualify.

The cost conversation everyone gets wrong

Ignore the starting price. On all three platforms the published licence figure is noise, because the licence is a fraction of true cost. The dominant spend is the run-rate underneath it: data integration, master-data remediation, system-integrator fees, application maintenance and support, internal headcount, and change management. That stack routinely runs multiples of the software, and it is structurally the same across SAP IBP, OMP, and o9.

This is also where the three differ in ways that matter to your budget. SAP IBP carries the largest partner ecosystem — every major SI knows it — which is good for availability and bad for nothing in particular except that the integration and AMS bill compounds annually, especially if your ERP is not SAP. OMP delivers more closely with the vendor itself, which reviewers praise, but customer success "depends heavily on modelling discipline, not just packaged functionality" — the cost is your team's rigour, not just the invoice. o9's certified-talent pool has grown fast but remains scarce relative to demand, which is the lever that drags out timelines and inflates the people cost.

Budget the people and the data, not the licence. The implementations that miss their business case almost never miss it on software price.

The lawsuit you have to factor in

There is one roadmap risk that belongs in any current evaluation of SAP IBP or o9, and it is unresolved as of this writing. In November 2025, o9 filed a trade-secret misappropriation complaint against SAP and several former o9 executives in the U.S. District Court for the Northern District of Texas, alleging that SAP's knowledge-graph roadmap mirrors o9's Enterprise Knowledge Graph. SAP denies the claim and points to its own long-running investments.

The buyer move here is not to pick a side on the merits — it is genuinely unresolved, and that is the point. The implication is narrower and more useful: factor roadmap-transparency risk into both vendors' AI and knowledge-graph commitments. If a salesperson on either side is selling you 2026–27 knowledge-graph capability, treat the timeline as soft and contract for what exists today, not what is promised on a slide.

Choose X if…

Choose SAP IBP if:

• You are on (or committed to) S/4HANA and value one coherent data spine from plan to execution.
• Finance-integrated S&OP on governance templates matters more to you than scenario flexibility.
• You already have SAP SIs and AMS in place and want the lowest-friction procurement path.
• Accept: an Excel-centric planner UX, weaker disaggregation and what-if than APO, and memory-bound scaling cost.

Choose OMP (Unison) if:

• You are a process or CPG manufacturer where finite scheduling and hard production constraints are the planning problem.
• You want one coherent model — not a stitched-together acquired suite — and a vendor that co-delivers closely.
• Accept: a multi-screen UI learning curve, some immature demand-sensing features, and a narrower fit outside your industry.

Choose o9 if:

• You are multi-ERP and heterogeneous, and want an ERP-agnostic planning brain above execution.
• Rapid what-if and combined commercial-plus-operational scenario modelling is a top-three requirement.
• You have the data maturity and governance to absorb a config-heavy graph deployment.
• Accept: premium cost, scarce certified talent, lock-in opacity, and AI claims you will need to prove in your own POC.

Choose none of the three if you want inspectable, code-owned, probabilistic decision logic your team can version and audit. That is a model-first category, and all three of these are config-first black boxes on the maths.

And if your bottleneck is speed of replanning rather than ERP fit or scheduling depth — a change in supply that has to cascade across demand, supply, and finance in near-real time — then the platform to add to your shortlist is not in this comparison at all. That is the concurrent-planning argument for Kinaxis.

The part that survives after the vendor leaves

The platform is not the bottleneck. Whichever of the three you choose, the demo will produce a better plan than your current process — on clean demo master data. Your tenant will not have clean data. The plan is only ever as good as the master data that constrains it and the actuals that feed it, and no solver fixes a lead time that still reflects a contract from three years ago.

So before you score a single feature, audit your own readiness: lead-time accuracy, unit-of-measure consistency, BOM completeness, supplier-capacity data, and a named, funded change-management workstream. The vendors will be helpful through sales and implementation. The capability that survives after they leave is entirely yours to build — and it is the thing that actually determines whether any of these three earns its cost.

---

Sources

• SAPinsider. Comparing SAP IBP and o9 Digital Brain. sapinsider.org
• Lokad. Reviews of o9 Solutions, OMP, and SAP. lokad.com
• Lokad. TCO of SAP IBP. lokad.com
• Gartner Peer Insights. Supply Chain Planning Solutions — OMP / Unison Planning; o9 vs SAP. gartner.com
• Gartner. Magic Quadrant for Supply Chain Planning Solutions (2024, 2025, 2026). gartner.com
• G2. SAP IBP and OMP Unison Planning reviews. g2.com
• Capterra. o9 reviews. capterra.com
• The Config Team. Rethink Excel in SAP IBP. theconfigteam.com
• PRNewswire / FreightWaves / D Magazine. Coverage of the o9 v. SAP trade-secret complaint (Nov 2025).
• Contrary Research. o9 Solutions business breakdown. research.contrary.com