Start with your SAP edition.
The SAP product you run decides the integration route more than any connector does. Each edition exposes different APIs, runs in a different place and follows its own release calendar. Pin down the edition, release and hosting first; many scoping mistakes start with “we run SAP” and nothing more.
SAP Business One runs on your own servers or with a hosting provider, on SAP HANA or Microsoft SQL Server. SAP Business ByDesign is SAP’s cloud ERP for small and mid-market companies, delivered as SAP-hosted tenants. SAP S/4HANA comes as Cloud Public Edition, Cloud Private Edition or an on-premise installation, and Public Edition has its own API catalog, separate from the one for Private Edition and on-premise releases. SAP ECC is the previous generation, and its maintenance dates should shape how much you invest in it.
SAP’s own Shopify integration package targets S/4HANA. When we checked the SAP Business Accelerator Hub in September 2026, SAP published a package for S/4HANA Cloud Public Edition and a general Shopify adapter for SAP Integration Suite, and partners listed packages for Public and Private Edition. There was no Shopify package for ByDesign or Business One.
| SAP edition | Integration route and APIs | Hosting | Typical first scope | Watch-outs |
|---|---|---|---|---|
| SAP Business One | Service Layer (OData v3 and v4) on SAP HANA, and on SQL Server from 10.0 PL01; DI API for Windows add-ons; Service Layer webhooks from 10.0 FP 2602 | Your servers or a hosting provider | Items, stock by warehouse, orders, customers, deliveries, payments and refunds | Older SQL Server releases without the Service Layer; secure access to on-premise servers; routing across several company databases |
| SAP Business ByDesign | SOAP web services such as Manage Sales Orders; custom OData services; analytics OData for stock; SAP Cloud Applications Studio for logic inside the tenant | SAP-hosted test and production tenants | Orders with external payment, materials, price lists, stock, deliveries and returns | External payment needs the web service, not OData; tenant upgrade windows; no ByDesign Shopify package on the SAP Hub |
| SAP S/4HANA Cloud Public Edition | APIs published for this edition, such as Sales Order (A2X), enabled through communication arrangements; SAP’s Shopify package on SAP Integration Suite | SAP’s cloud | Products, stock, prices, B2C customers, orders, cancellations, returns and deliveries | SAP’s package lists B2C customers only; B2B, bundles and custom order types need extension |
| SAP S/4HANA Private Edition or on-premise | The API catalog for these releases, BAPIs over RFC and IDocs; RFC and IDoc adapters in SAP Integration Suite | Private cloud or your data center | The Public Edition scope plus custom order types and existing interfaces | APIs can differ from Public Edition; transports and security reviews take calendar time |
| SAP ECC | IDocs such as DEBMAS and MATMAS, and BAPIs over RFC | On-premise or hosted | Orders and stock first, with a mapping layer that can move to S/4HANA | Mainstream maintenance ends in 2027 and optional extended maintenance in 2030 |
Reference: SAP Business Accelerator Hub: SAP S/4HANA Cloud Public Edition Integration with Shopify
Connector, iPaaS or custom build.
There are four common ways to deliver the integration, and a prebuilt option is sometimes all you need. Compare them on the flows they actually cover and on what happens when something fails, not on the logos on a vendor’s page.
A Shopify App Store app is the quickest start when the job is narrow. For example, eShopSync’s SAP Business One Integration app lists item and item-group sync from SAP B1 to Shopify at $99 per month; its listing does not cover orders. iPaaS templates cover more: Celigo’s Shopify and SAP Business One template includes flows for orders, customers and items, and APPSeCONNECT lists plans from $99 per month plus flow packs. Prices here are vendor list prices checked in September 2026.
A custom build costs more up front and pays off when your rules are specific: several SAP companies or Shopify stores, B2B price lists, bundles and kits, unusual refund handling, or a requirement to own and host the code. Many projects combine approaches, for example SAP’s package for standard S/4HANA flows and custom work for B2B.
| Approach | A good fit | Check before you buy |
|---|---|---|
| Shopify App Store app | One narrow flow, such as publishing the catalog | Which objects and directions the listing actually covers |
| iPaaS template | Standard orders, customers, items and stock on a vendor-run platform | How pricing grows with flows and volume, and how custom changes are charged |
| SAP Integration Suite content | S/4HANA teams that already run Integration Suite | Which flows are published, and what licensing your runtime needs |
| Custom build | Multiple companies or stores, B2B pricing, bundles, special refunds | Who hosts, monitors and updates it, and what the handover includes |
Reference: Shopify App Store: SAP Business One Integration by eShopSync
Decide who owns each record and how fast it moves.
Most integration problems are ownership problems. For every record, write down which system creates it, which may change it and which only displays it. The usual split is simple: SAP owns products, prices, stock, customers once they buy on account, deliveries and invoices; Shopify owns carts, checkouts, payments and the web order until SAP accepts it.
Then set the timing per flow instead of promising “real time” everywhere. Orders should post within minutes of payment, driven by Shopify webhooks. Stock changes with every goods movement, so it usually moves on a short schedule, backed by a nightly comparison of every SKU. Prices and product data change in batches and can move hourly or after a release. Shopify itself tells app developers not to rely on webhooks alone, because delivery is not guaranteed, and to run reconciliation jobs as well.
Build new work on Shopify’s GraphQL Admin API. Shopify made the REST Admin API legacy on October 1, 2024, and new public apps must use GraphQL since April 1, 2025. Bulk operations handle large loads, such as the first catalog sync or a historical backfill.
| Record | Usual owner | Typical timing |
|---|---|---|
| Products and descriptions | SAP | Hourly or after changes |
| Prices and B2B price lists | SAP | Scheduled, respecting validity dates |
| Available stock | SAP | Every few minutes, plus a nightly comparison |
| Web orders | Shopify until posted, then SAP | Within minutes of payment |
| Customers | Shopify for shoppers; SAP once they buy on account | Before the first order posts |
| Deliveries and tracking | SAP or the warehouse system | Shortly after goods issue |
| Refunds and returns | Started in Shopify, booked in SAP | Within the day, with finance review for exceptions |
Reference: Shopify: About webhooks (ordering, duplicates and reconciliation)
Shopify Plus, B2B and multiple stores.
Shopify’s pricing page lists Shopify B2B on the Basic, Grow and Advanced plans with up to three catalogs, and unlimited catalogs on Plus. B2B buyers are companies with locations and contacts. Catalogs are assigned to company locations and carry price lists with fixed prices or percentage adjustments, and payment terms, tax exemptions and order review settings sit on the company location too.
Every SAP edition has an equivalent: price lists and special prices in Business One, customer-group and customer-specific price lists in ByDesign, and pricing condition records in S/4HANA. The integration turns those into Shopify catalogs and keeps them current. This is also where prebuilt options most often stop; SAP’s S/4HANA package, for example, lists B2C customer replication only.
Plus also lists up to nine free expansion stores. Each extra store needs its own rules for which SAP company, sales area or warehouse receives its orders, which currency it sells in and which price list it shows.
- Count your customer price groups and compare them with your plan’s catalog limit.
- Decide which system creates B2B companies and where the SAP customer number is stored.
- Match payment terms and tax exemptions between Shopify company locations and SAP customers.
- Write routing rules for each store: SAP company or sales area, warehouse, currency and price list.
Test the failures, then cut over in stages.
Test in an SAP test system, not production: a copy of the Business One company, the ByDesign test tenant or the S/4HANA quality system, paired with a Shopify development store. Write the expected SAP document and Shopify state for each test before running it, and name the person who signs it off.
Most defects hide in the unhappy paths. Shopify documents that webhooks can arrive out of order, more than once or not at all. SAP can reject a valid order because of a blocked item, a missing price or a credit hold. The integration must survive all of these without losing or duplicating an order.
Cut over in stages. Load products and stock first and compare them, then switch on order posting for one store or one period, then add refunds and B2B. Keep the old process available until the reconciliation reports come back clean.
- A paid order with a discount, shipping and tax posts once, with matching totals.
- A duplicated webhook creates no second order.
- An order for an unmapped SKU stops with a readable error and posts after the fix.
- A partial delivery creates a partial fulfillment with tracking.
- A refund creates the return or credit memo finance expects.
- The nightly stock comparison reports no unexplained differences.
If you still run SAP ECC.
SAP’s mainstream maintenance for SAP Business Suite 7, which includes SAP ERP 6.0, runs to the end of 2027, with optional extended maintenance to the end of 2030. For its largest customers SAP added a paid transition option for 2031 to 2033, which requires moving to SAP ERP, private edition on SAP HANA before the end of 2030. SAP states that the option is not a maintenance extension for on-premise systems.
That is not a reason to wait. If an S/4HANA conversion is more than a year away, a focused ECC integration for orders and stock usually pays for itself. Keep the order rules and field mapping outside the ECC connector, so the move to S/4HANA replaces one adapter instead of the whole integration.
Reference: SAP News: SAP ERP, private edition, transition option
What to prepare before scoping.
A useful scoping call needs facts about both systems and the business rules between them. You do not need a finished specification, but the answers below let a delivery team give you a realistic plan and price.
- SAP edition, release and hosting, and who can grant API access or create communication arrangements.
- Shopify plan, number of stores and markets, and any apps that already touch orders or inventory.
- The flows in scope, their direction and the system that owns each record.
- Order volumes on a normal day and at peak, and the acceptable delay for each flow.
- How guest checkouts, B2B buyers, bundles, discounts and taxes should appear in SAP.
- How payments, refunds and payouts are booked today, and who in finance signs off.
- Test systems on both sides, and who will own monitoring after go-live.
How AIONDATA can help.
AIONDATA is an independent consultancy with leadership in San Ramon, California and engineering in Noida, India, and its delivery processes are ISO 9001:2015 and CMMI Level 3 certified. We are not certified by SAP or Shopify, and we will tell you when a prebuilt connector or SAP’s own package is the better choice.
We can review an existing connector, extend SAP’s Integration Suite content or build a custom integration on your edition’s APIs, with monitoring, reconciliation and a full handover. A standard products, stock, orders, customers and fulfillment sync usually takes a few weeks including testing; multiple stores, B2B price lists or complex bundles typically take two to three months.
Put the plan into practice.
Bring one workflow and the systems involved. We can help define the implementation, integration or training scope.