How does ml-connector handle the differences between Shopify orders and SAP Business One invoices?

Shopify orders become draft invoices in SAP Business One, not posted invoices, so the accounting team retains control over when financial entries are committed. The order number and customer name are mapped to SAP Business One fields, and a record in the audit trail links the two so you can trace any invoice back to its source order.

Does the integration require the SAP Business One Webhook Messenger Service to be set up?

No. ml-connector works with polling by default and does not require webhooks. If your SAP Business One admin has activated the Webhook Messenger Service, ml-connector can accept webhook events as well, but polling is the standard approach.

What happens if an order is placed in Shopify but the cost center does not exist in SAP Business One?

ml-connector validates cost centers and addresses against SAP Business One before posting. If a required dimension is missing, the order is held in the audit trail so you can add the cost center and replay the record without re-entering the order details.

SAP Business OneShopify

SAP Business One and Shopify integration

SAP Business One handles manufacturing finance, inventory, and accounts receivable. Shopify runs e-commerce and captures orders and customer information. Connecting them keeps your financial records and your sales channels aligned. Orders placed in Shopify flow into SAP Business One as invoices and receivables, customers from Shopify sync as business partners, and payment records close the loop automatically. ml-connector handles the very different APIs on each side and moves the data on a schedule you control.

How SAP Business One works

SAP Business One exposes business partners, invoices, purchase orders, orders, payment records, journal entries, and chart of accounts through OData v4 REST at a customer-specific Service Layer endpoint. Authentication is a session token issued via POST /Login that expires after 30 minutes of inactivity, with error code -5002 on timeout. SAP Business One v10.0 FP 2602 and later support webhooks for Create/Update/Delete events if the Webhook Messenger Service is activated by the SAP admin, but polling is recommended as the default approach. Each customer provides their own Service Layer hostname and port, typically 50000 or 50001.

How Shopify works

Shopify is a cloud-hosted e-commerce platform that exposes orders, customers, transactions, refunds, draft orders, and inventory through the Shopify Admin API in both GraphQL and REST formats. Authentication is OAuth 2.0 Authorization Code Grant with offline tokens (prefix shpat_) that do not expire, issued once at app install time. Shopify publishes webhook events for orders, customers, payments, and fulfillments with signature verification via X-Shopify-Webhook-Id. The API is rate-limited and versioned by date, with quarterly releases and approximately 12 months of support per version.

What moves between them

Orders and customer data flow from Shopify into SAP Business One on a schedule you set. Each Shopify order becomes a draft invoice in SAP Business One, mapped to a sales account and cost center. Shopify customers sync as business partners so AR aging reports and customer inquiries reference the same names and addresses. Payment records from Shopify are matched against invoices in SAP Business One to track collections. SAP Business One is the source of truth for the general ledger, so ml-connector never writes financial entries back into Shopify.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the Shopify side, it accepts the OAuth offline token issued at app install and handles webhook events with signature verification using X-Shopify-Webhook-Id. On the SAP Business One side, it accepts the customer-specific Service Layer hostname and port, logs in with the session token, and reuses the session across multiple requests to avoid the 5-second cold-start overhead. Session tokens expire after 30 minutes of inactivity, so ml-connector monitors the error code -5002 and re-authenticates when needed. Orders are deduplicated by Shopify order number before posting, and the draft invoice number in SAP Business One is mapped back to the source order for the audit trail. Cost centers and ship-to addresses are validated in SAP Business One before posting, so every order lands on a valid dimension. Payment records are matched by customer and amount, with retries on both sides if a downstream call fails.

A real-world example

A mid-sized apparel and home goods manufacturer runs SAP Business One for inventory, procurement, and accounts receivable, and sells through Shopify and a small number of partner marketplaces. Before the integration, the accounting team exported daily order summaries from Shopify and manually typed them into SAP Business One as batch invoice entries at the end of each day. Customer service had to check both systems separately to answer questions about order status, and the AR team spent hours every month reconciling the two lists of customer names. With Shopify and SAP Business One connected, orders post as draft invoices automatically within minutes of purchase, customers exist in SAP Business One with matching addresses and names, and the accounting team starts month-end close with the sales and receivables accounts already tied to the source transactions.

What you can do

Sync Shopify orders into SAP Business One as draft invoices, mapped to the correct sales account and cost center.
Create and update business partners in SAP Business One from Shopify customer records so AR and customer service see the same names and addresses.
Track payments from Shopify orders against invoices in SAP Business One to keep collections current.
Authenticate both systems securely: Shopify OAuth offline tokens and SAP Business One session tokens with automatic refresh.
Receive and verify Shopify webhooks, poll SAP Business One for data changes, and replay failed records with a full audit trail.

Questions

How does ml-connector handle the differences between Shopify orders and SAP Business One invoices?: Shopify orders become draft invoices in SAP Business One, not posted invoices, so the accounting team retains control over when financial entries are committed. The order number and customer name are mapped to SAP Business One fields, and a record in the audit trail links the two so you can trace any invoice back to its source order.
Does the integration require the SAP Business One Webhook Messenger Service to be set up?: No. ml-connector works with polling by default and does not require webhooks. If your SAP Business One admin has activated the Webhook Messenger Service, ml-connector can accept webhook events as well, but polling is the standard approach.
What happens if an order is placed in Shopify but the cost center does not exist in SAP Business One?: ml-connector validates cost centers and addresses against SAP Business One before posting. If a required dimension is missing, the order is held in the audit trail so you can add the cost center and replay the record without re-entering the order details.

Connect SAP Business One and Shopify

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started