SAP's CX Vision for Its Autonomous Enterprise Gets Product General Availability Timeline at Connect 2026
SAP Connect 2026 provided a clearer view of how SAP intends to execute its Autonomous Enterprise product vision. This emerging vision combines Joule Work as a common AI interface, Joule Assistants as role-based process coordinators, specialized Joule Agents as task executors, and SAP Business AI Platform as the foundation for data and governance.
For customer experience (CX), the significance of SAP’s AI architecture concerns how it connects front-office engagement with the operational systems that determine pricing, inventory, fulfillment, service delivery, and payment. Connect announcements for CX included new and expanded Joule Assistants across marketing, commerce, sales, service, operations, and compensation, alongside expanded Order Management Services, the general availability of SAP Commerce Cloud, cloud ERP edition, and a native connection between SAP Engagement Cloud and SAP Sales Cloud.
These developments do not constitute an entirely new SAP CX strategy. Instead, they are the products manifested from SAP’s Autonomous CX vision introduced at Sapphire in May 2026. Although parts of Connect’s announcements are repackaging and roadmap amplification, the combination of Order Management Services, ERP-connected commerce, Reltio, and cross-functional assistants makes SAP’s CX proposition more compelling.
The main caveat is availability. SAP Commerce Cloud, cloud ERP edition, and Reltio are available now, while the new CX assistants, enhancements to existing assistants, and expanded order management capabilities are not expected until Q1 2027. This note examines what SAP announced, how the components fit together, and what organizations should consider as the CX product strategy moves toward deployment.
Joule Work Begins Its Customer Rollout
Joule Work is beginning its customer rollout as SAP’s common interface for interacting with enterprise applications, data, assistants, and agents. Employees can use natural language to retrieve information and execute work across SAP and third-party environments.
Joule Work is grounded in business context from SAP Knowledge Graph, which maps more than 7 million data fields. Joule Work also connects with Joule Studio, where organizations can create and extend AI skills and agents using more than 70 supported models.
SAP is positioning openness and governance as important differentiators. Joule supports Agent2Agent connectivity with third-party agents, with a Model Context Protocol server for Commerce Cloud storefronts separately introduced. Agents operate within established user permissions, with SAP AI Agent Hub in LeanIX providing a central inventory of enterprise agents.
Neither Joule Work nor the broader Autonomous Enterprise strategy is entirely new. Both were introduced at Sapphire. SAP Connect represented the next stage: showing more detailed workflows, expanding the assistant portfolio, and beginning customer rollout. SAP reported that Joule Work is live with 110,000 of its own employees, with 20% productivity gains across finance, HR, and procurement; however, no baseline or contextual figures have been given to corroborate this effectiveness.
New Assistants Expand SAP’s Autonomous Enterprise for CX
SAP announced new and enhanced Joule Assistants intended to coordinate work across customer-facing and operational functions. These assistants draw on shared context including customer interactions, products, orders, contracts, prices, payments, and organizational policies.
The announced CX capabilities include:
General availability for these additions and enhancements is planned for Q1 2027.
With these new AI assistants, SAP is attempting to connect customer-facing tasks to the operational processes required to complete them. A campaign, for example, should account for inventory and product availability before promoting an offer. A quote requires current prices, contractual terms, and approval policies. A service commitment may require coordination across workforce availability, logistics, billing, and customer history. SAP’s advantage here is the breadth of operational information already held within its application portfolio.
Order Management Services Extends Across Complex B2B Environments
SAP is expanding SAP Order Management Services to coordinate B2B orders across SAP S/4HANA, other ERP systems, legal entities, business units, inventory locations, and fulfillment networks. SAP Order Management Services will validate orders, check inventory across locations, coordinate transactions between business units, and provide operations teams with a common view of order progress.
New Joule Agents within the Order Management Assistant will identify disruptions, initiate exception workflows, and help operations teams respond before issues affect customers. General availability for the expanded capabilities and agents is planned for Q1 2027.
Commerce Cloud Extends into the Midmarket
The cloud ERP edition of SAP Commerce Cloud is now generally available. Initially introduced at Sapphire, this edition provides midsize and growing organizations with a standardized, SAP-managed route to ERP-connected digital commerce.
SAP Commerce Cloud has traditionally been associated with large and comparatively complex enterprise deployments. The cloud ERP edition gives SAP a more packaged commerce proposition for organizations that want ERP-connected capabilities without adopting the platform through a heavily customized implementation.
SAP also announced a native connection between the enterprise edition of SAP Engagement Cloud and SAP Sales Cloud. The integration synchronizes company and contact information and places relevant marketing engagement signals into sales workflows.
SAP Reltio Provides Context for CX Agents
SAP Reltio is now generally available within SAP Business Data Cloud. Based on technology SAP recently acquired from Reltio, the solution reconciles fragmented records for customers, suppliers, products, and employees across SAP and third-party applications.
SAP describes this as a “system of context” that gives applications and AI agents a consistent understanding of business entities. For CX, this foundation is critical. An autonomous assistant cannot make dependable decisions if customer identities, product attributes, account relationships, or commercial terms differ across systems.
As such, Reltio provides an important, if less visible, component of the Autonomous CX proposition. The assistants supply the intelligence and workflow coordination; Reltio, Business Data Cloud, and Knowledge Graph are intended to supply the trusted context.
SAP Pay Launches
SAP announced SAP Pay, an embedded payment service powered by SAP subsidiary Tereina. SAP Pay executes and reconciles supplier payments directly within SAP Cloud ERP, supporting EFT, including ACH, wire, check, and stablecoin-based cross-border settlement. It is generally available in the United States and United Kingdom.
SAP Pay is notable because it reflects the broader direction of SAP’s strategy. SAP is moving beyond software that records transactions or recommends next steps toward software that executes business activity directly. This same transition underpins SAP’s Autonomous CX proposition: AI should recognize customer intent and carry that intent through the processes necessary to deliver an outcome.
Other Connect announcements included new finance, procurement, workforce, supply chain, governance, and industry-specific assistants; the planned acquisition of workforce intelligence provider TechWolf, expected to close in Q4 2026; Moody’s supplier risk intelligence within SAP Ariba; and procurement orchestration through ORO Labs. A full list is available in SAP’s Connect 2026 Innovation News Guide.
Our Take
SAP did not introduce a new CX strategy at Connect. Autonomous CX, Joule Work, and the broader Autonomous Enterprise vision were established at the Sapphire conference in May 2026. The Connect announcements made that strategy more tangible through expanded assistants, customer deployments, and product availability. The practical constraint for buyers is timing: Among the CX-relevant items, only SAP Reltio and Commerce Cloud are generally available, while most of the new CX capabilities are planned for Q1 2027.
SAP is unlikely to establish market leadership in CX. Competing CRM, marketing, commerce, and contact center vendors offer similar capabilities, often with stronger adoption in their respective categories. SAP’s defence is that CX cannot be separated from pricing, inventory, credit, orders, supply chains, field operations, invoices, and payments; SAP already owns many of the systems governing those processes and so claims authority over these workflows.
However, that defence is not unique to SAP. Oracle makes a similar case for running CRM alongside ERP, HCM, and supply chain data in one suite. SAP's differentiation, at least for the moment, is its heterogeneous positioning: Order Management Services across SAP and non-SAP ERPs alongside Reltio across third-party applications.
As such, Order Management Services, Commerce Cloud’s connection to Cloud ERP, and the Reltio data foundation are more strategically important than the Joule Assistant announcements. Together, they give SAP an opportunity to orchestrate the operational side of CX, particularly for manufacturers, distributors, retailers, utilities, and other organizations with complex fulfillment requirements.
SoftwareReviews’ data suggests that SAP’s laggard status in the CX space does not mean poor satisfaction. SAP Commerce Cloud, for instance, is a 2026 Emotional Footprint Champion for both B2B and B2C eCommerce categories; 95% of reviewers plan to renew, and 88% are likely to recommend. In line with Connect’s announcements, SAP scores 91% for strategy and innovation.
However, Commerce Cloud scores lower than both the B2B and B2C eCommerce category score averages for “ease of data integration” and “usability and intuitiveness.” Indeed, the risk is that SAP’s portfolio breadth, and now heterogeneous approach, creates implementation complexity: Cross-functional autonomy requires harmonized data, integrated applications, explicit process ownership, and governance that extends well beyond the CX team.
Buyers should also separate available products from forward-looking demonstrations. The customer examples SAP presented at Connect came largely from finance, procurement, and supply chain rather than CX. Organizations should begin with narrow workflows where SAP already controls the relevant customer and operational data, establish baseline measures for cycle time, exceptions, accuracy, and customer outcomes, and require SAP to demonstrate end-to-end execution in the buyer’s actual application landscape before accepting the broader Autonomous CX claim.