Skip to content
E-commerce ⇄ ERP

Bigcommerce to DEAR Inventory integration — real-time, two-way sync

Keep Bigcommerce and DEAR Inventory 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 DEAR Inventory

Keep the storefront in step with the back office: Bigcommerce and DEAR Inventory share products, inventory, and orders in real time, in both directions.

Bigcommerce runs the storefront and takes the orders; DEAR Inventory 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 Shipments, Products, Variants and SKUs, Orders in Bigcommerce with Assemblies / Production, Locations, Products, Stock levels in DEAR Inventory field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from DEAR Inventory, order and customer detail from Bigcommerce — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Push Price Lists from an ERP into BigCommerce to drive customer-group and B2B pricing without manual catalog edits.
  • 02 Two-way sync of Products and Variants between BigCommerce and a PIM or ERP so catalog content, SKUs, and pricing stay aligned across systems.
  • 03 Push sale orders from a storefront or CRM into DEAR for fulfillment without manual re-entry.
  • 04 Land orders, costs, and inventory movements in a warehouse for margin and stock-turn reporting.

Common sync patterns

One customer master

Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.

Where DEAR Inventory is the inventory system of record: stock stays accurate

Available quantities from DEAR Inventory 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 DEAR Inventory with customer, line items, and totals, so fulfillment and invoicing start without re-entry.

What you can sync between Bigcommerce and DEAR Inventory

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 DEAR Inventory 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 pricing, suppliers, and bill-of-material links; the master data most syncs start from. 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.
Customers V3 customer accounts, customer groups, and addresses; synced two-way with a CRM so storefront and GTM records match. Customers Buyer records aligned with CRM and accounting counterparts. 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.
Shipments Order shipments with tracking numbers; created in BigCommerce from a 3PL or fulfillment system as packages ship. Suppliers Vendor records referenced on purchase orders. Shipments is specific to Bigcommerce and Suppliers to DEAR Inventory — 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. Stock adjustments and transfers Inventory movement transactions that explain changes in availability. Variants and SKUs is specific to Bigcommerce and Stock adjustments and transfers to DEAR Inventory — 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. Assemblies / Production Bill-of-material and production records for light manufacturing workflows. Orders is specific to Bigcommerce and Assemblies / Production to DEAR Inventory — 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. Locations Warehouses and bins that scope stock levels and fulfillment. Categories is specific to Bigcommerce and Locations to DEAR Inventory — each maps to any object or custom field on the other side.

How changes propagate between Bigcommerce and DEAR Inventory

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

DEAR Inventory Bigcommerce Sub-second propagation

DetectionDEAR Inventory notifies Stacksync of record changes through webhook events. Polling with modified-since 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.
  • DEAR Inventory: Subject to the platform's per-account API rate limits.
What ships with Bigcommerce ⇄ DEAR Inventory

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

DEAR Inventory

Integration surface
REST API
Authentication
Account ID plus application key sent as request headers
Change detection
Polling with modified-since filters; webhook notifications for sale and purchase events are available on subscriptions that include the Automation module
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's per-account API rate limits
How it works

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

    Choose tables

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

Bigcommerce and DEAR Inventory 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 366 integrations available for Bigcommerce and DEAR Inventory.

Popular · 7 of 366
All Bigcommerce integrations All DEAR Inventory 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