Contact us
Oil painting in blue: an ERP architect and an e-commerce manager review a printed systems map on the table
  1. Home
  2. Integrations
  3. SAP and e-commerce

SAP talking to e-commerce, the way it should.

SAP S/4HANA, ECC, or Commerce Cloud integrated with VTEX, Salesforce, Shopify, and Emarsys, with governance, observability, and contract discipline.

Book an assessmentSee the architecture

Integrating SAP with the commerce layer requires command of both worlds. For more than 10 years, we have treated this integration as a project in its own right, with its own architecture, squad, and deliverables.

Enterprise combinations we've already delivered

Every e-commerce platform has its specifics, and so does every SAP module. In all of them, integration is asynchronous, secure, and auditable.

Explore the SAP practice
SAP and VTEXECC or S/4HANA with VTEX via CPI, BTP, or middleware on AWS or GCP: orders, customers, inventory, table pricing, invoices, and delivery status. Ideal for retail in Brazil and Latin America.
SAP and Salesforce CommerceB2B and B2C with CPI as the hub, for multi-country and multi-brand operations: orders, quotes, contracts, catalog, dynamic pricing, and returns, with Data Cloud.
SAP and Shopify PlusVia CPI or serverless middleware: orders, customers, inventory, NF-e, and fulfillment, for brands that want speed without giving up the SAP core.
SAP Emarsys in the stackCustomer, behavior, and order data unified between ERP and commerce for omnichannel journeys, without manual exports.
S/4HANA and commerceOn-premise, Private, or Public Cloud: BAPIs, CDS views, OData, events, and authorizations, with continuity during the ECC to S/4HANA migration.
CPI and BTP as the backboneiFlows, managed APIs, Event Mesh, governance, and consolidated monitoring, ready for any commerce, CRM, or marketing endpoint.

Why CCX for this work

The same squad owns the SAP side, the integration layer, and the commerce front end.

10+ years in SAP and commerce

SAP integrations delivered for retail, manufacturing, food service, wholesale, and enterprise B2B.

CPI, BTP, or custom middleware

The path that makes sense for your stack and your moment, with no tool dogma.

Real governance

API catalog, versioning, contracts, observability, dead-letter queue, and reconciliation, all documented.

End-to-end view

A team that masters both sides avoids the classic gap between the ERP vendor and the commerce vendor.

Three layers, no rigid coupling

Contracts stay isolated in the orchestration layer: the ERP evolves at its own pace and commerce at its own, with neither held hostage by the other.

  1. SAP S/4HANACloud or on-premise
  2. SAP ECCCore in operation
  3. ERP contractsBAPIs, IDocs, OData, CDS
  4. SAP CPIIntegration Suite, iFlows
  5. SAP Event MeshEvents on SAP BTP
  6. Cloud queuesAWS SQS or Google Pub/Sub
  7. VTEXVTEX IO and FastStore
  8. SalesforceCommerce Cloud B2B and B2C
  9. Shopify PlusOrders and fulfillment
  10. SAP EmarsysOmnichannel marketing

Reference architecture with CPI at the center. Without an active BTP, serverless middleware on AWS or GCP takes over orchestration.

CPI, BTP, or custom middleware: when to use each

All three paths cover the same functions: orchestration, queues, reconciliation, and observability. What changes is the starting point.

OptionMakes sense whenWatch out
SAP CPI (Integration Suite)The company already has an SAP BTP license and strong corporate SAP governance.At high volume with peaks, combine it with Event Mesh or external queues to protect the core.
Full SAP BTPThe stack mixes SAP and non-SAP systems, with high volume, peaks, and strong SAP governance.Higher investment; a burden on tight budgets and short timelines.
Custom middleware (AWS or GCP serverless)There is no active BTP, the stack is multi-platform, and budget or timeline is tight.Governance depends on the design. If CPI comes later, the migration is smooth because the patterns are already mature.

Three critical flows we solve

Where SAP and commerce integration usually breaks, and how we design each flow.

Catalog and SKU master

Product master in SAP, enrichment via PIM, and incremental sync to VTEX, Salesforce, or Shopify, with deduplication, versioning, and batch rollback.

Price and promotion

Tables by channel, list, B2B segment, and campaign calculated in SAP and published in near real time, preserving discount, contract, and negotiation rules.

Order, fulfillment, and NF-e

The order enters commerce and orchestrates credit, inventory reservation, tax, and fulfillment in SAP, returning status to the consumer with a traceable correlation ID.

An integration that only asks for attention when it needs it

We instrument every message, function, and queue from the first release, so the team learns about a discrepancy before the customer does.

  • A correlation ID on every message, from commerce to SAP.
  • A latency and error-rate dashboard per iFlow or function.
  • A monitored dead-letter queue on every integration.
  • Daily reconciliation with a comparison report between SAP and commerce.
  • Proactive alerts before the consumer calls customer service.
  • After go-live, a dedicated squad, advisory, or on-call support.

Frequently asked questions

What is the best way to integrate SAP S/4HANA with VTEX?

Current practice is to use SAP CPI (Integration Suite) as the orchestration layer, with dedicated iFlows for orders, customers, inventory, pricing, and invoices. VTEX exposes REST and GraphQL APIs and order and catalog events, which allows near real-time integration for critical operations and batch integration for high-volume data.

CPI or custom middleware: which one to choose?

If the company already uses SAP BTP and CPI with active licenses, building on them is the fastest and most governable path. In smaller scenarios or with several non-SAP platforms, middleware on AWS or GCP, with Node, Python, or serverless, can be cheaper and more flexible. CCX works with both.

Does SAP and Salesforce Commerce Cloud integration work well?

Yes. We use Salesforce connectors with SAP CPI for B2B and B2C orders, accounts, and catalogs. Salesforce Commerce Cloud has open APIs and webhooks that cover most scenarios without heavy customization.

What about Shopify Plus?

Shopify Plus also integrates with SAP via CPI or middleware. For small volumes, off-the-shelf connectors may be enough. For larger operations with customizations, we build a dedicated integration through CPI or BTP.

What role does SAP Emarsys play in this stack?

Emarsys is the omnichannel marketing layer: it receives customer, order, and behavior data from the commerce platform and from SAP. We connect Emarsys with VTEX, Salesforce, or Shopify and with S/4HANA or ECC, enabling segmentation, automation, and personalization with unified data.

Can SAP Commerce Cloud (Hybris) be integrated with VTEX?

Yes, in coexistence or transition scenarios. In a Hybris to VTEX migration, it is common to run both in parallel for a while: we keep the SAP integrations intact and make a coordinated switch at cutover.

How long does a typical SAP and e-commerce integration project take?

A core scope, with orders, customers, inventory, pricing, and invoices, usually takes 3 to 6 months. Scopes with B2B, multiple ERPs, a data lake, and personalization can take up to 9 months.

Does CCX support SAP ECC or only S/4HANA?

Both: SAP ECC, S/4HANA on-premise, S/4HANA Cloud Private Edition, and S/4HANA Public Cloud, integrated with VTEX, Salesforce, Shopify, and Emarsys.

I have an in-house SAP team. Can CCX handle only the e-commerce side?

Yes, it's a common model. CCX works on the commerce front end and the integration layer, in CPI, BTP, or middleware, alongside the in-house SAP team.

Get your SAP and commerce integration in order.

Thirty minutes with a CCX engineer, at no cost, to map integrations, risks, and next steps between SAP and your platform.

Book an assessmentRequest a proposal