Skip to content
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

  • Route leads that originate in WhatsApp or Instagram conversations into other systems of record
  • Replicate Kommo leads and contacts into a database or warehouse for reporting beyond built-in dashboards
  • Push invoices and payments into an accounting platform for reconciliation.
  • Keep the product catalog aligned between Brightpearl and e-commerce channels, including price list changes.

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
Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. Tasks Follow-up records keep rep activity consistent across systems.
Purchase orders Supplier orders synced with procurement or accounting systems. Notes Free-text and system notes attach context to synced leads and contacts.
Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. Custom Fields Per-entity custom fields hold data written from external databases and enrichment.
Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. Users Account users map lead ownership to people in other systems.
Goods-out notes Fulfillment documents that carry picking and shipping status back to order sources. Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts.
Invoices and payments Financial documents synced to accounting platforms for reconciliation. Leads The central pipeline record; external signups and form fills sync in as leads.
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.

Real-time

Two-way sync

Changes in Brightpearl or Kommo instantly reflect in both systems. No stale data, no manual imports.

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.

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

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Brightpearl connected
    Kommo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Brightpearl ⇄ Kommo
    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
    Brightpearl Kommo
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Brightpearl and Kommo integration FAQ

SECURITY

Security teams love 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
CSA STAR
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 386 integrations available for Brightpearl and Kommo.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.