Brightpearl to DEAR Inventory integration — real-time, two-way sync

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 Purchase orders and Contacts), 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.