Real-time
Two-way sync
Changes in Brightpearl or Kustomer instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ CRM
Brightpearl to Kustomer integration — real-time, two-way sync
Keep Brightpearl and Kustomer 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 Kustomer
Close the gap between front office and back office: Kustomer and Brightpearl share customers and status in real time, in both directions.
Kustomer 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 Conversations, Messages, Companies, Custom Objects (Klasses) in Kustomer with Products, Sales orders, Purchase orders, Contacts 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
- Keep customer attributes updated from billing systems so routing rules and SLAs reflect account value
- Escalate conversation-derived signals into the CRM as tasks or opportunities
- Land order and margin data in a warehouse for retail performance reporting.
- Sync Brightpearl sales orders and fulfillment status with a CRM so sales and support see order state without switching tools.
Where Brightpearl handles order-to-cash: closed-won flows through
A deal won in Kustomer creates or updates the customer in Brightpearl with clean data, so fulfillment and invoicing start without re-entry.
Where Brightpearl is the finance system of record: money status on the account
Invoice and payment state from Brightpearl shows on the account in Kustomer, so reps see balances before promising the next order.
One customer master
Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.
What you can sync between Brightpearl and Kustomer
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 | Kustomer objects | |
|---|---|---|
| Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. | Conversations Support threads across channels sync outward for analytics and CRM context. | |
| Goods-out notes Fulfillment documents that carry picking and shipping status back to order sources. | Messages Individual messages within conversations support full-thread replication. | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Companies Organization records group customers and map to CRM accounts. | |
| Custom fields Per-object custom attributes included in field mappings. | Custom Objects (Klasses) Structured external records such as orders and subscriptions synced in to appear on the customer timeline. | |
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Users Agent records map conversation ownership to people in other systems. | |
| Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | Teams Team assignments support routing parity and reporting. |
What ships with Brightpearl ⇄ Kustomer
Connect Brightpearl and Kustomer for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Kustomer connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or Kustomer 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 Kustomer record.
Observability
Monitoring
Track your Brightpearl ⇄ Kustomer 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 Kustomer.
How the Brightpearl and Kustomer 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
Kustomer
- Integration surface
- REST API
- Authentication
- API key used as a bearer token, scoped by role
- Change detection
- Outbound webhooks on record events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
How it works
How to connect Brightpearl to Kustomer — 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 Kustomer 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
Kustomer
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and Kustomer 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 ⇄ KustomerCustomers 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 KustomerCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and Kustomer integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Kustomer: authenticate both systems, choose the objects to sync (such as Brightpearl's Inventory and warehouses and Goods-out notes), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Brightpearl and Kustomer: Where Brightpearl handles order-to-cash: closed-won flows through; Where Brightpearl is the finance system of record: money status on the account; One customer master. A deal won in Kustomer creates or updates the customer in Brightpearl with clean data, so fulfillment and invoicing start without re-entry.
-
Brightpearl: 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. Kustomer: REST API. Authentication: API key used as a bearer token, scoped by role. Stacksync manages authentication, retries, and rate limits on both sides.
-
Kustomer: API keys are issued as role-scoped bearer tokens, so integration access can be limited to the specific object types a sync touches. Brightpearl: Brightpearl is part of Sage following its 2022 acquisition. Stacksync's field mapping accounts for these differences between Brightpearl and Kustomer 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 Brightpearl and Kustomer records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Brightpearl and Kustomer connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Brightpearl–Kustomer integration in-house.
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 Kustomer.
Popular · 8 of 386
-
Brightpearl ⇄ Veeva CRM -
Brightpearl ⇄ Vtiger CRM -
Brightpearl ⇄ Zoho SalesIQ -
Brightpearl ⇄ ZoomInfo -
Kustomer ⇄ SAP S/4HANA -
Kustomer ⇄ Odoo -
Kustomer ⇄ Blue Yonder WMS -
Kustomer ⇄ Cetec ERP
No integrations match .
