Two-way sync
Changes in Brightpearl or eClinicalWorks instantly reflect in both systems. No stale data, no manual imports.
Keep Brightpearl and eClinicalWorks in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
The ERP holds the records the business is run on, and it is rarely where day-to-day work happens. eClinicalWorks is closer to the work, and the two often need the same facts about the same people, organizations, and transactions. Bridging them by hand, or by nightly file transfer, leaves each side out of date for hours at a time.
Stacksync syncs Observations, Medications, Allergies, Immunizations in eClinicalWorks with Inventory and warehouses, Goods-out notes, Invoices and payments, Custom fields in Brightpearl bi-directionally and in real time, with field-level mapping and rules for which system wins on conflict. Changes made where the work happens reach the system of record within seconds, and the reverse.
Worker and organization data from Brightpearl stays current in eClinicalWorks, so the tools people use daily reflect the org as it actually is.
A customer, supplier, or contact detail corrected in either system updates the other, ending duplicate maintenance.
Order, invoice, or account status from Brightpearl appears alongside the customer in eClinicalWorks, so front-line teams answer from live data.
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 | eClinicalWorks objects | |
|---|---|---|
| Goods-out notes Fulfillment documents that carry picking and shipping status back to order sources. | Documents Clinical notes and attachments referenced from the chart. | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Diagnostic reports Structured result reports grouping observations for a study or panel. | |
| Custom fields Per-object custom attributes included in field mappings. | Patients Demographic records exposed via FHIR Patient resources and HL7 ADT feeds; the anchor for all clinical syncs. | |
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Appointments Scheduling records available via FHIR and HL7 SIU messages, synced for reminders and outreach. | |
| Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | Encounters Visit records tying diagnoses, providers, and billing context together. | |
| Purchase orders Supplier orders synced with procurement or accounting systems. | Practitioners Provider records used to keep directories and scheduling systems consistent. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–eClinicalWorks connection.
Changes in Brightpearl or eClinicalWorks instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Brightpearl or eClinicalWorks data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Brightpearl or eClinicalWorks record.
Track your Brightpearl ⇄ eClinicalWorks sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Brightpearl and eClinicalWorks.
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.
Authenticate Brightpearl and eClinicalWorks with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Brightpearl and eClinicalWorks 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and eClinicalWorks: authenticate both systems, choose the objects to sync (such as Brightpearl's Goods-out notes and Invoices and payments), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 eClinicalWorks: Where Brightpearl is the HR or people system of record; Master data corrections travel; Where eClinicalWorks faces customers and Brightpearl carries account records. Worker and organization data from Brightpearl stays current in eClinicalWorks, 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. eClinicalWorks: FHIR R4 REST API plus HL7 v2 interfaces (ADT, SIU, ORU) through an interface engine. Authentication: OAuth 2.0 / SMART on FHIR for the FHIR API; site-configured credentials for HL7 interface connections. Stacksync manages authentication, retries, and rate limits on both sides.
eClinicalWorks: All patient data is PHI, so integrations must run under HIPAA business associate agreements with appropriate access controls. Brightpearl: The API is split into functional services (order-service, product-service, contact-service, warehouse-service, accounting-service), each with its own resource paths. Stacksync's field mapping accounts for these differences between Brightpearl and eClinicalWorks without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Brightpearl and eClinicalWorks records are not retained after a sync operation.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Brightpearl and eClinicalWorks.