Real-time
Two-way sync
Changes in Brightpearl or DEAR Inventory instantly reflect in both systems. No stale data, no manual imports.
ERP
Brightpearl to DEAR Inventory integration — real-time, two-way sync
Keep Brightpearl and DEAR Inventory 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 DEAR Inventory
Two ERPs, one set of facts: Stacksync keeps Brightpearl and DEAR Inventory 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 Goods-out notes, Invoices and payments, Custom fields, Products in Brightpearl with Products, Stock levels, Sale orders, Purchase orders in DEAR Inventory 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 Land order and margin data in a warehouse for retail performance reporting.
- 02 Sync Brightpearl sales orders and fulfillment status with a CRM so sales and support see order state without switching tools.
- 03 Keep supplier and purchase order data aligned with the accounting system for accrual accuracy.
- 04 Sync stock levels and product data to e-commerce storefronts and a CRM so sales quotes reflect real availability.
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 DEAR Inventory
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 | DEAR Inventory objects | How this pairing syncs | |
|---|---|---|---|
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Products SKU records with pricing, suppliers, and bill-of-material links; the master data most syncs start from. | 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. | Sale orders Customer orders through their pick/pack/ship lifecycle; synced with storefronts and CRMs. | 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. | |
| Purchase orders Supplier orders synced with procurement or accounting systems. | Purchase orders Supplier orders and receiving records synced with accounting and planning tools. | 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. | Stock adjustments and transfers Inventory movement transactions that explain changes in availability. | Contacts is specific to Brightpearl and Stock adjustments and transfers to DEAR Inventory — each maps to any object or custom field on the other side. | |
| Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. | Assemblies / Production Bill-of-material and production records for light manufacturing workflows. | Inventory and warehouses is specific to Brightpearl and Assemblies / Production to DEAR Inventory — 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. | Locations Warehouses and bins that scope stock levels and fulfillment. | Goods-out notes is specific to Brightpearl and Locations to DEAR Inventory — each maps to any object or custom field on the other side. |
How changes propagate between Brightpearl and DEAR Inventory
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 DEAR Inventory 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 DEAR Inventory through its API, with automatic retries and rate-limit backoff.
DEAR Inventory Brightpearl Sub-second propagation
DetectionDEAR Inventory notifies Stacksync of record changes through webhook events. Polling with modified-since 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.
- DEAR Inventory: Subject to the platform's per-account API rate limits.
What ships with Brightpearl ⇄ DEAR Inventory
Connect Brightpearl and DEAR Inventory for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–DEAR Inventory connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or DEAR Inventory 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 DEAR Inventory record.
Observability
Monitoring
Track your Brightpearl ⇄ DEAR Inventory 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 DEAR Inventory.
How the Brightpearl and DEAR Inventory 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
DEAR Inventory
- Integration surface
- REST API
- Authentication
- Account ID plus application key sent as request headers
- Change detection
- Polling with modified-since filters; webhook notifications for sale and purchase events are available on subscriptions that include the Automation module
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's per-account API rate limits
How it works
How to connect Brightpearl to DEAR Inventory — 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 DEAR Inventory 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
DEAR Inventory
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and DEAR Inventory 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 ⇄ DEAR InventoryCustomers 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 DEAR InventoryCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and DEAR Inventory integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and DEAR Inventory: 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.
-
Change detection on Brightpearl: Webhooks for object created/updated events, with resource search polling as a fallback. On DEAR Inventory: Polling with modified-since filters; webhook notifications for sale and purchase events are available on subscriptions that include the Automation module. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Brightpearl side: Goods-out notes, Invoices and payments, Custom fields, Products, plus custom fields where Brightpearl exposes them. On the DEAR Inventory side: Products, Stock levels, Sale orders, Purchase orders. 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.
-
Common patterns for Brightpearl and DEAR Inventory: 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. DEAR Inventory: REST API. Authentication: Account ID plus application key sent as request headers. Stacksync manages authentication, retries, and rate limits on both sides.
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 409 integrations available for Brightpearl and DEAR Inventory.
Popular · 6 of 409
-
Brightpearl ⇄ Epicor ERP -
Brightpearl ⇄ Extensiv (3PL Central) -
Brightpearl ⇄ Fishbowl Manufacturing -
DEAR Inventory ⇄ Sage Intacct - DEAR Inventory ⇄ Sage X3
-
DEAR Inventory ⇄ SAP
No integrations match .
