BigCommerce SAP Business One integration
OpusNext connects BigCommerce to SAP Business One through the Catalog and Orders APIs, with AI mapping your real B1 items, user-defined fields and price lists to BigCommerce products, customer groups and orders. Everything moves by event, within the platform API limits, in both directions. Typical go-live is 2 to 6 weeks.
What syncs between SAP B1 and BigCommerce
| Data | Direction | What it means |
|---|---|---|
| Products & options | B1 → BigCommerce | Catalogue built from your live B1 item data |
| Price lists & customer groups | B1 → BigCommerce | Each account is priced the way B1 prices it |
| Inventory by warehouse | B1 → BigCommerce | No overselling across channels |
| Orders | BigCommerce → B1 | Posted to B1 in seconds, not overnight |
| Invoices & shipments | B1 → BigCommerce | Buyers track their own orders |
Where BigCommerce projects usually go wrong
The parts that decide whether this integration ages well - and how we handle them.
BigCommerce price lists are powerful but static. Mirroring B1 special prices into them means pushing a very large number of price records, and every deal change starts another bulk update.
We keep B1 as the pricing authority and resolve the buyer price per business partner, quantity and currency, syncing only the assignments the storefront actually needs - so there is no giant price table to keep in step.
API limits are real. Plans cap requests, and a chatty connector that polls for changes burns the budget and then falls behind exactly when you are busiest.
We sync on events rather than polling and batch writes to stay inside the platform limits, so catalogue and stock updates keep up during peak trading instead of queueing.
Multi-storefront setups multiply the problem - the same catalogue sold through several channels with different pricing, currency and availability rules.
Each channel is mapped to its own B1 price list, warehouse and currency, so a single B1 can feed several storefronts without them contradicting each other.
Before you choose a BigCommerce connector
Five questions worth asking any vendor - and our answers for SAP B1.
OpusNext: Yes. Your user-defined fields are read and mapped into product data, confirmed with you rather than guessed.
OpusNext: Resolved in B1 per business partner, price list, quantity and currency, then applied to the right customer group or channel.
OpusNext: Event-driven with batched writes, deliberately designed around BigCommerce API rate limits.
OpusNext: No. We connect directly to B1 via the Service Layer or DI API - no middleware to license or host.
OpusNext: Platform and B1 upgrades are absorbed - we use the official APIs and the mapping re-checks itself when the B1 schema changes.
BigCommerce and SAP Business One - common questions
Can BigCommerce show SAP Business One customer-specific prices?+
Yes. Price is resolved in B1 for the logged-in business partner - price list, quantity breaks and currency included - and applied to that buyer.
How do you stay inside BigCommerce API rate limits?+
We sync on events instead of polling and batch writes, so updates keep flowing during peak trading rather than queueing behind a rate limit.
Can one SAP Business One feed several BigCommerce storefronts?+
Yes. Each channel is mapped to its own price list, warehouse and currency so the storefronts do not contradict each other.
Do orders reach B1 immediately?+
Yes, orders post to B1 in seconds as proper business partners and sales orders, with no overnight file.
Is stock synced per warehouse?+
Yes. Availability is synced per B1 warehouse so the store shows what is genuinely sellable.