Shopify SAP Business One Integration: Service Layer, Sessions, and Sync Design

SAP Business One is a common ERP for small and mid-size distributors and manufacturers that add a Shopify store — often alongside wholesale and EDI. It has no Shopify connector of its own, so integrations come from SAP partners, integration platforms, or custom builds. This page covers what any of those must handle on the Business One side. As on every page, documented marks statements from SAP or Shopify documentation, and recommendation marks our guidance.

The Service Layer

Documented: the SAP Business One Service Layer is an OData-based web API. SAP describes its core as the same interface used by the SAP Business One DI API, with identical object definitions. A session starts with a login request and ends with a logout request; after login, the B1SESSION cookie must be sent with subsequent requests (a ROUTEID cookie supports session stickiness in load-balanced setups).

Documented: the Service Layer’s session timeout is an idle timeout per session, 30 minutes by default, configured by the administrator in the Service Layer configuration file; configuration changes take effect after a Service Layer restart.

Recommendation:

• Use a dedicated Business One user for the integration with only the permissions it needs.
• Keep one session per worker and reuse it; logging in for every request is slow and can hit license limits.
• On a 401 with an invalid-session error, log in again once and retry; if that fails, stop and alert.
• Always log out when a batch ends, so sessions don’t accumulate.

POST https://{server}:50000/b1s/v1/Login
Content-Type: application/json

{ "CompanyDB": "{company}", "UserName": "{integration_user}", "Password": "{secret}" }

POST https://{server}:50000/b1s/v1/Orders
Cookie: B1SESSION={session}; ROUTEID={route}
Content-Type: application/json

{
  "CardCode": "WEBUS",
  "NumAtCard": "SHOP-US-5551234",
  "DocDueDate": "2026-10-30",
  "DocumentLines": [{ "ItemCode": "TSHIRT-BLK-M", "Quantity": 2 }]
}

Illustrative only. Ports, version paths, required fields, user-defined fields, and numbering series depend on your installation — confirm with your SAP partner and the Service Layer metadata.

Orders without duplicates

Documented (Shopify): Shopify webhooks can be delivered more than once.

Recommendation: put the Shopify order ID (with a per-store prefix) in a searchable reference such as the customer reference number on the sales order, keep your own processed-events table, and query Business One for that reference before retrying an uncertain create. See preventing duplicate orders.

Getting changes out of Business One

Recommendation: stock, shipments, and price changes need to flow from Business One to Shopify, and a standard setup won’t push them for you. Common patterns:

• Scheduled change detection: every few minutes, query items, stock, and delivery documents updated since your last checkpoint (scheduled synchronization).
• Partner or platform event tooling: some partners and integration platforms provide event mechanisms for Business One; evaluate them for latency and reliability.
• Daily full reconciliation of stock per warehouse, whichever pattern you choose.

Respect Shopify’s rate limits when pushing large stock updates — batch them and send only changed quantities.

Inventory, fulfillment, and accounting

Recommendation:

• Warehouses: map each Shopify location to one Business One warehouse; publish available quantities (on hand minus committed) with safety buffers.
• Fulfillment: when the delivery is posted in Business One, create the Shopify fulfillment with carrier and tracking.
• Tax: post the sales tax Shopify or your tax engine calculated at checkout; don’t recalculate it (sales tax guide).
• Payouts: reconcile Shopify Payments payouts as net deposits with fees booked separately (reconciling payouts).
• Add-ons and UDFs: list the user-defined fields and add-ons that touch sales documents before mapping — they are where most surprises come from.

Common pitfalls

• Logging in on every request and running out of sessions or time.
• Expired sessions handled as permanent failures instead of a clean re-login.
• No change detection for stock and shipments, so Shopify drifts.
• Duplicate orders after timeouts without a reference lookup.
• Ignoring partner customizations (UDFs, numbering series, approval procedures) that reject API documents.