Skip to content
E-commerce ⇄ CRM

Bigcommerce to Folk CRM integration — real-time, two-way sync

Keep Bigcommerce and Folk CRM 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 Folk CRM

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

Folk CRM 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 Notes, Reminders, People, Companies in Folk CRM 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 Push enriched contact data from a data warehouse into folk custom fields.
  • 02 Mirror folk groups into a reporting database to track pipeline and outreach coverage.
  • 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

One customer identity across sales and store

A person who exists as a contact in Folk CRM and a buyer in Bigcommerce is kept as a single, deduplicated record, so both teams work from the same customer instead of two partial copies.

Where Bigcommerce records orders: purchase history on the account

Orders and their status from Bigcommerce appear on the matching contact or account in Folk CRM, so reps see what a customer has bought and what is in flight before the next conversation.

New buyers become CRM records

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

What you can sync between Bigcommerce and Folk CRM

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 Folk CRM 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. Companies Organization records linked to people and kept aligned with billing or CS systems. Customers is specific to Bigcommerce and Companies to Folk CRM — 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. Groups Shared workspaces that organize contacts; group membership is often the field integrations act on. Categories is specific to Bigcommerce and Groups to Folk CRM — 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. Custom fields Group-scoped attributes that receive enriched or computed values from external systems. Brands is specific to Bigcommerce and Custom fields to Folk CRM — 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. Notes Free-text context attached to people and companies, readable for reporting. Inventory is specific to Bigcommerce and Notes to Folk CRM — 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. Reminders Follow-up items that can be created from external triggers. Price Lists is specific to Bigcommerce and Reminders to Folk CRM — 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. People Contact records; the primary entity synced with outreach and enrichment tools. Shipments is specific to Bigcommerce and People to Folk CRM — each maps to any object or custom field on the other side.

How changes propagate between Bigcommerce and Folk CRM

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

Folk CRM Bigcommerce Sub-second propagation

DetectionFolk CRM notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling of list endpoints as a fallback.

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.
  • Folk CRM: Subject to the platform's API rate limits.
What ships with Bigcommerce ⇄ Folk CRM

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Folk CRM

Integration surface
REST API
Authentication
API key (Bearer token)
Change detection
Webhook subscriptions for record events, with polling of list endpoints as a fallback
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's API rate limits
How it works

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

    Choose tables

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

Bigcommerce and Folk CRM 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 374 integrations available for Bigcommerce and Folk CRM.

Popular · 7 of 374
All Bigcommerce integrations All Folk CRM 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