Videos

Duplicate orders, stock and ERP outages in BigCommerce

0:42 · November 18, 2026 · Watch on YouTube

Short: how a BigCommerce ERP integration should handle duplicate orders, stock that can really ship, credit holds, and the hours when the ERP itself is down.

Read the full write-up: BigCommerce ERP integration

More shorts from this video

Transcript

Orders come next. Duplicates appear when a retry posts the same order twice. Every order needs an idempotency key, a durable queue, and the real ERP document number returned to the buyer. For stock, a synced on-hand quantity isn't enough. Buyers need what can ship to them, plus a soft reserve at add to cart for when sync lags. On-account orders need the credit limit, balance and holds at the moment of order, and the storefront makes no financial writes. And when the ERP is down, the store serves its last good synced state, orders queue and post when it returns, and circuit breakers keep a slow ERP from becoming a slow store.

Narration is an AI voice (Azure). The facts come from the linked write-up.