Real-time
Two-way sync
Changes in Bigcommerce or Kommo instantly reflect in both systems. No stale data, no manual imports.
E-commerce ⇄ CRM
Bigcommerce to Kommo integration — real-time, two-way sync
Keep Bigcommerce and Kommo 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 Kommo
Keep the customers and orders that Kommo and Bigcommerce share aligned in real time, so sales works from live purchase history and the store works from current account details.
Kommo 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 Companies, Pipelines & Statuses, Tasks, Notes in Kommo to Products, Variants and SKUs, Orders, Customers 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 web form and product signups into Kommo pipelines as they are submitted so messenger-based follow-up starts quickly
- 02 Keep customer records consistent between Kommo and invoicing or ERP systems
- 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 Kommo segments customers: status travels to the store record
Lifecycle stage, tier, or account owner set in Kommo 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 Kommo 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 Kommo
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 | Kommo objects | How this pairing syncs | |
|---|---|---|---|
| Categories Catalog V3 category tree; mapped for merchandising and kept aligned with a product master or PIM. | Custom Fields Per-entity custom fields hold data written from external databases and enrichment. | Categories is specific to Bigcommerce and Custom Fields to Kommo — 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. | Users Account users map lead ownership to people in other systems. | Brands is specific to Bigcommerce and Users to Kommo — 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. | Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. | Inventory is specific to Bigcommerce and Chats to Kommo — 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. | Leads The central pipeline record; external signups and form fills sync in as leads. | Price Lists is specific to Bigcommerce and Leads to Kommo — 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. | Contacts Person records sync with other CRMs and databases for a shared contact file. | Shipments is specific to Bigcommerce and Contacts to Kommo — 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. | Companies Organization records map to accounts in ERPs and invoicing tools. | Products is specific to Bigcommerce and Companies to Kommo — each maps to any object or custom field on the other side. |
How changes propagate between Bigcommerce and Kommo
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 Kommo 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 Kommo through its API, with automatic retries and rate-limit backoff.
Kommo Bigcommerce Sub-second propagation
DetectionKommo notifies Stacksync of record changes through webhook events. Webhooks on record add and update events, plus polling for backfill.
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.
- Kommo: Subject to per-account request rate limits.
What ships with Bigcommerce ⇄ Kommo
Connect Bigcommerce and Kommo for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Bigcommerce–Kommo connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Bigcommerce or Kommo 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 Kommo record.
Observability
Monitoring
Track your Bigcommerce ⇄ Kommo 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 Kommo.
How the Bigcommerce and Kommo 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.
Kommo
- Integration surface
- REST API
- Authentication
- OAuth 2.0 with refresh tokens
- Change detection
- Webhooks on record add and update events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account request rate limits
How it works
How to connect Bigcommerce to Kommo — 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 Kommo 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
Kommo
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Bigcommerce and Kommo 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 ⇄ KommoCustomers 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 KommoCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Bigcommerce and Kommo integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Bigcommerce and Kommo: authenticate both systems, choose the objects to sync (such as Bigcommerce's Categories and Brands), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Bigcommerce and Kommo: Contact and address details stay consistent; Where Kommo segments customers: status travels to the store record; Where both keep product records: catalog and CRM products aligned. 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.
-
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). Kommo: REST API. Authentication: OAuth 2.0 with refresh tokens. Stacksync manages authentication, retries, and rate limits on both sides.
-
Kommo: The API uses OAuth 2.0 with short-lived access tokens refreshed via refresh tokens, and supports webhooks on record lifecycle events. Bigcommerce: Rate-limit quota refreshes every 30 seconds rather than continuously, so a burst of order events during a sale can exhaust the window. Stacksync's field mapping accounts for these differences between Bigcommerce and Kommo 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 Kommo records are not retained after a sync operation.
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 476 integrations available for Bigcommerce and Kommo.
Popular · 8 of 476
-
Bigcommerce ⇄ Affinity -
Bigcommerce ⇄ 6sense -
Bigcommerce ⇄ Apollo.io -
Bigcommerce ⇄ Clearbit -
Kommo ⇄ Easypost -
Kommo ⇄ Magento -
Kommo ⇄ Nuorder -
Kommo ⇄ Shipwire
No integrations match .
