SAP Business One + Shopify integration

Orders arrive through Shopify webhooks and are usually created in SAP B1 within seconds to a couple of minutes. Stock is read from the Service Layer on a short schedule, often every 5 to 10 minutes, and can also be pushed after goods receipts or deliveries. On SAP Business One 10.0 FP 2602 or later, Service Layer webhooks can notify the integration when documents change; SAP ships them disabled for each company, and they need the Webhook Messenger Service.

The Service Layer for new integrations. SAP describes it as an OData service built on the same DI core as the DI API, so business objects and properties match. The DI API is a Microsoft COM library that fits Windows add-ons, and we use it only where the Service Layer lacks a function. SAP also lists Service Layer limits, such as no user transactions across requests, which we handle with batch requests and retry-safe design.

Less than it used to. SAP added Service Layer support for Microsoft SQL Server with SAP Business One 10.0 PL01, so both versions integrate through the same API. Differences remain in reporting features: Semantic Layer views are HANA only, while SQL Server systems can expose their own SQL views through the Service Layer. Older SQL Server releases without the Service Layer need the DI API or an upgrade first.

Yes. Each Service Layer login names one company database, so the integration keeps a session per company and routes each order by store, market or SKU rule. Warehouses, price lists, tax codes and payment accounts are mapped per company, and no order is written to a company without an explicit rule.

We map SAP B1 ItemCode to the Shopify variant SKU and handle variants, bundles and units of measure explicitly in the mapping workbook. Shopify customers are matched to Business Partners by email or a stored CardCode, with an optional shared web-customer account for guest checkouts. The CardCode is written back to the Shopify customer so the next order matches without a search.

It stops in a retry queue with the SAP error, for example a missing item, a blocked Business Partner or a credit limit, and an alert goes to the named owner. Technical errors retry automatically; data errors wait for a fix and a replay. Before creating an order, the integration checks for an existing document with the same Shopify order ID, so replays and duplicate webhooks cannot create a second sales order.

Most businesses create a sales order, then a delivery and an A/R invoice as goods ship, because stock is committed and fulfillment is tracked in SAP B1. Stores that ship at checkout or sell services sometimes post an A/R invoice directly, with an incoming payment for the Shopify transaction. We decide per sales channel with your finance team.

Captured payments become Incoming Payments against the A/R invoice, posted to the bank or clearing account agreed for each payment gateway. Refunds create A/R Credit Memos, and when goods come back to stock a Return document comes first. Payout fees and settlements are matched in a separate step so the clearing account reconciles to your bank.

Start with the smallest option that covers your flows. A Shopify App Store app such as eShopSync’s SAP Business One Integration publishes B1 items and item groups to Shopify for a published monthly fee. iPaaS templates, such as Celigo’s Shopify and SAP Business One template, add orders, customers and items. A custom build is worth it for multiple companies or stores, B2B price lists, bundles and kits, special refund rules, or when you want to own the code.

The number of flows and stores, and how much logic sits between them. Multiple B1 companies, B2B price lists, bundles and kits, units of measure, historical backfills and peak-season volumes all add build and test time. Ongoing cost depends on hosting, monitoring, any iPaaS subscription and the support you choose. A written scope lists each of these before you approve an estimate.

Yes. B1 price lists and special prices for specific Business Partners map to Shopify price lists, which attach to catalogs assigned to company locations. Shopify’s pricing page lists B2B on Basic, Grow and Advanced with up to three catalogs, and unlimited catalogs on Plus, so your plan sets how many customer price groups can have their own list. Payment terms and tax exemptions are set per company location in Shopify and should match the Business Partner in B1.

Yes, without exposing the Service Layer to the internet. Common patterns are a small agent inside your network that calls the Service Layer and sends data out, or a VPN to a hosted integration service. SAP’s guide also recommends firewalling Service Layer load-balancer members so only the load balancer can reach them, and we keep that in place.

You choose. We hand over the code, mapping workbook, runbook and alert setup so your team can operate it, or we support it under an agreed plan. Shopify releases a new API version every quarter and supports each for at least 12 months, and SAP ships B1 feature packs, so someone should review both on a schedule.

Yes. We can build a custom MCP server exposing the SAP B1 Service Layer and Shopify Admin API so an assistant can check stock, look up an order’s status across both systems or trigger a re-sync for a specific SKU. Write actions are scoped and auditable.

A standard products, stock, orders, customers and fulfillment sync usually takes a few weeks including testing against a copy of your SAP B1 company. Multiple Shopify stores, B2B price lists per customer, or complex bundles and kits extend the build, typically to two to three months.