Skip to content
E-commerce ⇄ CRM

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

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

Keep the customers and orders that Close and Bigcommerce share aligned in real time, so sales works from live purchase history and the store works from current account details.

Close 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.

Stacksync links Contacts, Opportunities, Activities, Tasks in Close to Categories, Brands, Inventory, Price Lists in Bigcommerce with bi-directional, real-time sync. New customers, order activity, and corrected contact details move in whichever direction you configure, field by field, with conflicts resolved by rules you set. A record created or changed on either side shows up on the other within seconds, with no CSV exports and no nightly job.

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 Write product usage or firmographic data from an internal database onto Close lead custom fields to prioritize follow-up.
  • 02 Sync Close leads and opportunities into Postgres or a warehouse for pipeline reporting outside Close's built-in reports.
  • 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

New buyers become CRM records

A customer created in Bigcommerce creates or updates the matching contact or account in Close, so first-time and repeat buyers land in the relationship system without a manual import.

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 Close segments customers: status travels to the store record

Lifecycle stage, tier, or account owner set in Close syncs onto the customer record in Bigcommerce, so the buying side can act on how the relationship is classified.

What you can sync between Bigcommerce and Close

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 Close objects How this pairing syncs
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. Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. Variants and SKUs is specific to Bigcommerce and Custom Activities to Close — 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. Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. Orders is specific to Bigcommerce and Custom Fields to Close — 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. Users Sales reps referenced as owners on leads, opportunities, and activities. Customers is specific to Bigcommerce and Users to Close — 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. Smart Views Saved lead searches that can scope which records a segment-based sync pulls. Categories is specific to Bigcommerce and Smart Views to Close — 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. Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. Brands is specific to Bigcommerce and Leads to Close — 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. Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. Inventory is specific to Bigcommerce and Contacts to Close — each maps to any object or custom field on the other side.

How changes propagate between Bigcommerce and Close

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

Close Bigcommerce Sub-second propagation

DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.

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.
  • Close: Subject to per-endpoint rate limits communicated in response headers.
What ships with Bigcommerce ⇄ Close

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Close

Integration surface
REST API
Authentication
API key (sent via HTTP Basic auth)
Change detection
Webhook subscriptions for record events, with polling on date_updated fields for backfills
Capabilities
read · write · webhooks
Rate limits
Subject to per-endpoint rate limits communicated in response headers
How it works

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

    Choose tables

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

Bigcommerce and Close 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 487 integrations available for Bigcommerce and Close.

Popular · 8 of 487
All Bigcommerce integrations All Close 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