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

Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Resend: 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 Resend: Webhooks for email lifecycle events; polling for contact and audience state. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.

On the Resend side: API keys, Emails, Contacts, Audiences, plus custom fields where Resend exposes them. On the Brightpearl side: Inventory and warehouses, Goods-out notes, Invoices and payments, Custom fields. 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 Resend: Where Resend faces customers and Brightpearl carries account records; Where Brightpearl is the HR or people system of record; Master data corrections travel. Order, invoice, or account status from Brightpearl appears alongside the customer in Resend, so front-line teams answer from live data.

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