Shopify SAP Business One integration
OpusNext connects Shopify to SAP Business One over the Admin API, mapping your real B1 items, user-defined fields, business partners and price lists to Shopify products, customers and orders - including Shopify B2B companies and catalogs where you use them. Data moves by event in both directions. Typical go-live is 2 to 6 weeks.
What syncs between SAP B1 and Shopify
| Data | Direction | What it means |
|---|---|---|
| Products, variants & metafields | B1 → Shopify | B1 item data, including the fields you added |
| B2B companies & catalogs | B1 → Shopify | Business partners priced like they are in B1 |
| Inventory by location | B1 → Shopify | Each location shows the right warehouse stock |
| Orders & draft orders | Shopify → B1 | Straight into B1 as sales orders |
| Invoices & fulfilments | B1 → Shopify | Status visible to the customer |
Where Shopify projects usually go wrong
The parts that decide whether this integration ages well - and how we handle them.
Shopify B2B is its own model. Companies, locations, catalogs and price lists do not map one-to-one onto B1 business partners, ship-to addresses and price lists - and this is exactly where most projects quietly go wrong.
We agree the model with you first: which B1 business partner becomes a company, how ship-to addresses become locations, and which price list drives each catalog. Then the sync follows that model instead of improvising.
Shopify variant and option rules are stricter than a B1 item structure. Catalogues that are perfectly normal in B1 will not fit the platform without a deliberate decision about what becomes a product, a variant or a metafield.
The mapping engine reads your real B1 structure and we make those calls with you before launch, so nothing is silently dropped or flattened into the wrong product.
The Admin API is rate limited by design. A connector that polls or fires large bursts spends its budget on nothing and falls behind on the updates that matter, like stock during a promotion.
We sync on events and pace writes within the API budget, prioritising stock and price so the storefront stays accurate when traffic spikes.
Before you choose a Shopify connector
Five questions worth asking any vendor - and our answers for SAP B1.
OpusNext: Yes. User-defined fields are read and mapped into product data and metafields, agreed with you up front.
OpusNext: Resolved in B1 per business partner, price list, quantity and currency, then applied through the customer or B2B catalog.
OpusNext: Event-driven, paced within the Shopify Admin API budget so stock and price stay current at peak.
OpusNext: No. We connect directly to B1 through the Service Layer or DI API - no middleware server in between.
OpusNext: We use the official Admin API, and the B1 mapping re-checks itself when your schema or version changes.
Shopify and SAP Business One - common questions
Does OpusNext support Shopify B2B?+
Yes. B1 business partners can drive Shopify companies, locations and catalogs, so B2B buyers are priced the way they are priced in B1.
Can Shopify show SAP Business One customer-specific pricing?+
Yes. The price is resolved in B1 for the logged-in buyer, including price list, quantity breaks and currency.
How is inventory handled across Shopify locations?+
B1 warehouse stock is mapped to the matching Shopify locations, so availability reflects the warehouse that will ship the order.
Do Shopify orders create business partners in B1?+
Yes. Orders post to B1 in seconds as sales orders, with the customer created or matched as a business partner.
What about Shopify API rate limits?+
We sync on events and pace writes inside the API budget, prioritising stock and price updates so the storefront stays accurate during peaks.