Skip to content
E-commerce ⇄ Database

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

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

Give your engineers Bigcommerce's products, orders, and customers in Citus: read them with normal queries, write inventory and prices back through the sync, and skip the storefront API.

E-commerce data sits behind an API built for the storefront, not for your internal systems. Teams that need those records, for order routing, inventory logic, reporting, or back-office tools, end up writing integration code against a rate-limited API and maintaining it through every catalog change and platform upgrade.

Stacksync mirrors Price Lists, Shipments, Products, Variants and SKUs from Bigcommerce into Citus and keeps both sides consistent in real time. Whatever Bigcommerce holds, whether products, orders, customers, or inventory, those records become rows your code can query, and changes written in Citus, such as new prices, stock levels, or fulfillment status, sync back into Bigcommerce with its validations respected.

Merchandising and operations keep working in the storefront, engineers keep working in the database, and neither side has to reconcile against a nightly export.

Common use cases

  • 01 Consolidate per-tenant rows from distributed tables into per-customer reporting databases.
  • 02 Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
  • 03 Write Inventory levels from a WMS or ERP onto BigCommerce Variants and SKUs so storefront availability reflects warehouse on-hand counts.
  • 04 Sync Customers and customer groups two-way with a CRM so marketing and support see the same accounts and addresses as the storefront.

Common sync patterns

Controlled write-back

Choose exactly which tables and fields may flow from Citus back into Bigcommerce, keeping the store authoritative on what it owns.

Read the store's data with a query

Records from Bigcommerce, whether products, orders, customers, or inventory, live in Citus as ordinary tables or collections, joinable with the rest of your data.

Internal tools and automations without API code

Scripts and services read and write the synced tables; Stacksync handles the Bigcommerce API, rate limits, and retries.

What you can sync between Bigcommerce and Citus

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 Citus objects How this pairing syncs
Shipments Order shipments with tracking numbers; created in BigCommerce from a 3PL or fulfillment system as packages ship. Sequences Key generators that matter when external writes must not collide with application inserts. Shipments is specific to Bigcommerce and Sequences to Citus — each maps to any object or custom field on the other side.
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. Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. Products is specific to Bigcommerce and Distributed tables to Citus — each maps to any object or custom field on the other side.
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. Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. Variants and SKUs is specific to Bigcommerce and Reference tables to Citus — 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. Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. Orders is specific to Bigcommerce and Local tables to Citus — 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. Schemas Standard Postgres namespaces used to scope what a sync user can read and write. Customers is specific to Bigcommerce and Schemas to Citus — 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. Views Curated projections over distributed data, often used as read-only sync sources. Categories is specific to Bigcommerce and Views to Citus — each maps to any object or custom field on the other side.

How changes propagate between Bigcommerce and Citus

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 Citus 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 applied to Citus as a row-level write, with types converted between the two schemas.

Citus Bigcommerce Sub-second propagation

DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.

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.
What ships with Bigcommerce ⇄ Citus

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

How the Bigcommerce and Citus 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

Citus

Integration surface
PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
Authentication
Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
Change detection
PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
Capabilities
read · write · CDC
How it works

How to connect Bigcommerce to Citus — 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 Citus 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
    Citus connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Bigcommerce and Citus 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 ⇄ Citus
    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 Citus
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Bigcommerce and Citus 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 390 integrations available for Bigcommerce and Citus.

Popular · 7 of 390
All Bigcommerce integrations All Citus 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