Two-way sync
Changes in Brightpearl or Customer.io instantly reflect in both systems. No stale data, no manual imports.
Keep Brightpearl and Customer.io in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
The ERP holds the records the business is run on, and it is rarely where day-to-day work happens. Customer.io is closer to the work, and the two often need the same facts about the same people, organizations, and transactions. Bridging them by hand, or by nightly file transfer, leaves each side out of date for hours at a time.
Stacksync syncs Broadcasts, Deliveries / Messages, Newsletters, People in Customer.io with Contacts, Inventory and warehouses, Goods-out notes, Invoices and payments in Brightpearl bi-directionally and in real time, with field-level mapping and rules for which system wins on conflict. Changes made where the work happens reach the system of record within seconds, and the reverse.
Payment events sync into Brightpearl as they occur, keeping the enterprise records current without manual entry.
Worker and organization data from Brightpearl stays current in Customer.io, so the tools people use daily reflect the org as it actually is.
A customer, supplier, or contact detail corrected in either system updates the other, ending duplicate maintenance.
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 | Customer.io objects | |
|---|---|---|
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Segments Attribute- or event-based groups; data syncs feed the attributes segments evaluate. | |
| Custom fields Per-object custom attributes included in field mappings. | Campaigns Automated workflows whose membership and metrics can be read via the App API. | |
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Broadcasts One-off sends to segments or audiences, triggerable via API. | |
| Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | Deliveries / Messages Per-recipient message records whose lifecycle events flow out through reporting webhooks. | |
| Purchase orders Supplier orders synced with procurement or accounting systems. | Newsletters Recurring email sends with performance metrics available for reporting syncs. | |
| Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. | People Profiles with attributes, matched on identifiers like id or email; the main write target of data syncs. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Customer.io connection.
Changes in Brightpearl or Customer.io instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Brightpearl or Customer.io data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Brightpearl or Customer.io record.
Track your Brightpearl ⇄ Customer.io sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Brightpearl and Customer.io.
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.
Authenticate Brightpearl and Customer.io with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Brightpearl and Customer.io 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Customer.io: authenticate both systems, choose the objects to sync (such as Brightpearl's Invoices and payments and Custom fields), 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 Brightpearl and Customer.io: Where Customer.io collects payments: transactions post through; Where Brightpearl is the HR or people system of record; Master data corrections travel. Payment events sync into Brightpearl as they occur, keeping the enterprise records current without manual 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. Customer.io: REST APIs split by purpose: Track API for data ingestion, App API for campaigns, people lookups, and messages. Authentication: Basic auth with site ID and API key for the Track API; bearer token for the App API. Stacksync manages authentication, retries, and rate limits on both sides.
Customer.io: Reporting webhooks emit granular message lifecycle events, which is the practical way to get engagement data out at scale. Brightpearl: Order and fulfillment state is modeled through linked documents (sales order, goods-out note, invoice) rather than a single status field, so syncs track several objects to represent one order lifecycle. Stacksync's field mapping accounts for these differences between Brightpearl and Customer.io 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 Customer.io records are not retained after a sync operation.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Brightpearl and Customer.io.