BigCommerce
Live connector
Scale on BigCommerce.
Operate it everywhere else.
Real-time webhooks across the BigCommerce v3 API. Variants, modifiers, price lists and B2B Edition pricing flow both ways — your storefront stays the storefront.
APIBigCommerce v3 · Webhooks
SyncWebhook · 1–3s typical
EditionsStandard · Pro · Enterprise · B2B
item photo
184
#SKU-3091845 · Live
Vintage Hamilton Khaki Field Auto · 38mm · Black Dial
$429.00
listed
×4in stock
184watching
82rank
BrandHamilton
MovementAutomatic
Case38 mm · steel
Variations4 SKUs · all synced
Recent activity
−0:02
↓
Orders
order.paid
HAM-38-BLK · qty 1 · $429
−0:04
↑
Inventory
stock.update
HAM-38-BLK · 4 → 3
−0:18
↑
Inventory
price.update
OMG-SS-41 · $1,495 → $1,420
−1:42
↓
Orders
order.paid
ROL-OYS-36 · qty 1 · $612
−3:08
↑
Fulfilment
tracking.add
ORD-58821 · UPS 1Z9A…
Connector
Live · webhook-driven
Catalog
Variants + modifiers
Pricing
Price lists synced
B2B
B2B Edition supported
Multi-store
Unlimited storefronts
What actually syncs
Both directions.
Every field that matters.
Seven first-class data types across the BigCommerce v3 API and webhook scopes. No nightly export, no one-way feed.
BigCommerce
bidirectional
SalesChannelHub
BigCommerce
→
SalesChannelHub
Orders & customers
Webhook · store/order/created
SalesChannelHub
→
BigCommerce
Inventory levels
v3 · inventory/adjustments
SalesChannelHub
→
BigCommerce
Catalog & variants
v3 · catalog/products
SalesChannelHub
→
BigCommerce
Price lists
v3 · pricelists/records
SalesChannelHub
→
BigCommerce
Shipments & tracking
v3 · orders/shipments
BigCommerce
→
SalesChannelHub
Returns & refunds
Webhook · store/order/refund
BigCommerce
→
SalesChannelHub
Manual stock edits
Webhook · store/product/updated
Three things BigCommerce sellers told us
BigCommerce handles big catalogs well.
The other channels are the gap.
01
"We sell B2B on BigCommerce and B2C on a marketplace. The two never agree on stock."
One master count under both. A sale on either side decrements the other within seconds, B2B price list intact.
1–3stypical sync latency
02
"Variants with modifiers are a nightmare to keep priced correctly across channels."
Variants and modifier-driven SKUs map to one canonical record. Price lists push per customer group.
Per-groupprice lists synced
03
"Our catalog has 6,000 products. Bulk edits in the control panel time out."
Edit in the master catalogue; the v3 batch endpoints push thousands of records without a timeout.
6k+products handled
The catalog flow
Every BigCommerce field, in one form.
Pushed through the v3 API.
Variants, modifiers, custom fields, categories and price lists — managed in the master catalogue and pushed to BigCommerce in one batched call.
Product
Variants4
Custom fields23
Categories
Price lists
Modifiers
Synced 8 seconds ago
Track inventory — at variant level
Show on storefront
Apply B2B price list
BigCommerce listing #SKU-3091845 · Pushed via v3 · catalog/products · SalesChannelHub product HAM-KFA-38
Inventory sync
A stock count both B2B and B2C can trust.
When a unit sells anywhere, the new quantity hits BigCommerce through the v3 inventory API in seconds — and the right price list stays attached to the right customer group.
Variant-level tracking
Stock tracked per variant, including modifier-driven SKUs, so a 6,000-product catalog stays accurate.
Per-channel buffer
Hold units back from BigCommerce while a reorder lands — protects the B2B side from a B2C spike.
Batched writes
Updates grouped into the v3 batch endpoints — thousands of records without a control-panel timeout.
Reservations during pick
Stock decrements at allocation, not at label — no double-sells while orders sit unpicked.
Sync timeline · last 30s
2.1s avg latency
−30s−20s−10snow
BigCommerce
Amazon
Shopify
Walmart
delivered
retried
Orders & fulfilment
From order created to tracking number.
One pipeline, four steps.
Every BigCommerce order — B2B or B2C — flows through the same fulfilment pipeline as your marketplaces.
01
Order webhook lands
Webhook · store/order/created
The webhook fires on order creation. Customer, address, line items and price-list pricing captured.
02
Allocated to a warehouse
Engine · routing rules
Picks the location that satisfies all lines with the fewest splits and the lowest ship cost.
03
Picked, packed, labelled
Floor · pick + carrier
Lands on a wave pick list. Carrier rates compared, label printed, the order marked picked.
04
Shipment back to BigCommerce
v3 · orders/shipments
A shipment record with tracking is posted back; the order status updates and the customer is notified.
Order #11–13427–58821
tobias_rh · BigCommerce buyer
Paid · ready to pick
handle by Thu 6:00 PM
Item
Hamilton Khaki Field Auto · 38mm · Black
HAM-38-BLK · SKU-3091845
HAM-38-BLK · SKU-3091845
Buyer paid
$429.00
+ $0 ship · −$33.27 fees
+ $0 ship · −$33.27 fees
Ship to
Portland, OR 97211
USPS Ground Advantage · 3 day
USPS Ground Advantage · 3 day
Allocation
PDX · A2-12-3
1 unit reserved · pick wave 12:30 PM
1 unit reserved · pick wave 12:30 PM
BigCommerce-only reports
The numbers behind the catalog.
Right next to your stock count.
Fulfilment SLA, return rate, price-list coverage and catalog accuracy — surfaced as first-class widgets.
Fulfilment
On-time fulfilment
98.2%
+0.9 pts vs last 30d
Fulfilment
Avg time to ship
6.9h
target 24h
Returns
Return rate
2.4%
−0.2 pts vs last 30d
Catalog
Variants in sync
99%
1,184 of 1,196 green
Inventory
Out-of-stock SKUs
11
down from 28 last week
Pricing
Price lists in sync
100%
all 6 customer groups
What changes day one
What it looks like before
and after the connector.
BigCommerce control panel
SalesChannelHub
Stock decrement across channels
✕control panel sees one store
✓1–3 seconds · webhook
6,000-product bulk edit
✕CSV import that times out
✓batched v3 API calls
B2B + B2C price lists
✕managed by hand per group
✓pushed per customer group
Shipment + tracking
✕enter per order
✓auto · native customer email
Variants with modifiers
✕priced one at a time
✓one record · all SKUs synced
Two storefronts
✕two control panels
✓one catalogue · both stores
Setup
Three minutes from sign-in
to first synced order.
Connect via a BigCommerce API account. No app to install, no per-connection fee.
01
Create an API account
Generate a v3 API account in the BigCommerce control panel with the scopes we list. Paste the token in.
BigCommerce · API accounts
02
Connect the store
We verify the token and confirm which scopes are granted before anything syncs.
v3 · store information
03
Match existing products
We pull your catalog and match products to the master catalogue by SKU. Conflicts surfaced for review.
v3 · catalog/products
04
Register the webhooks
Order and product webhooks register automatically. Bidirectional sync from the next minute on.
v3 · webhooks
Asked before every BigCommerce seller switches
Six questions.
Honest answers.
Yes. Price lists sync per customer group, so the B2B side keeps its negotiated pricing while stock stays unified with B2C.
Variants map to variant SKUs directly. Modifier-driven SKUs are tracked at the variant level too, so stock and price stay correct across every option.
No. We use the v3 batch endpoints from our side, so a large change is a series of API calls, not a single control-panel import that stalls.
Yes. Each store connects as its own channel with its own orders, but the catalogue underneath is one record set.
Yes. We post the shipment and tracking through the v3 API, so BigCommerce sends its own shipping notification.
No. The first sync matches your live BigCommerce products to the catalogue by SKU. Matched products stay the same product — we just attach our record.
BigCommerce
·
and seven other channels, the same way.
Sell everywhere.
Manage once.
A 14-day trial, no credit card, no sales call. Connect your BigCommerce store in three minutes and watch your first order sync.
Connector · live · webhook-driven
Built by sellers · honest pricing