Why SAP Ariba Needed ORO Labs to Take On Coupa After Tonkean

ORO Labs has signed an agreement with SAP to have its procurement orchestration solution sold as an SAP solution extension, branded SAP Ariba Procurement Orchestration by ORO Labs. The offering gives SAP customers a pre-built orchestration layer that connects procurement experiences, workflows, and systems across SAP and third-party applications. General availability is planned for November 2026.

The official framing is about ecosystem flexibility. ProcureScore sees a sharper competitive story. In May 2026, Coupa acquired Tonkean and brought one of the leading intake and orchestration platforms inside its suite. That move put pressure on every S2P vendor without a credible orchestration layer, and above all on SAP Ariba, Coupa’s most direct rival in large enterprise deals. ORO Labs is SAP’s answer, while GEP's Quantum Intelligence (Qi) is their version of agentic procurement.

What was announced

• The partnership model: ORO Labs is now an SAP solution extension partner. Solution extensions must pass SAP’s qualification process and are SAP-branded, sold,and supported through the customer’s existing SAP relationship.
• The scope: Orchestration across mixed SAP and third-party landscapes, including customers running both current-generation and next-generation SAP Ariba environments.
• SAP AI alignment: Designed to work with Joule Work, including deployments where Joule Work is the primary user engagement layer.
• Integration: Pre-built connectors and APIs, with SAP Integration Suite supporting integration orchestration.
• Core capabilities: A unified employee procurement experience, low-code/no-code workflows, cross-system orchestration, and agentic AI embedded in governed processes with approvals and human oversight.
• Ecosystem support: ProcureScore sees this as a major win for ORO Labs first, and for SAP second. More importantly, the partnership lets ORO Labs work with legacy platforms rather than compete against them. ProcureScore also believes SAP may, at some point, consider acquiring ORO Labs outright. In a recent conversation with ProcureScore, a private equity firm’s investors said their main concern was that replacing legacy procurement platforms has proved slow and difficult. This partnership answers that concern directly: it modernizes the procurement experience on top of existing systems instead of waiting for a rip-and-replace.

What Coupa did with Tonkean

Coupa announced on 21 May 2026 that it had acquired Tonkean, an AI-native intake and orchestration platform used by enterprise procurement, legal and internal service teams. Tonkean offers a no-code process builder and more than 250 native connectors, letting customers integrate workflows with existing systems instead of replacing them. It also supports multi-agent orchestration and agent-to-agent coordination, where software agents hand tasks to one another within longer processes.

Coupa reported that Tonkean has helped customers raise user adoption 2.2 times, cut cycle times by 50% and save operations teams more than 30 hours a week. Tonkean was Coupa’s fourth strategic acquisition for its agentic trade network vision, after Cirtuo, Scoutbee and Rossum, adding orchestration to category management, supplier intelligence and document reading. Coupa is integrating Tonkean’s capabilities into Coupa Compose, and some solutions will continue to be sold as add-ons alongside the core suite. Coupa’s message to the market is clear: orchestration, intake and agentic AI now sit natively inside its spend platform as one architecture.

Why Ariba needed to respond

1. Intake and orchestration now lead the deal

Increasingly, procurement technology evaluations begin with the front door: how employees request goods, services and suppliers, and how those requests move through policy, risk, legal and sourcing. P2P and S2P functionality is becoming the back end of that decision, not the headline. With Tonkean, Coupa can lead with orchestration in enterprise deals. Without a comparable layer, Ariba risked being judged on its transactional backbone while Coupa competed on experience.

2. Coupa turned a neutral layer into a suite advantage

Before the acquisition, independent orchestration platforms sat above any S2P suite, Ariba included. Once Tonkean became part of Coupa, the orchestration layer stopped being neutral ground and became part of Coupa’s competitive offer. SAP needed its own credible orchestration partner, and ORO Labs is among the strongest independent platforms left in the enterprise segment.

3. Ariba’s landscape needs orchestration more than most

Ariba customers usually run Ariba alongside S/4HANA, plus third-party tools for supplier risk, CLM, TPRM and tail spend. Many are also moving between Ariba generations, as the announcement acknowledges. That complexity has often counted against Ariba on user experience and process agility. An orchestration layer that spans SAP and non-SAP systems turns that fragmentation into something manageable, and gives customers a modern experience without a back-end migration.

