Platform Integration

Your BigCommerce store,
connected to
everything.

Stop re-keying orders. Stop fixing stock mismatches. Stop chasing dispatch updates. Supply Lens connects BigCommerce to your ERP, warehouse and finance system — orders, fulfilment, inventory and products all automated, with full support for multi-storefront setups, B2B Edition and custom field configurations.

BigCommerce connects to
By the numbers
Real-time
Order sync speed
Webhook-driven · no polling delay
99.9%
Uptime SLA
Monitored 24/7 · alerting included
4flows
Full coverage
Orders · fulfilment · stock · products
Live order flow
BigCommerce order #BC-10482 received
2x Merino Base Layer (L) · 1x Wool Beanie · £156.00
ORDER IN
Validated and transformed
SKUs matched · customer resolved · tax £26.00
PROCESS
Unleashed SO-9014 created
Sales order confirmed · ref BC-10482
CREATED
Dispatch confirmed · tracking pushed
DHL 1234567890 → BigCommerce shipment created
SHIPPED
Stock levels updated
Merino Base Layer (L) 77→75 · Wool Beanie 203→202
STOCK
What Supply Lens handles

Four flows. Built for
BigCommerce's scale and flexibility.

BigCommerce is built for businesses that have outgrown simpler platforms. Multi-storefront, B2B Edition, custom fields and a mature API mean more capability — and more to handle correctly at the integration layer.

Order sync
BigCommerce orders are picked up via webhook at an eligible status and created as correctly structured sales orders in your ERP or IMS. Customer records are resolved or created per your defined strategy. Tax treatment, shipping lines, coupons and gift certificates all translate correctly to ERP fields. Where you operate multiple storefronts from a single BigCommerce instance, orders are routed to the correct ERP entity or warehouse based on the channel they came from. B2B Edition orders carry customer group and pricing context through to the ERP sales order.
Webhook-drivenCustomer resolutionSKU matchingTax handlingMulti-storefront routingB2B Edition supportCoupons and gift certs
Fulfilment confirmation
When an order ships from your ERP or 3PL, Supply Lens creates the BigCommerce shipment record, attaches the carrier name, tracking number and tracking URL, and moves the order to the fulfilled status. The customer receives their despatch notification. BigCommerce supports both full and partial order fulfilment — Supply Lens handles partial shipments correctly, updating the specific line items that have shipped and leaving unshipped lines in the correct pending state until they despatch separately.
BigCommerce shipment APICarrier and trackingCustomer notificationPartial fulfilmentMulti-consignment
Inventory sync
Available stock from your ERP or IMS updates BigCommerce product and variant inventory quantities. BigCommerce supports inventory tracked at the variant level and Supply Lens writes stock counts for each SKU variant independently — size, colour or any other option combination — rather than posting a single product-level figure. Where you operate multiple storefronts, channel-specific stock rules can be applied so each storefront reflects the inventory available for that specific channel's fulfilment method.
Variant-level updatesMulti-storefront stock rulesAvailable-to-sell logicBackorder handlingWarehouse mapping
Product sync
Product data from your ERP or IMS pushes to BigCommerce — names, descriptions, pricing, categories, images and custom fields all maintained from your source of truth. BigCommerce's product model supports simple products, products with options and variant combinations, and custom fields at both product and variant level. Supply Lens creates and updates all of these correctly, including linking variants to the right option values and maintaining custom field data. New products, price changes and discontinued lines flow through without manual work in BigCommerce.
Simple and variant productsOptions and combinationsCustom fieldsPricing and price listsCategoriesNew product push
Where BigCommerce integrations break

BigCommerce gives you more control.
More control means more to configure correctly.

BigCommerce's flexibility is one of its strengths — multi-storefront, B2B Edition, price lists, custom fields. Each adds something to the integration surface that a basic connector handles poorly or ignores entirely.

We have three storefronts on one BigCommerce instance and orders from each need to go to different ERP entities.

BigCommerce's multi-storefront architecture means a single store can serve multiple brands, regions or channels from one backend. Supply Lens reads the channel ID on each order and routes it to the correct ERP entity, warehouse or price list based on rules you define per channel. Stock updates flow back with per-channel availability logic applied, so each storefront shows the inventory relevant to its own fulfilment model — not a combined figure across all channels.

We use BigCommerce B2B Edition and wholesale orders are landing in our ERP at retail pricing.

BigCommerce B2B Edition adds customer groups, price lists, company accounts and buyer permissions on top of the standard store. Supply Lens reads the customer group and active price list from the B2B order context and maps them to the correct ERP customer type and price tier. Wholesale orders arrive in your ERP with the correct pricing, the correct customer account and the correct payment terms — not as DTC orders that someone has to manually adjust after the fact.

Our product variant SKUs in BigCommerce don't match our ERP codes and orders fail to sync.

BigCommerce assigns its own internal product and variant IDs and the SKU field, while available, is not always populated consistently — especially on stores migrated from other platforms. Supply Lens maintains a cross-reference between BigCommerce variant IDs and ERP product codes. Orders sync correctly regardless of SKU field consistency, mismatches are flagged immediately rather than failing silently, and the cross-reference is updated as part of ongoing maintenance when new products are added.

We use BigCommerce price lists for different customer segments and the prices in our ERP don't match what was charged.

BigCommerce price lists allow segment-specific pricing that can differ significantly from the base catalogue price. Supply Lens reads the actual line item prices recorded on the order — not the base product price — so the ERP sales order reflects exactly what the customer paid under the active price list at the time of purchase. The full price breakdown, including any price list adjustments, discount amounts and the net total, lands in the ERP correctly structured.

Getting started

Most BigCommerce integrations
are live in 2–3 days.

We ask about your storefront setup, B2B configuration and price lists upfront so there are no surprises mid-project. Once we understand your channel structure the rest moves quickly.

What you need to provide
  • BigCommerce API credentials — client ID, client secret and access token
  • Confirmation of storefront count and whether B2B Edition is active
  • ERP or WMS credentials and warehouse list
  • SKU alignment — or a mapping file if BigCommerce and ERP codes differ
  • Channel-to-ERP routing rules if running multiple storefronts
  • Customer group and price list mapping if using B2B Edition
  • A handful of sample orders covering your main order types
How we get you live
1
Scope
Credentials, storefront config, B2B setup and sample orders collected.
2
Configure
Connection built in staging. Channel routing, price list mapping and SKU cross-reference applied.
3
Test
End-to-end run with real data. Multi-storefront routing, B2B orders and partial fulfilment all validated.
4
Go live
Production activated. Monitoring on from day one.

Monitored support included for 30 days after go-live.

Ready to connect BigCommerce
to your operation?

Orders, fulfilment, stock and products — all four flows automated. Multi-storefront and B2B Edition supported. 30-day trial available.