SAP Business One and BigCommerce integration

What moves between them

The main flow runs from BigCommerce into SAP Business One. ml-connector reads storefront orders and the payment transactions captured against them and posts them into SAP Business One as sales invoices and incoming payments, mapped to the matching item codes, business partners, and accounts. Customer records flow the same direction so the SAP Business One business partner master reflects BigCommerce shoppers as CardType C partners. Product references are aligned so each order line resolves to a real SAP Business One item code, and item stock levels flow the other way from SAP Business One into the BigCommerce catalog so listings show accurate inventory. The general ledger stays in SAP Business One, since BigCommerce has no GL resource, so ml-connector never writes ledger entries back to the store.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the BigCommerce side it sends the static X-Auth-Token on every request, scoped to the store hash, and on the SAP Business One side it accepts the full Service Layer base URL per customer, logs in once to obtain a B1SESSION cookie, and reuses that cookie rather than authenticating per request because the first login carries a cold-start cost of several seconds. When the Service Layer returns error code -5002 on session timeout, ml-connector re-logs in and replays the request. Item codes and business partners are mapped first, so every order line references an SAP Business One item and a customer that already exist. BigCommerce webhooks arrive signed with HMAC-SHA256, so each notification is verified before processing, and because payloads are stubs ml-connector immediately calls back to fetch the full order and its transactions. Neither side offers an idempotency key, so inbound webhooks are deduplicated on a BullMQ jobId and writes check for an existing DocNum before posting, which avoids double-booking a re-read order. SAP Business One is usually on a private network, so it may require a VPN or reverse proxy and sometimes a custom CA for a self-signed certificate. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized consumer goods maker with around 80 staff runs SAP Business One for inventory, finance, and purchasing, and sells direct to shoppers through a BigCommerce store. Before the integration, a clerk exported web orders from BigCommerce each morning and keyed them into SAP Business One by hand, which meant orders sat for hours, SKUs were sometimes typed wrong, and the storefront kept selling items that were already out of stock in the warehouse. With SAP Business One and BigCommerce connected, each order and its captured payment flow into SAP Business One within the polling window, allocated to the right customer and item code, and warehouse stock levels push back to the catalog so the listings stay accurate. Orders are invoiced sooner, the keying errors are gone, and oversells stop.

What you can do

• •Post BigCommerce orders and captured payment transactions into SAP Business One as sales invoices and incoming payments.
• •Map BigCommerce SKUs to SAP Business One item codes so every order line lands on a real product.
• •Keep the SAP Business One business partner master aligned with BigCommerce shoppers as CardType C customers.
• •Push SAP Business One item stock levels into the BigCommerce catalog so storefront inventory stays accurate.
• •Bridge the BigCommerce X-Auth-Token and the SAP Business One session login, with retries and a full audit trail on every record.

Questions

Which direction does data move between SAP Business One and BigCommerce?

The main flow is BigCommerce into SAP Business One. Orders, payment transactions, and customer records move from BigCommerce into SAP Business One, while item stock levels move the other way so the storefront catalog reflects warehouse inventory. BigCommerce has no chart of accounts, so the general ledger stays in SAP Business One and ml-connector never writes ledger entries back to the store.

Does ml-connector use BigCommerce webhooks or polling for SAP Business One?

It uses both, matched to each system. BigCommerce pushes signed HMAC-SHA256 webhooks for order and inventory events, which ml-connector verifies and then follows with a callback because each payload carries only a resource type and ID. SAP Business One webhooks require server-side admin setup and are not always available, so SAP Business One records are read by polling the Service Layer on a schedule you control.

How does the integration handle the SAP Business One session and lack of idempotency keys?

ml-connector logs in once to get a B1SESSION cookie and reuses it across requests, re-authenticating and replaying the call when the Service Layer returns error code -5002 on timeout. Since neither system exposes an idempotency key, inbound webhooks are deduplicated on a BullMQ jobId and each write checks for an existing DocNum first, so a re-read BigCommerce order is never booked twice in SAP Business One.