Real-time
Two-way sync
Changes in Brightpearl or Citus instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Database
Brightpearl to Citus integration — real-time, two-way sync
Keep Brightpearl and Citus in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from Mulesoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Brightpearl and Citus
Give your engineers Brightpearl's data in Citus: read it with normal queries, write back through the sync, and skip the ERP API entirely.
ERP data sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.
Stacksync mirrors Goods-out notes, Invoices and payments, Custom fields, Products from Brightpearl into Citus and keeps both sides consistent in real time. Whatever Brightpearl is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in Citus sync back into Brightpearl with its validations respected.
Common use cases
- Consolidate per-tenant rows from distributed tables into per-customer reporting databases.
- Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
- Push invoices and payments into an accounting platform for reconciliation.
- Keep the product catalog aligned between Brightpearl and e-commerce channels, including price list changes.
Internal tools and automations without API code
Scripts and services read and write the synced tables; Stacksync handles the Brightpearl interface, limits, and retries.
React to ERP changes
Updates in Brightpearl arrive as row changes in Citus, so jobs and triggers can respond as the business record changes.
Where Brightpearl is the HR system of record: people data for internal systems
Worker and org records stay current in Citus for provisioning, access, and reporting systems that read from the database.
What you can sync between Brightpearl and Citus
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 | Citus objects | |
|---|---|---|
| Goods-out notes Fulfillment documents that carry picking and shipping status back to order sources. | Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | |
| Custom fields Per-object custom attributes included in field mappings. | Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | |
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | |
| Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | Views Curated projections over distributed data, often used as read-only sync sources. | |
| Purchase orders Supplier orders synced with procurement or accounting systems. | Sequences Key generators that matter when external writes must not collide with application inserts. |
What ships with Brightpearl ⇄ Citus
Connect Brightpearl and Citus for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Citus connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or Citus data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Brightpearl or Citus record.
Observability
Monitoring
Track your Brightpearl ⇄ Citus sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Brightpearl and Citus.
How the Brightpearl and Citus connectors work
Brightpearl
- Integration surface
- 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
- Change detection
- Webhooks for object created/updated events, with resource search polling as a fallback
- Capabilities
- read · write · webhooks
- Rate limits
- Requests are throttled per account under Brightpearl's API usage policies; bulk operations should use batch endpoints
Citus
- Integration surface
- PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
- Authentication
- Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
- Change detection
- PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
- Capabilities
- read · write · CDC
How it works
How to connect Brightpearl to Citus — three steps, no code
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.
- 01
Connect your apps
Authenticate Brightpearl and Citus with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Brightpearl
connected
Citus
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and Citus 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.
objects · Brightpearl ⇄ CitusCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Brightpearl CitusCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and Citus integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Citus: 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.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Brightpearl and Citus connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Brightpearl–Citus integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Brightpearl and Citus. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Brightpearl: Webhooks for object created/updated events, with resource search polling as a fallback. On Citus: PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Citus side: Views, Sequences, Distributed tables, Reference tables, plus custom fields where Citus 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.
SECURITY
Security teams love Stacksync
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.
SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Brightpearl and Citus.
Popular · 8 of 386
-
Brightpearl ⇄ Google Cloud SQL -
Brightpearl ⇄ IBM AS/400 -
Brightpearl ⇄ IBM Informix -
Brightpearl ⇄ InfluxDB -
Citus ⇄ Infor WMS -
Citus ⇄ IQMS (DELMIAworks) -
Citus ⇄ JobBOSS² -
Citus ⇄ Körber WMS
No integrations match .
