Skip to content
E-commerce ⇄ ERP

Bigcommerce to Dynamics 365 F&O integration — real-time, two-way sync

Keep Bigcommerce and Dynamics 365 F&O 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 Dynamics 365 F&O

Keep the storefront in step with the back office: Bigcommerce and Dynamics 365 F&O share products, inventory, and orders in real time, in both directions.

Bigcommerce runs the storefront and takes the orders; Dynamics 365 F&O 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 Customer Invoices, Vendor Invoices, General Journal Entries, On-hand Inventory in Dynamics 365 F&O field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Dynamics 365 F&O, order and customer detail from Bigcommerce — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Sync Customers and customer groups two-way with a CRM so marketing and support see the same accounts and addresses as the storefront.
  • 02 Push Price Lists from an ERP into BigCommerce to drive customer-group and B2B pricing without manual catalog edits.
  • 03 Push sales orders from e-commerce into F&O and sync fulfillment and invoice status back to the storefront.
  • 04 Mirror GL journals and invoice lines into a warehouse for finance reporting without recurring DMF exports.

Common sync patterns

Fulfillment and shipment status close the loop

As orders are picked, shipped, or invoiced in Dynamics 365 F&O, tracking and status flow back to Bigcommerce so buyers see accurate updates.

One customer master

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

Where Dynamics 365 F&O is the inventory system of record: stock stays accurate

Available quantities from Dynamics 365 F&O publish to Bigcommerce, so the store shows what can actually ship and stops overselling.

What you can sync between Bigcommerce and Dynamics 365 F&O

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 Dynamics 365 F&O objects How this pairing syncs
Customers V3 customer accounts, customer groups, and addresses; synced two-way with a CRM so storefront and GTM records match. Customers Customer master records; kept aligned with CRM accounts in two-way syncs. 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.
Price Lists V3 price lists and records driving customer-group and B2B pricing; pushed from an ERP so tiered prices stay current. On-hand Inventory Stock positions; read out to storefronts and internal apps for availability. Price Lists is specific to Bigcommerce and On-hand Inventory to Dynamics 365 F&O — 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. Vendors Supplier master records; synced with procurement and AP tools. Shipments is specific to Bigcommerce and Vendors to Dynamics 365 F&O — 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. Released Products Sellable product master; read out to commerce channels and CRM catalogs. Products is specific to Bigcommerce and Released Products to Dynamics 365 F&O — 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. Sales Orders Order transactions; written in from storefronts or CRM and tracked through fulfillment. Variants and SKUs is specific to Bigcommerce and Sales Orders to Dynamics 365 F&O — 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. Purchase Orders Procurement transactions; extracted for spend and supply chain reporting. Orders is specific to Bigcommerce and Purchase Orders to Dynamics 365 F&O — each maps to any object or custom field on the other side.

How changes propagate between Bigcommerce and Dynamics 365 F&O

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 Dynamics 365 F&O 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 Dynamics 365 F&O through its API, with automatic retries and rate-limit backoff.

Dynamics 365 F&O Bigcommerce Sub-second propagation

DetectionDynamics 365 F&O pushes changes as they happen — webhook events backed by change data capture. Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity.

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.
  • Dynamics 365 F&O: OData requests are subject to platform throttling; high-volume loads belong in the Data Management Framework.
What ships with Bigcommerce ⇄ Dynamics 365 F&O

Connect Bigcommerce and Dynamics 365 F&O for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Bigcommerce–Dynamics 365 F&O connection.

Real-time

Two-way sync

Changes in Bigcommerce or Dynamics 365 F&O instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Bigcommerce or Dynamics 365 F&O 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 Dynamics 365 F&O record.

Observability

Monitoring

Track your Bigcommerce ⇄ Dynamics 365 F&O 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 Dynamics 365 F&O.

How the Bigcommerce and Dynamics 365 F&O 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

Dynamics 365 F&O

Integration surface
OData REST endpoint over data entities, plus the Data Management Framework for batch
Authentication
OAuth via Microsoft sign-in: provide the D365 F&O environment URL, sign in with Microsoft credentials, and grant the Stacksync app consent (admin consent may be required — "Need admin approval for this app")
Change detection
Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity; falls back to periodic full-sync where change tracking is unavailable
Capabilities
read · write · CDC · webhooks
Rate limits
OData requests are subject to platform throttling; high-volume loads belong in the Data Management Framework.
Dynamics 365 F&O setup guide
How it works

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

    Choose tables

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

Bigcommerce and Dynamics 365 F&O 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 372 integrations available for Bigcommerce and Dynamics 365 F&O.

Popular · 7 of 372
All Bigcommerce integrations All Dynamics 365 F&O 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