Skip to content
E-commerce ⇄ Database

Bigcommerce to Dynamo DB integration — real-time, two-way sync

Keep Bigcommerce and Dynamo DB 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 Dynamo DB

Give your engineers Bigcommerce's products, orders, and customers in Dynamo DB: 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 Shipments, Products, Variants and SKUs, Orders from Bigcommerce into Dynamo DB 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 Dynamo DB, 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 Stream item changes from DynamoDB application tables into a Postgres or warehouse copy for SQL analytics.
  • 02 Sync customer records between DynamoDB-backed services and a CRM so support and sales see live application state.
  • 03 Sync Customers and customer groups two-way with a CRM so marketing and support see the same accounts and addresses as the storefront.
  • 04 Push Price Lists from an ERP into BigCommerce to drive customer-group and B2B pricing without manual catalog edits.

Common sync patterns

React to store changes

Updates in Bigcommerce arrive as row changes in Dynamo DB, so jobs and triggers can respond the moment an order, price, or stock level changes.

Keep catalog and inventory current

Prices, stock levels, or product details maintained in Dynamo DB sync back onto Bigcommerce, so the storefront shows what your systems treat as true.

Order data where your code can use it

Orders and their status become rows in Dynamo DB for routing, fulfillment, and reporting, without polling the platform.

What you can sync between Bigcommerce and Dynamo DB

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 Dynamo DB objects How this pairing syncs
Categories Catalog V3 category tree; mapped for merchandising and kept aligned with a product master or PIM. Global Secondary Indexes Alternate access paths used when sync queries filter on non-key attributes. Categories is specific to Bigcommerce and Global Secondary Indexes to Dynamo DB — 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. DynamoDB Streams Ordered item-level change records consumed for incremental sync. Brands is specific to Bigcommerce and DynamoDB Streams to Dynamo DB — 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. Global Tables Multi-region replicas relevant when syncs must read from a specific region. Inventory is specific to Bigcommerce and Global Tables to Dynamo DB — 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. Tables The top-level containers a sync targets; each table is addressed independently. Price Lists is specific to Bigcommerce and Tables to Dynamo DB — 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. Items Schemaless records keyed by partition (and optional sort) key, mapped to rows or SaaS objects in syncs. Shipments is specific to Bigcommerce and Items to Dynamo DB — 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. Attributes Per-item fields, including nested maps and lists, flattened or mapped during sync. Products is specific to Bigcommerce and Attributes to Dynamo DB — each maps to any object or custom field on the other side.

How changes propagate between Bigcommerce and Dynamo DB

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

Dynamo DB Bigcommerce Sub-second propagation

DetectionChanges in Dynamo DB are captured at the source via change data capture — no polling loop against its API. Item-level change streams via DynamoDB Streams or Kinesis Data Streams integration.

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.
  • Dynamo DB: Throughput is governed by the table's provisioned or on-demand capacity mode.
What ships with Bigcommerce ⇄ Dynamo DB

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Dynamo DB

Integration surface
Proprietary JSON-over-HTTPS API accessed through AWS SDKs; PartiQL supported for SQL-like queries
Authentication
AWS IAM credentials with SigV4 request signing
Change detection
Item-level change streams via DynamoDB Streams or Kinesis Data Streams integration
Capabilities
read · write · CDC
Rate limits
Throughput is governed by the table's provisioned or on-demand capacity mode
How it works

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

    Choose tables

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

Bigcommerce and Dynamo DB 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 408 integrations available for Bigcommerce and Dynamo DB.

Popular · 7 of 408
All Bigcommerce integrations All Dynamo DB 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