Skip to content
E-commerce ⇄ CRM

Bigcommerce to Shopify integration — real-time, two-way sync

Keep Bigcommerce and Shopify 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 Shopify

Keep the customers and orders that Shopify and Bigcommerce share aligned in real time, so sales works from live purchase history and the store works from current account details.

Shopify holds the customer relationship: the contacts, accounts, and deals a go-to-market team works. Bigcommerce runs the buying side: who placed which order, what they bought, and where it ships. The two describe the same people and companies, and when they are connected only by exports, sales answers questions without recent orders in front of them while the store works from account details that changed weeks ago.

Stacksync links Orders, Customers, Abandoned Checkouts, Products in Shopify to Price Lists, Shipments, Products, Variants and SKUs in Bigcommerce with bi-directional, real-time sync. New customers, order activity, and corrected contact details move in whichever direction you configure, field by field, with conflicts resolved by rules you set. A record created or changed on either side shows up on the other within seconds, with no CSV exports and no nightly job.

The shared entity is the customer, matched on email or an external ID, so both systems agree on who the buyer is and the order history sits next to the relationship instead of in a separate tab.

Common use cases

  • 01 Sync orders, customers, and inventory into Postgres for operational reporting across stores.
  • 02 Keep customer records aligned between Shopify and a CRM for segmentation and lifetime-value analysis.
  • 03 Two-way sync of Products and Variants between BigCommerce and a PIM or ERP so catalog content, SKUs, and pricing stay aligned across systems.
  • 04 Write Inventory levels from a WMS or ERP onto BigCommerce Variants and SKUs so storefront availability reflects warehouse on-hand counts.

Common sync patterns

Where both keep product records: catalog and CRM products aligned

Where Shopify tracks products or line items and Bigcommerce holds the catalog, shared items are matched on SKU so quotes, deals, and orders reference the same products.

One customer identity across sales and store

A person who exists as a contact in Shopify and a buyer in Bigcommerce is kept as a single, deduplicated record, so both teams work from the same customer instead of two partial copies.

Where Bigcommerce records orders: purchase history on the account

Orders and their status from Bigcommerce appear on the matching contact or account in Shopify, so reps see what a customer has bought and what is in flight before the next conversation.

What you can sync between Bigcommerce and Shopify

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 Shopify 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 Catalog entries; often mastered in a PIM or ERP and written into Shopify. 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.
Orders V2 Orders API header, line items, and shipping/billing addresses; read into an ERP or accounting system, with status written back. Orders Purchase transactions; pushed to ERPs for fulfillment and billing, and read into databases for reporting. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Customers V3 customer accounts, customer groups, and addresses; synced two-way with a CRM so storefront and GTM records match. Customers Buyer records; matched to CRM contacts for marketing and lifetime-value analysis. 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.
Brands Catalog V3 brand records linked to products; kept aligned with a product master or PIM so brand names and pages stay consistent. ProductVariants Synced with incremental and full sync per the Stacksync docs. Brands is specific to Bigcommerce and ProductVariants to Shopify — 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. Abandoned Checkouts Synced with incremental and full sync per the Stacksync docs. Inventory is specific to Bigcommerce and Abandoned Checkouts to Shopify — 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. ProductMedias Synced with incremental and full sync per the Stacksync docs. Price Lists is specific to Bigcommerce and ProductMedias to Shopify — each maps to any object or custom field on the other side.

How changes propagate between Bigcommerce and Shopify

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 Shopify 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 Shopify through its API, with automatic retries and rate-limit backoff.

Shopify Bigcommerce Sub-second propagation

DetectionShopify notifies Stacksync of record changes through webhook events. Webhook topics per resource, with polling on updated_at as a fallback.

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.
  • Shopify: GraphQL uses a calculated query-cost budget; the REST API uses a leaky-bucket model.
What ships with Bigcommerce ⇄ Shopify

Connect Bigcommerce and Shopify for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Bigcommerce or Shopify instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Bigcommerce ⇄ Shopify 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 Shopify.

How the Bigcommerce and Shopify 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.
Bigcommerce setup guide

Shopify

Integration surface
GraphQL Admin API (primary) and REST Admin API (legacy)
Authentication
OAuth via a custom Shopify app: admin creates an app in the Shopify Dev Dashboard, enables required API scopes, sets the Stacksync redirect URL, then supplies shop name + Client ID and Client Secret to Stacksync
Change detection
Webhook topics per resource, with polling on updated_at as a fallback
Capabilities
read · write · webhooks
Rate limits
GraphQL uses a calculated query-cost budget; the REST API uses a leaky-bucket model.
Shopify setup guide
How it works

How to connect Bigcommerce to Shopify — 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.

  1. 01

    Connect your apps

    Authenticate Bigcommerce and Shopify with each platform's 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
    Shopify connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Bigcommerce and Shopify 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Bigcommerce ⇄ Shopify
    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 Shopify
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Bigcommerce and Shopify integration FAQ

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

Related integrations

Every pair below is a real-time, two-way sync. Search all 490 integrations available for Bigcommerce and Shopify.

Popular · 8 of 490
All Bigcommerce integrations All Shopify integrations Browse all integrations
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