4. It answers Coupa’s agentic story

Coupa is positioning Tonkean’s multi-agent and agent-to-agent capabilities as the engine of autonomous spend management. SAP needed a governed agentic orchestration story for the 2026–27 buying cycle. ORO’s workflows, alongside Joule Work, give SAP a way to run agentic actions within enterprise controls and approvals.

5. Buy vs partner: two different ecosystem strategies

Coupa chose to buy and embed. SAP chose to partner, resell and support. Each approach has trade-offs. Coupa can promise one architecture and one roadmap. SAP gains speed to market and a broader ecosystem, with systems integrators like IBM already behind the offer. It also avoids an acquisition at a time when the market is still deciding what agentic orchestration should look like. Either way, both leaders now agree that orchestration is core to the procurement suite, not a nice-to-have.

The counter-argument Coupa will make

Coupa will argue that a natively owned orchestration layer beats a partner extension: one vendor, one roadmap, one data and agent architecture, and no handoffs between two companies. For customers that value single accountability, that argument will resonate. SAP will need joint reference customers and a clear support model to show the partnership works as one offer.

GEP’s counter-position: orchestration as a native platform capability

GEP has taken a different route. It has neither acquired an orchestration specialist nor partnered with one. Instead, it has repositioned its whole platform around agentic orchestration. GEP Quantum Intelligence (Qi) is presented as an AI-native source-to-pay platform that brings sourcing, contracts, suppliers, purchasing and payments into one experience, and as the agentic orchestration engine behind every workflow.

GEP’s total agentic orchestration message covers three layers under one hood: the user experience, end-to-end procurement processes, and the wider supply chain ecosystem. Users get a single entry point and can start requests in plain language from Teams, collaboration tools, or email. GEP also offers GEP Quantum Intelligence Studio for creating, modifying, and extending agents without tying the customer’s AI strategy to one model or platform.

GEP is also explicit about its competitive stance. In its positioning, it affirms that its AI-native platform outperforms thin orchestration layers built on legacy systems. Its competitive comparison goes further, criticizing a legacy suite vendor whose third-party partner handles intake, a separate company on a separate platform. That description fits the SAP–ORO Labs model closely.

What buyers should consider

1. Owned vs partnered orchestration: Do you prefer orchestration natively owned by your suite vendor (Coupa–Tonkean) or delivered through a qualified partner extension (SAP–ORO Labs)? Consider roadmap control, accountability, and long-term product commitment.
2. Positioning against SAP’s own roadmap: How does the ORO Labs extension fit alongside SAP’s guided buying, Joule Work, and next-generation Ariba? Where does each one start and stop?
3. Third-party coverage: Which non-SAP connectors are pre-built, and which need custom work through SAP Integration Suite? Compare this with Tonkean’s connector library.
4. Agent governance: How are agentic actions governed across SAP and third-party systems, and how are they logged and audited?
5. Support model: How are issues escalated between SAP and ORO Labs, and who owns the product roadmap?
6. Commercial transparency: How will costs be split across platform licenses, implementation and deployment services, and ongoing support and maintenance? Ask for a three-to-five-year total cost of ownership comparison: Ariba plus the ORO Labs extension against Coupa with Tonkean capabilities. Check whether orchestration is bundled or sold as an add-on, how pricing scales with users, request volumes, AI agent usage and integrations, and whether buying through SAP paper changes pricing, discounting or renewal terms.

The bottom line

Coupa bought its way to orchestration with Tonkean, GEP built it natively into its AI-native platform, and SAP has partnered with ORO Labs. Three different models, one shared conclusion: the front door to procurement now matters as much as the suite behind it. For enterprise buyers, choosing between Ariba, Coupa and GEP is no longer only about S2P depth. It turns on who offers the better requester experience, the stronger agentic orchestration, and the more credible ecosystem. Buyers also have a fourth option: an independent agentic orchestration platform that sits above whichever suites they already run. That route keeps the orchestration layer neutral, protects existing investments, and avoids tying the AI strategy to a single suite vendor’s roadmap. The trade-off is more integration ownership and a second vendor to manage.