Real-time
Two-way sync
Changes in Brightpearl or Reltio instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Database
Brightpearl to Reltio integration — real-time, two-way sync
Keep Brightpearl and Reltio 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 Reltio
Give your engineers Brightpearl's data in Reltio: 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 Invoices and payments, Custom fields, Products, Sales orders from Brightpearl into Reltio 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 Reltio sync back into Brightpearl with its validations respected.
Common use cases
- 01 Feed Interactions (transactions, visits, events) into Reltio to enrich entity profiles, then read them back for 360-degree reporting.
- 02 Mirror the Reltio Activity Log and change history into a database for audit, lineage, and governance reporting.
- 03 Sync Brightpearl sales orders and fulfillment status with a CRM so sales and support see order state without switching tools.
- 04 Mirror inventory levels from Brightpearl into a database that feeds availability to storefronts and marketplaces.
Common sync patterns
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 Reltio, 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 Reltio for provisioning, access, and reporting systems that read from the database.
What you can sync between Brightpearl and Reltio
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 | Reltio objects | How this pairing syncs | |
|---|---|---|---|
| Goods-out notes Fulfillment documents that carry picking and shipping status back to order sources. | Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. | Goods-out notes is specific to Brightpearl and Crosswalks to Reltio — each maps to any object or custom field on the other side. | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. | Invoices and payments is specific to Brightpearl and Interactions to Reltio — each maps to any object or custom field on the other side. | |
| Custom fields Per-object custom attributes included in field mappings. | Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. | Custom fields is specific to Brightpearl and Matches (Potential Matches) to Reltio — each maps to any object or custom field on the other side. | |
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. | Products is specific to Brightpearl and Activity Log to Reltio — each maps to any object or custom field on the other side. | |
| Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. | Sales orders is specific to Brightpearl and Data Change Requests (DCR) to Reltio — each maps to any object or custom field on the other side. | |
| Purchase orders Supplier orders synced with procurement or accounting systems. | Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. | Purchase orders is specific to Brightpearl and Reference Data (RDM) to Reltio — each maps to any object or custom field on the other side. |
How changes propagate between Brightpearl and Reltio
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Brightpearl Reltio Sub-second propagation
DetectionBrightpearl notifies Stacksync of record changes through webhook events. Webhooks for object created/updated events, with resource search polling as a fallback.
DeliveryEach detected change is written to Reltio through its API, with automatic retries and rate-limit backoff.
Reltio Brightpearl Interval-based propagation
DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.
DeliveryEach detected change is written to Brightpearl through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Brightpearl: Requests are throttled per account under Brightpearl's API usage policies; bulk operations should use batch endpoints.
- Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with Brightpearl ⇄ Reltio
Connect Brightpearl and Reltio for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Reltio connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or Reltio 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 Reltio record.
Observability
Monitoring
Track your Brightpearl ⇄ Reltio 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 Reltio.
How the Brightpearl and Reltio 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
Reltio
- Integration surface
- Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
- Authentication
- OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
- Change detection
- Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
- Capabilities
- read · write
- Rate limits
- Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
How it works
How to connect Brightpearl to Reltio — 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 Reltio 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
Reltio
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and Reltio 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 ⇄ ReltioCustomers 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 ReltioCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and Reltio integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Reltio: 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 — Stacksync ships production-grade connectors for both Brightpearl and Reltio. 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 Reltio: Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Reltio side: Activity Log, Data Change Requests (DCR), Reference Data (RDM), Entities, plus custom fields where Reltio exposes them. On the Brightpearl side: Invoices and payments, Custom fields, Products, Sales orders. 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 Reltio: Internal tools and automations without API code; React to ERP changes; Where Brightpearl is the HR system of record: people data for internal systems. Scripts and services read and write the synced tables; Stacksync handles the Brightpearl interface, limits, and retries.
SECURITY
Security teams trust 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 432 integrations available for Brightpearl and Reltio.
Popular · 8 of 432
-
Brightpearl ⇄ DuckDB -
Brightpearl ⇄ Elasticsearch -
Brightpearl ⇄ Google Cloud Spanner - Brightpearl ⇄ Google Cloud SQL
-
Reltio ⇄ Sage 300 - Reltio ⇄ Sage Intacct
- Reltio ⇄ Sage X3
-
Reltio ⇄ SAP
No integrations match .
