Real-time
Two-way sync
Changes in Bigcommerce or Linnworks instantly reflect in both systems. No stale data, no manual imports.
E-commerce ⇄ ERP
Bigcommerce to Linnworks integration — real-time, two-way sync
Keep Bigcommerce and Linnworks in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Bigcommerce and Linnworks
Keep the storefront in step with the back office: Bigcommerce and Linnworks share products, inventory, and orders in real time, in both directions.
Bigcommerce runs the storefront and takes the orders; Linnworks owns the item master, the stock on hand, and the finance behind every transaction. The two overlap wherever the same products, customers, and sales matter to both — and when re-keying or an overnight batch is what connects them, the store oversells items it can't ship, quotes prices finance never set, or leaves buyers waiting on status that already changed.
Stacksync syncs Variants and SKUs, Orders, Customers, Categories in Bigcommerce with Locations, Purchase Orders, Suppliers, Channel Listings in Linnworks field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Linnworks, order and customer detail from Bigcommerce — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Push Price Lists from an ERP into BigCommerce to drive customer-group and B2B pricing without manual catalog edits.
- 02 Two-way sync of Products and Variants between BigCommerce and a PIM or ERP so catalog content, SKUs, and pricing stay aligned across systems.
- 03 Push customer and order data to a CRM or marketing platform for post-purchase campaigns
- 04 Sync orders from Linnworks into an ERP or accounting system as they are processed, without CSV exports
Common sync patterns
One product catalog
Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.
Fulfillment and shipment status close the loop
As orders are picked, shipped, or invoiced in Linnworks, tracking and status flow back to Bigcommerce so buyers see accurate updates.
One customer master
Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.
What you can sync between Bigcommerce and Linnworks
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Bigcommerce objects | Linnworks objects | How this pairing syncs | |
|---|---|---|---|
| Customers V3 customer accounts, customer groups, and addresses; synced two-way with a CRM so storefront and GTM records match. | Shipping Services Carrier and service definitions support label and tracking data in order syncs. | Customers is specific to Bigcommerce and Shipping Services to Linnworks — each maps to any object or custom field on the other side. | |
| Categories Catalog V3 category tree; mapped for merchandising and kept aligned with a product master or PIM. | Open Orders Unshipped orders aggregated from sales channels sync into ERPs and fulfillment systems. | Categories is specific to Bigcommerce and Open Orders to Linnworks — each maps to any object or custom field on the other side. | |
| Brands Catalog V3 brand records linked to products; kept aligned with a product master or PIM so brand names and pages stay consistent. | Processed Orders Completed orders feed accounting and warehouse-based margin reporting. | Brands is specific to Bigcommerce and Processed Orders to Linnworks — each maps to any object or custom field on the other side. | |
| Inventory Product- or variant-level stock, plus multi-location counts via the V3 Inventory API; written from a WMS to reflect on-hand quantities. | Stock Items SKU records keep product data aligned with ERPs and PIMs. | Inventory is specific to Bigcommerce and Stock Items to Linnworks — each maps to any object or custom field on the other side. | |
| Price Lists V3 price lists and records driving customer-group and B2B pricing; pushed from an ERP so tiered prices stay current. | Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. | Price Lists is specific to Bigcommerce and Stock Levels to Linnworks — each maps to any object or custom field on the other side. | |
| Shipments Order shipments with tracking numbers; created in BigCommerce from a 3PL or fulfillment system as packages ship. | Locations Warehouse and fulfillment location records scope stock data during mapping. | Shipments is specific to Bigcommerce and Locations to Linnworks — each maps to any object or custom field on the other side. |
How changes propagate between Bigcommerce and Linnworks
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Bigcommerce Linnworks Sub-second propagation
DetectionBigcommerce notifies Stacksync of record changes through webhook events. Webhooks push near-real-time events (store/order/*, store/product/*, store/customer/* and more).
DeliveryEach detected change is written to Linnworks through its API, with automatic retries and rate-limit backoff.
Linnworks Bigcommerce Interval-based propagation
DetectionStacksync polls Linnworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling on order and stock endpoints.
DeliveryEach detected change is written to Bigcommerce through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Bigcommerce: OAuth quota refreshes every 30 seconds and varies by plan (about 20,000 requests/hour on Standard and Plus, 60,000 on Pro, higher on Enterprise); the X-Rate-Limit-Requests-Left header reports remaining calls.
- Linnworks: Per-endpoint rate limits apply on the Linnworks API.
What ships with Bigcommerce ⇄ Linnworks
Connect Bigcommerce and Linnworks for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Bigcommerce–Linnworks connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Bigcommerce or Linnworks data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Bigcommerce or Linnworks record.
Observability
Monitoring
Track your Bigcommerce ⇄ Linnworks sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Bigcommerce and Linnworks.
How the Bigcommerce and Linnworks connectors work
Bigcommerce
- Integration surface
- REST Management API (V2 and V3), plus GraphQL Storefront and Admin APIs
- Authentication
- OAuth API account credentials — a store-generated client ID and permanent access token sent in the X-Auth-Token header, limited to the OAuth scopes granted when the account is created (e.g. store_v2_orders, store_v2_products)
- Change detection
- Webhooks push near-real-time events (store/order/*, store/product/*, store/customer/* and more); polling uses date_modified:min/max filters on Products, Orders, and Customers
- Capabilities
- read · write · webhooks
- Rate limits
- OAuth quota refreshes every 30 seconds and varies by plan (about 20,000 requests/hour on Standard and Plus, 60,000 on Pro, higher on Enterprise); the X-Rate-Limit-Requests-Left header reports remaining calls.
Linnworks
- Integration surface
- REST API
- Authentication
- Application credentials and an install token exchanged for a session token
- Change detection
- Polling on order and stock endpoints
- Capabilities
- read · write
- Rate limits
- Per-endpoint rate limits apply on the Linnworks API
How it works
How to connect Bigcommerce to Linnworks — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Bigcommerce and Linnworks with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Bigcommerce
connected
Linnworks
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Bigcommerce and Linnworks objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Bigcommerce ⇄ LinnworksCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Bigcommerce LinnworksCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Bigcommerce and Linnworks integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Bigcommerce and Linnworks: authenticate both systems, choose the objects to sync (such as Bigcommerce's Customers and Categories), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Bigcommerce and Linnworks. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Bigcommerce: Webhooks push near-real-time events (store/order/*, store/product/*, store/customer/* and more); polling uses date_modified:min/max filters on Products, Orders, and Customers. On Linnworks: Polling on order and stock endpoints. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Bigcommerce side: Variants and SKUs, Orders, Customers, Categories, plus custom fields where Bigcommerce exposes them. On the Linnworks side: Locations, Purchase Orders, Suppliers, Channel Listings. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Bigcommerce and Linnworks: One product catalog; Fulfillment and shipment status close the loop; One customer master. Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 462 integrations available for Bigcommerce and Linnworks.
Popular · 7 of 462
-
Bigcommerce ⇄ Sage Intacct - Bigcommerce ⇄ Sage X3
-
Bigcommerce ⇄ SAP -
Linnworks ⇄ Shopware -
Linnworks ⇄ Akeneo -
Linnworks ⇄ Channelengine -
Linnworks ⇄ Easypost
No integrations match .
