Skip to content
E-commerce

Connect Bigcommerce to any app with two-way sync.

Two-way sync Bigcommerce across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes
Setup guide: how Stacksync connects to Bigcommerce

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
Object catalog

What Stacksync syncs in Bigcommerce.

These objects sync between Bigcommerce and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Bigcommerce exposes them.

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.
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.
Orders
V2 Orders API header, line items, and shipping/billing addresses; read into an ERP or accounting system, with status written back.
Customers
V3 customer accounts, customer groups, and addresses; synced two-way with a CRM so storefront and GTM records match.
Categories
Catalog V3 category tree; mapped for merchandising and kept aligned with a product master or PIM.
Brands
Catalog V3 brand records linked to products; kept aligned with a product master or PIM so brand names and pages stay consistent.
Inventory
Product- or variant-level stock, plus multi-location counts via the V3 Inventory API; written from a WMS to reflect on-hand quantities.
Price Lists
V3 price lists and records driving customer-group and B2B pricing; pushed from an ERP so tiered prices stay current.
Shipments
Order shipments with tracking numbers; created in BigCommerce from a 3PL or fulfillment system as packages ship.
API surface

How Stacksync connects to Bigcommerce.

The connector runs on Bigcommerce's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
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
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.

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Supported
Bigcommerce connector documentation
What ships with Bigcommerce

Connect Bigcommerce for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every connection.

Real-time

Two-way sync

Changes in Bigcommerce instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Bigcommerce 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 record.

Observability

Monitoring

Track your Bigcommerce sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the Bigcommerce connector.

BigCommerce is the ecommerce system of record for mid-market and larger online stores, owned by ecommerce operations and store administrators. It holds the live catalog — Products, Variants, Categories, and Brands — plus Orders, Customers, customer groups, and inventory levels. Because storefront transactions and product data originate there, the ERP, PIM, WMS, and CRM around it all need to read orders and customers out of BigCommerce and write catalog, pricing, and stock back in.

  • Ecommerce operations managers
  • Store and platform administrators
  • Data engineering
  • Merchandising teams

  1. Two-way sync of Products and Variants between BigCommerce and a PIM or ERP so catalog content, SKUs, and pricing stay aligned across systems.

  2. Stream new Orders and their line items into an ERP or accounting system such as NetSuite for fulfillment, invoicing, and revenue reporting.

  3. Write Inventory levels from a WMS or ERP onto BigCommerce Variants and SKUs so storefront availability reflects warehouse on-hand counts.

  4. Sync Customers and customer groups two-way with a CRM so marketing and support see the same accounts and addresses as the storefront.

  5. Push Price Lists from an ERP into BigCommerce to drive customer-group and B2B pricing without manual catalog edits.

  6. Two-way sync of Products, Variants, and Categories between BigCommerce and a PIM or ERP so catalog content, SKUs, and pricing stay consistent; edits in either system propagate via date_modified polling or product webhooks.

All Bigcommerce integrations

Pick the system you need to keep in sync with Bigcommerce. Each page covers the sync setup, field mapping, and common workflows for that pair.

CRM · 45

ERP · 38

Database · 50

Data warehouse · 29

Accounting and finance · 17

How it works

Set up Bigcommerce in minutes, without APIs.

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.

  1. 01

    Connect your apps

    Authenticate Bigcommerce with its native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Bigcommerce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Bigcommerce objects to sync — Stacksync auto-detects the schema, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Bigcommerce
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Bigcommerce database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo

FAQ

Bigcommerce connector FAQ

What can I sync with the Bigcommerce connector?

Bigcommerce's core objects — Products, Variants and SKUs, Orders, Customers and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Bigcommerce?

Via REST Management API (V2 and V3), plus GraphQL Storefront and Admin APIs, authenticated with 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). Changes are detected as follows — 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. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Bigcommerce connector two-way?

Yes. Changes made in Bigcommerce propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a Bigcommerce integration take to set up?

Most Bigcommerce integrations go live in minutes: authenticate Bigcommerce and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Bigcommerce data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Bigcommerce data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own