Real-time
Two-way sync
Changes in Brightpearl or Kommo instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ CRM
Brightpearl to Kommo integration — real-time, two-way sync
Keep Brightpearl 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 Brightpearl and Kommo
Close the gap between front office and back office: Kommo and Brightpearl share customers and status in real time, in both directions.
Kommo holds the customer relationship; Brightpearl runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.
Stacksync syncs Leads, Contacts, Companies, Pipelines & Statuses in Kommo with Goods-out notes, Invoices and payments, Custom fields, Products in Brightpearl field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Route leads that originate in WhatsApp or Instagram conversations into other systems of record
- 02 Replicate Kommo leads and contacts into a database or warehouse for reporting beyond built-in dashboards
- 03 Push invoices and payments into an accounting platform for reconciliation.
- 04 Keep the product catalog aligned between Brightpearl and e-commerce channels, including price list changes.
Common sync patterns
One customer master
Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.
Where Brightpearl manages people and org data: keep Kommo aligned
Owners, territories, and org structure informed by Brightpearl stay current in Kommo.
Where Brightpearl handles order-to-cash: closed-won flows through
A deal won in Kommo creates or updates the customer in Brightpearl with clean data, so fulfillment and invoicing start without re-entry.
What you can sync between Brightpearl 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.
| Brightpearl objects | Kommo objects | How this pairing syncs | |
|---|---|---|---|
| Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. | Contacts Person records sync with other CRMs and databases for a shared contact file. | 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. | |
| Custom fields Per-object custom attributes included in field mappings. | Custom Fields Per-entity custom fields hold data written from external databases and enrichment. | 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. | |
| Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. | Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. | Inventory and warehouses is specific to Brightpearl and Chats to Kommo — each maps to any object or custom field on the other side. | |
| Goods-out notes Fulfillment documents that carry picking and shipping status back to order sources. | Leads The central pipeline record; external signups and form fills sync in as leads. | Goods-out notes is specific to Brightpearl and Leads to Kommo — each maps to any object or custom field on the other side. | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Companies Organization records map to accounts in ERPs and invoicing tools. | Invoices and payments is specific to Brightpearl and Companies to Kommo — each maps to any object or custom field on the other side. | |
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Pipelines & Statuses Stage definitions structure lead progress and drive stage-change syncs to reporting tools. | Products is specific to Brightpearl and Pipelines & Statuses to Kommo — each maps to any object or custom field on the other side. |
How changes propagate between Brightpearl 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.
Brightpearl Kommo Sub-second propagation
DetectionBrightpearl notifies Stacksync of record changes through webhook events. Webhooks for object created/updated events, with resource search polling as a fallback.
DeliveryEach detected change is written to Kommo through its API, with automatic retries and rate-limit backoff.
Kommo Brightpearl 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 Brightpearl through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Brightpearl: Requests are throttled per account under Brightpearl's API usage policies; bulk operations should use batch endpoints.
- Kommo: Subject to per-account request rate limits.
What ships with Brightpearl ⇄ Kommo
Connect Brightpearl and Kommo for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Kommo connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl 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 Brightpearl or Kommo record.
Observability
Monitoring
Track your Brightpearl ⇄ Kommo sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Brightpearl and Kommo.
How the Brightpearl and Kommo connectors work
Brightpearl
- Integration surface
- REST API, organized into services (order, product, contact, warehouse, accounting)
- Authentication
- OAuth 2.0 (authorization code grant) for current apps; legacy private and public apps authenticate with app reference and account token headers
- Change detection
- Webhooks for object created/updated events, with resource search polling as a fallback
- Capabilities
- read · write · webhooks
- Rate limits
- Requests are throttled per account under Brightpearl's API usage policies; bulk operations should use batch endpoints
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 Brightpearl 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 Brightpearl 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.
Brightpearl
connected
Kommo
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl 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 · Brightpearl ⇄ 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.
Brightpearl KommoCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and Kommo integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Kommo: authenticate both systems, choose the objects to sync (such as Brightpearl's Contacts and Custom fields), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Brightpearl and Kommo connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Brightpearl–Kommo integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Brightpearl and Kommo. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Brightpearl: Webhooks for object created/updated events, with resource search polling as a fallback. On Kommo: Webhooks on record add and update events, plus polling for backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Kommo side: Leads, Contacts, Companies, Pipelines & Statuses, plus custom fields where Kommo exposes them. On the Brightpearl side: Goods-out notes, Invoices and payments, Custom fields, Products. Stacksync auto-detects both schemas and converts types between the two systems.
-
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.
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 519 integrations available for Brightpearl and Kommo.
Popular · 6 of 519
-
Brightpearl ⇄ Clari -
Brightpearl ⇄ Dun And Bradstreet -
Brightpearl ⇄ Seismic -
Brightpearl ⇄ Xactly -
Kommo ⇄ Cin7 - Kommo ⇄ DEAR Inventory
No integrations match .
