Real-time
Real-time sync
Changes in Bigcommerce or Dun And Bradstreet instantly reflect in both systems. No stale data, no manual imports.
E-commerce ⇄ CRM
Bigcommerce to Dun And Bradstreet integration — real-time data sync
Keep Bigcommerce and Dun And Bradstreet 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 Dun And Bradstreet
Keep the customers and orders that Dun And Bradstreet and Bigcommerce share aligned in real time, so sales works from live purchase history and the store works from current account details.
Dun And Bradstreet is a read-only source: Stacksync reads its data in real time and delivers it into Bigcommerce, so Bigcommerce always reflects the current state of Dun And Bradstreet — without exports, scripts, or schedulers.
Dun And Bradstreet 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.
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 the D&B corporate family tree (parent and subsidiary DUNS) into the CRM so ABM and territory owners see full account hierarchies and roll pipeline up to the global ultimate.
- 02 Build target-account lists with Criteria Search and land the resulting DUNS plus firmographics in a database for outbound and TAM 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
Contact and address details stay consistent
An email, phone, or shipping and billing address corrected in either system updates the other, so the next order and the next outreach both use current information.
Where Dun And Bradstreet segments customers: status travels to the store record
Lifecycle stage, tier, or account owner set in Dun And Bradstreet syncs onto the customer record in Bigcommerce, so the buying side can act on how the relationship is classified.
Where both keep product records: catalog and CRM products aligned
Where Dun And Bradstreet 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.
What you can sync between Bigcommerce and Dun And Bradstreet
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 | Dun And Bradstreet objects | How this pairing syncs | |
|---|---|---|---|
| Categories Catalog V3 category tree; mapped for merchandising and kept aligned with a product master or PIM. | Monitoring Notifications Change notices for a registered portfolio of DUNS; read-only feed pulled from the notifications endpoint (retained ~60 days) or delivered as bundled push. | Categories is specific to Bigcommerce and Monitoring Notifications to Dun And Bradstreet — 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. | Company Information (Data Block) Core firmographics for a D-U-N-S Number - legal name, addresses, industry codes, employees, sales, status. Retrieved read-only via the Enrich endpoint; blocks come in levels L1-L4. | Brands is specific to Bigcommerce and Company Information (Data Block) to Dun And Bradstreet — 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. | Principals & Contacts (Data Block) Company officers, executives, and contacts tied to a D-U-N-S Number; read-only enrichment used to populate CRM contact and account-owner fields. | Inventory is specific to Bigcommerce and Principals & Contacts (Data Block) to Dun And Bradstreet — 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. | Company Hierarchy & Connections (Family Tree) Parent, subsidiary, branch, and global-ultimate DUNS relationships; read-only, used to build account hierarchies and corporate-family rollups. | Price Lists is specific to Bigcommerce and Company Hierarchy & Connections (Family Tree) to Dun And Bradstreet — 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. | Financial Strength & Risk Insight (Data Block) D&B risk and credit signals - D&B Rating, PAYDEX, Failure Score, Delinquency Score, Viability - keyed by D-U-N-S Number; read-only. | Shipments is specific to Bigcommerce and Financial Strength & Risk Insight (Data Block) to Dun And Bradstreet — 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. | Identity Resolution (Match / cleanseMatch) Sends a company name and address and returns ranked candidate DUNS with confidence codes and a MatchGrade; read-only scored match, not an exact lookup. | Products is specific to Bigcommerce and Identity Resolution (Match / cleanseMatch) to Dun And Bradstreet — each maps to any object or custom field on the other side. |
How changes propagate between Bigcommerce and Dun And Bradstreet
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 Dun And Bradstreet 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).
DeliveryDun And Bradstreet does not accept inbound record writes, so this direction carries requests rather than records: Dun And Bradstreet's output flows back as field updates on the originating Bigcommerce records.
Dun And Bradstreet Bigcommerce Interval-based propagation
DetectionStacksync polls Dun And Bradstreet for changes on an incremental schedule, reading only records changed since the previous pass. Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days).
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.
- Dun And Bradstreet: Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.
What ships with Bigcommerce ⇄ Dun And Bradstreet
Connect Bigcommerce and Dun And Bradstreet for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Bigcommerce–Dun And Bradstreet connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Bigcommerce or Dun And Bradstreet 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 Dun And Bradstreet record.
Observability
Monitoring
Track your Bigcommerce ⇄ Dun And Bradstreet 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 Dun And Bradstreet.
How the Bigcommerce and Dun And Bradstreet 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.
Dun And Bradstreet
- Integration surface
- D&B Direct+ REST API (plus.dnb.com) - capability groups for Identity Resolution (Match), Search, Enrich (Data Blocks by D-U-N-S Number), Multi-Process, Data File/Batch, and Monitoring
- Authentication
- OAuth 2.0 client-credentials: Base-auth a consumer key/secret to POST /v3/token for a bearer token; access tokens expire after 24 hours.
- Change detection
- Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days). Bundled push delivery is configured with your D&B rep; there is no standard HTTP webhook and no log-based CDC.
- Capabilities
- read
- Rate limits
- Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.
How it works
How to connect Bigcommerce to Dun And Bradstreet — 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.
- 01
Connect your apps
Authenticate Bigcommerce and Dun And Bradstreet with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Bigcommerce
connected
Dun And Bradstreet
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Bigcommerce and Dun And Bradstreet 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.
objects · Bigcommerce ⇄ Dun And BradstreetCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Bigcommerce Dun And BradstreetCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Bigcommerce and Dun And Bradstreet integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between Bigcommerce and Dun And Bradstreet — Dun And Bradstreet is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
-
Bigcommerce: 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). Dun And Bradstreet: D&B Direct+ REST API (plus.dnb.com) - capability groups for Identity Resolution (Match), Search, Enrich (Data Blocks by D-U-N-S Number), Multi-Process, Data File/Batch, and Monitoring. Authentication: OAuth 2.0 client-credentials: Base-auth a consumer key/secret to POST /v3/token for a bearer token; access tokens expire after 24 hours. Stacksync manages authentication, retries, and rate limits on both sides.
-
Dun And Bradstreet: Data is organized into Data Blocks (e.g. companyinfo, principalscontacts, hierarchyconnections, financialstrengthinsight) retrieved by D-U-N-S Number via the Enrich endpoint, and blocks are sold at levels L1-L4. Bigcommerce: BigCommerce splits its API across V2 and V3 — Orders live largely in V2 while Catalog (Products, Variants, Categories) uses V3 — so a sync must map both surfaces. Stacksync's field mapping accounts for these differences between Bigcommerce and Dun And Bradstreet without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Bigcommerce and Dun And Bradstreet records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Bigcommerce and Dun And Bradstreet connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Bigcommerce–Dun And Bradstreet integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Bigcommerce and Dun And Bradstreet. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 441 integrations available for Bigcommerce and Dun And Bradstreet.
Popular · 8 of 441
-
Bigcommerce ⇄ Zoho CRM -
Bigcommerce ⇄ Shopify -
Bigcommerce ⇄ Affinity -
Bigcommerce ⇄ 6sense -
Dun And Bradstreet ⇄ Magento -
Dun And Bradstreet ⇄ Nuorder -
Dun And Bradstreet ⇄ Shipwire -
Dun And Bradstreet ⇄ Shopware
No integrations match .
