Real-time
Two-way sync
Changes in Bigcommerce or Cin7 instantly reflect in both systems. No stale data, no manual imports.
E-commerce ⇄ ERP
Bigcommerce to Cin7 integration — real-time, two-way sync
Keep Bigcommerce and Cin7 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 Cin7
Keep the storefront in step with the back office: Bigcommerce and Cin7 share products, inventory, and orders in real time, in both directions.
Bigcommerce runs the storefront and takes the orders; Cin7 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 Customers, Categories, Brands, Inventory in Bigcommerce with Products, Inventory levels, Sales orders, Purchase orders in Cin7 field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Cin7, order and customer detail from Bigcommerce — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Two-way sync of Products and Variants between BigCommerce and a PIM or ERP so catalog content, SKUs, and pricing stay aligned across systems.
- 02 Write Inventory levels from a WMS or ERP onto BigCommerce Variants and SKUs so storefront availability reflects warehouse on-hand counts.
- 03 Publish Cin7 inventory levels to storefronts, marketplaces, and a CRM so every channel quotes real availability.
- 04 Sync sales orders from Cin7 into an accounting platform or warehouse for revenue and margin reporting.
Common sync patterns
Where Cin7 is the inventory system of record: stock stays accurate
Available quantities from Cin7 publish to Bigcommerce, so the store shows what can actually ship and stops overselling.
New orders reach the back office
An order captured in Bigcommerce creates the matching record in Cin7 with customer, line items, and totals, so fulfillment and invoicing start without re-entry.
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.
What you can sync between Bigcommerce and Cin7
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 | Cin7 objects | How this pairing syncs | |
|---|---|---|---|
| Products Catalog V3 records with custom fields and images; mastered in a PIM or ERP and written to BigCommerce, or read out to a warehouse. | Products SKU records with options and pricing, synced with storefront and marketplace catalogs. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Variants and SKUs Per-variant pricing and inventory; synced to keep stock and SKU data aligned with an ERP or WMS at the option level. | Contacts Customers and suppliers, matched to CRM records to keep account data consistent. | Variants and SKUs is specific to Bigcommerce and Contacts to Cin7 — each maps to any object or custom field on the other side. | |
| Orders V2 Orders API header, line items, and shipping/billing addresses; read into an ERP or accounting system, with status written back. | Branches / locations Warehouse entities that scope every stock movement and order allocation. | Orders is specific to Bigcommerce and Branches / locations to Cin7 — each maps to any object or custom field on the other side. | |
| Customers V3 customer accounts, customer groups, and addresses; synced two-way with a CRM so storefront and GTM records match. | Stock adjustments and transfers Inventory movements read for audit and reconciliation reporting. | Customers is specific to Bigcommerce and Stock adjustments and transfers to Cin7 — 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. | Credit notes / returns Return documents synced so finance and support see the same refund state. | Categories is specific to Bigcommerce and Credit notes / returns to Cin7 — 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. | Inventory levels Stock on hand by branch or location, published outward for availability. | Brands is specific to Bigcommerce and Inventory levels to Cin7 — each maps to any object or custom field on the other side. |
How changes propagate between Bigcommerce and Cin7
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 Cin7 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 Cin7 through its API, with automatic retries and rate-limit backoff.
Cin7 Bigcommerce Sub-second propagation
DetectionCin7 notifies Stacksync of record changes through webhook events. Polling on modified-date filters.
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.
- Cin7: Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core.
What ships with Bigcommerce ⇄ Cin7
Connect Bigcommerce and Cin7 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Bigcommerce–Cin7 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Bigcommerce or Cin7 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 Cin7 record.
Observability
Monitoring
Track your Bigcommerce ⇄ Cin7 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 Cin7.
How the Bigcommerce and Cin7 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.
Cin7
- Integration surface
- REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs
- Authentication
- API key credentials (paired with a username or account ID, depending on the product)
- Change detection
- Polling on modified-date filters; webhook support exists on some editions for order and stock events
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core
How it works
How to connect Bigcommerce to Cin7 — 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 Cin7 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
Cin7
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Bigcommerce and Cin7 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 ⇄ Cin7Customers 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 Cin7Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Bigcommerce and Cin7 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Bigcommerce and Cin7: authenticate both systems, choose the objects to sync (such as Bigcommerce's Products and Variants and SKUs), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Bigcommerce and Cin7. 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 Cin7: Polling on modified-date filters; webhook support exists on some editions for order and stock events. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Bigcommerce side: Customers, Categories, Brands, Inventory, plus custom fields where Bigcommerce exposes them. On the Cin7 side: Products, Inventory levels, Sales orders, Purchase orders. 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 Cin7: Where Cin7 is the inventory system of record: stock stays accurate; New orders reach the back office; One product catalog. Available quantities from Cin7 publish to Bigcommerce, so the store shows what can actually ship and stops overselling.
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 458 integrations available for Bigcommerce and Cin7.
Popular · 5 of 458
No integrations match .
