Real-time
Two-way sync
Changes in Brightpearl or Cin7 instantly reflect in both systems. No stale data, no manual imports.
ERP
Brightpearl to Cin7 integration — real-time, two-way sync
Keep Brightpearl and Cin7 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 Cin7
Two ERPs, one set of facts: Stacksync keeps Brightpearl and Cin7 consistent in real time, whether they split the business or one is replacing the other.
Companies run two ERPs for structural reasons: a two-tier setup with subsidiaries on lighter systems, an acquisition that brought its own stack, a split by function or region, or a migration that will take quarters. In all of these, some of the same organizations, people, and transactions exist in both systems, and keeping them aligned by hand is a standing tax on the back office.
Stacksync syncs Custom fields, Products, Sales orders, Purchase orders in Brightpearl with Sales orders, Purchase orders, Contacts, Branches / locations in Cin7 bi-directionally and in real time, with field-level mapping across the two data models and conflict rules you define. A record changed in either system is reflected in the other within seconds, not at the next interface run.
Common use cases
- 01 Sync Brightpearl sales orders and fulfillment status with a CRM so sales and support see order state without switching tools.
- 02 Mirror inventory levels from Brightpearl into a database that feeds availability to storefronts and marketplaces.
- 03 Keep customer records aligned between Cin7 and the CRM to remove duplicate account entry.
- 04 Write purchase orders created in a planning tool back into Cin7 for receiving.
Common sync patterns
Migration in parallel
When one system is replacing the other, run both fully live during the transition and cut over without a data freeze.
Shared master data
Where both systems keep records of the same customers, suppliers, or organizations, a correction in either updates the other.
Split by function
Where one system is the people or finance suite and the other runs operations, the records both sides depend on, such as organizations, cost centers, and reference data, stay in agreement.
What you can sync between Brightpearl and Cin7
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 | Cin7 objects | How this pairing syncs | |
|---|---|---|---|
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Products SKU records with options and pricing, synced with storefront and marketplace catalogs. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Purchase orders Supplier orders synced with procurement or accounting systems. | Purchase orders Supplier orders synced with procurement and accounting workflows. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. | Contacts Customers and suppliers, matched to CRM records to keep account data consistent. | 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. | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Credit notes / returns Return documents synced so finance and support see the same refund state. | Invoices and payments is specific to Brightpearl and Credit notes / returns to Cin7 — each maps to any object or custom field on the other side. | |
| Custom fields Per-object custom attributes included in field mappings. | Inventory levels Stock on hand by branch or location, published outward for availability. | Custom fields is specific to Brightpearl and Inventory levels to Cin7 — each maps to any object or custom field on the other side. |
How changes propagate between Brightpearl and Cin7
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 Cin7 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 Cin7 through its API, with automatic retries and rate-limit backoff.
Cin7 Brightpearl Sub-second propagation
DetectionCin7 notifies Stacksync of record changes through webhook events. Polling on modified-date filters.
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.
- Cin7: Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core.
What ships with Brightpearl ⇄ Cin7
Connect Brightpearl and Cin7 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Cin7 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or Cin7 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 Cin7 record.
Observability
Monitoring
Track your Brightpearl ⇄ Cin7 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 Cin7.
How the Brightpearl and Cin7 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
Cin7
- Integration surface
- REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs
- Authentication
- API key credentials (paired with a username or account ID, depending on the product)
- Change detection
- Polling on modified-date filters; webhook support exists on some editions for order and stock events
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core
How it works
How to connect Brightpearl to Cin7 — 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 Cin7 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
Cin7
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and Cin7 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 ⇄ Cin7Customers 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 Cin7Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and Cin7 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Cin7: authenticate both systems, choose the objects to sync (such as Brightpearl's Products and Sales orders), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Brightpearl and Cin7: Migration in parallel; Shared master data; Split by function. When one system is replacing the other, run both fully live during the transition and cut over without a data freeze.
-
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. Cin7: REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs. Authentication: API key credentials (paired with a username or account ID, depending on the product). Stacksync manages authentication, retries, and rate limits on both sides.
-
Brightpearl: Resource search endpoints return column-oriented result sets with filter parameters, which is the efficient way to poll for changed records. Cin7: Inventory is modeled per branch/location, so availability syncs choose between per-location and aggregated quantities. Stacksync's field mapping accounts for these differences between Brightpearl and Cin7 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 Cin7 records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Brightpearl and Cin7 connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Brightpearl–Cin7 integration in-house.
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 501 integrations available for Brightpearl and Cin7.
Popular · 6 of 501
-
Brightpearl ⇄ Infor M3 - Brightpearl ⇄ Infor WMS
-
Cin7 ⇄ Logiwa WMS -
Cin7 ⇄ Macola ERP -
Cin7 ⇄ Manhattan Associates WMS -
Cin7 ⇄ Microsoft Dynamics GP
No integrations match .
