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

Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Gorgias: authenticate both systems, choose the objects to sync (such as Brightpearl's Custom fields 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 Gorgias: Webhooks for ticket and message events, supplemented by polling with updated-at cursors. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.

On the Gorgias side: Customers, Users (agents), Tags, Satisfaction surveys, plus custom fields where Gorgias exposes them. On the Brightpearl side: Purchase orders, Contacts, Inventory and warehouses, Goods-out notes. 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 Gorgias: Where Brightpearl is the finance system of record: money status on the account; One customer master; Where Brightpearl manages people and org data: keep Gorgias aligned. Invoice and payment state from Brightpearl shows on the account in Gorgias, so reps see balances before promising the next order.

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. Gorgias: REST API. Authentication: API key paired with the account email over HTTP Basic auth; OAuth 2.0 for public apps. Stacksync manages authentication, retries, and rate limits on both sides.