BigCommerce — on the roadmap
BigCommerce integration for order management
Updated 2 min read
You cannot connect BigCommerce yet. It is on our roadmap, and everything below describes how OMS Pro is built to run a BigCommerce operation rather than something you can switch on today. Amazon, Flipkart, Meesho, Shopify, Shiprocket and Delhivery are ready to connect now — tell us you sell on BigCommerce and it moves up the queue.
The short answer
BigCommerce is on the OMS Pro roadmap: the connector is not built yet, so you cannot switch it on today. BigCommerce stores tend to belong to brands with larger catalogues, where variant sprawl and stock accuracy matter more than the storefront's own features. This page describes how OMS Pro is designed to handle a BigCommerce operation as a storefront platform — get in touch if you sell there and we will tell you where it sits in the queue.
- Catalogue mapped to canonical SKUs shared across every channel.
- Storefront orders in the same queue and the same warehouse workflow.
- One invoice series covering storefront and marketplace sales.
What makes BigCommerce different to operate
BigCommerce stores tend to belong to brands with larger catalogues, where variant sprawl and stock accuracy matter more than the storefront's own features. The integration's job is to keep that catalogue mapped cleanly to one set of canonical SKUs.
What the BigCommerce connector handles
- Catalogue mapped to canonical SKUs shared across every channel.
- Storefront orders in the same queue and the same warehouse workflow.
- One invoice series covering storefront and marketplace sales.
Connecting it
- 1
Authorise your BigCommerce account
Connect the account from Settings → Integrations. Each account you run on BigCommerce is added as its own connection.
- 2
Map listings to canonical SKUs
Every listing must resolve to one SKU you physically hold. Treat an unmapped listing as an error that blocks sync, not a warning.
- 3
Set opening stock from a physical count
Start from reality rather than from whatever the channel currently believes. This is the step that decides whether you trust the system in month two.
- 4
Run it one-way first
Import BigCommerce orders for a few days and confirm they behave, before enabling stock and price updates back to the channel.
- 5
Turn on sync and watch a weekend
Weekends and sale events are when lag and rate limits show up. Confirm behaviour under load, then connect your next channel.
Frequently asked questions
How are large catalogues handled?
By mapping every storefront variant to a canonical SKU once, at setup. Catalogue size is not the difficulty; duplicate or unmapped SKUs are, which is why unmapped listings should block sync rather than warn.
How do I connect BigCommerce to OMS Pro?
Not yet — BigCommerce is on the roadmap and the connector is not built. When it ships it will follow the same path as the channels already supported: authorise the account under Settings → Integrations, map every listing to a canonical SKU, set opening stock from a physical count, then run order import one-way before enabling stock updates back. Amazon, Flipkart, Meesho and Shopify are ready to connect today.
Will connecting BigCommerce change my listings?
Listing creation and content stay in BigCommerce's own seller tools. OMS Pro reads orders and product identifiers, and writes available quantity — it does not rewrite your listing content.