Brightpearl to Orderful integration — real-time, two-way sync

Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Orderful: authenticate both systems, choose the objects to sync (such as Brightpearl's Sales orders and Purchase 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 Orderful: Webhooks push inbound transactions and status events; polling available as fallback. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.

On the Orderful side: Trading partners, Relationships, Validation guidelines, Acknowledgments, plus custom fields where Orderful exposes them. On the Brightpearl side: Goods-out notes, Invoices and payments, Custom fields, Products. 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 Orderful: Where Brightpearl is the HR or people system of record; Master data corrections travel; Where Orderful faces customers and Brightpearl carries account records. Worker and organization data from Brightpearl stays current in Orderful, so the tools people use daily reflect the org as it actually is.

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. Orderful: REST API (JSON). Authentication: API key. Stacksync manages authentication, retries, and rate limits on both sides.