Shopify + SAP Integration

All three main lines, but not the same way. Business One integrates through the Service Layer as the strategic surface on current versions, with the older DI API still shipping alongside it and common on older installs. S/4HANA integrates through OData APIs, with SAP BTP or middleware carrying the flow. ECC integrates through IDocs and BAPIs behind an integration layer. Authentication, object models, constraints, and timelines differ across the three, which is why the first question in any scoping conversation is which SAP you run, which version, and where it is hosted.

No. SAP does not ship a first-party Shopify connector with Business One, S/4HANA, or ECC, and the third-party market is fragmented: most connectors target one SAP product and one integration pattern, so a vendor claiming to cover every SAP the same way is describing a brochure, not an architecture. What exists is a market of single-product connectors, most of them built for Business One, and some are genuinely useful within that scope. The evaluation question is never "does it support SAP" but "does it support your SAP, your version, and your deployment". A pitch that answers the first question without the second is a brochure, not an architecture.

Because there is no generic SAP. Business One, S/4HANA public cloud, S/4HANA private cloud, and ECC expose different APIs, different object models, different authentication, and different constraints. A vendor who has actually delivered SAP integrations will ask which one you run before quoting anything, and will name the integration surface they intend to use. A vendor who quotes a price for "SAP" without asking is quoting for a project they have not understood yet, and the gap surfaces later as change requests.

Through released OData APIs only. Public cloud does not allow direct database access or custom code inside the core, so anything the released APIs do not cover needs a proper extension, typically built on SAP BTP, rather than a quick workaround. The upside is that the APIs you are allowed to use are clean, documented, and stable across upgrades. Private cloud and on-premise S/4HANA relax these restrictions, which is exactly why the deployment model changes the scope and has to be established before anyone quotes a number.

Integrate now, and build so the SAP-facing edge is swappable. ECC integration through IDocs such as ORDERS, MATMAS, DEBMAS, and DESADV is mature, well understood, and works. SAP has announced the end of mainstream maintenance for ECC in 2027 with paid extension options beyond that, so the migration pressure is real, but S/4HANA programmes run for years and the store cannot wait for one. Keeping the mapping logic in the middleware rather than inside SAP means the eventual cutover swaps an adapter instead of rebuilding the integration.

SAP owns base and contract pricing, Shopify owns promotions, and the invoice price authority is SAP. That split holds up because SAP pricing, especially condition-based pricing on ECC and S/4HANA, models things Shopify’s single price field cannot, while promotions change too fast to route through ERP governance. The order carries the price actually charged at checkout into SAP explicitly, and a reconciliation report flags any line where the systems disagree. Customer-specific contract pricing surfaces to logged-in wholesale buyers through Shopify B2B catalogues, which requires Shopify Plus.

Ten to twenty weeks, a wider range than we quote for any other ERP because SAP varies more than any other ERP. Business One projects land near the bottom of that range, heavily customised ECC estates near the top. The things that move the number are master data quality, the count of company codes and plants, customisations in the order flow, and how quickly your basis team or SAP partner can provision access. We run a staged cutover with a parallel-run window rather than a big-bang switch, because with an ERP that owns finance, boring is the goal.