Real-time
Two-way sync
Changes in Brightpearl or Rillet instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Accounting and finance
Brightpearl to Rillet integration — real-time, two-way sync
Keep Brightpearl and Rillet 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 Rillet
Keep Rillet and Brightpearl agreeing on customers, invoices, and balances, whether they split the finance workload or one is replacing the other.
A dedicated finance tool and an ERP end up side by side for practical reasons: a subsidiary runs lighter software than headquarters, billing runs in a specialist system while the enterprise system holds the wider view, or the company is mid-migration and both are live. Whatever the split, the two systems describe overlapping customers and transactions, and that overlap drifts without a live connection.
Stacksync syncs Custom Field, Account, Customer, Vendor in Rillet with Invoices and payments, Custom fields, Products, Sales orders in Brightpearl in real time and in both directions. You decide which system wins on which field, and every change made in one is reflected in the other within seconds instead of at the next batch run.
Common use cases
- 01 Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
- 02 Push billing events from a product or usage-metering system into Rillet for revenue recognition.
- 03 Mirror inventory levels from Brightpearl into a database that feeds availability to storefronts and marketplaces.
- 04 Push invoices and payments into an accounting platform for reconciliation.
Common sync patterns
One customer and vendor master
Where both systems keep records of the same organizations, corrections made in either propagate to the other.
Subsidiary to headquarters
Where Rillet serves a business unit and Brightpearl is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.
Where Rillet handles billing: invoices land in Brightpearl
Invoices and payment activity from the billing side post through to the enterprise system automatically.
What you can sync between Brightpearl and Rillet
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 | Rillet objects | How this pairing syncs | |
|---|---|---|---|
| Custom fields Per-object custom attributes included in field mappings. | Custom Field Synced with incremental and full sync per the Stacksync docs. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. | Credit Memo Synced with incremental and full sync per the Stacksync docs. | Inventory and warehouses is specific to Brightpearl and Credit Memo to Rillet — each maps to any object or custom field on the other side. | |
| Goods-out notes Fulfillment documents that carry picking and shipping status back to order sources. | Bill Synced with incremental and full sync per the Stacksync docs. | Goods-out notes is specific to Brightpearl and Bill to Rillet — each maps to any object or custom field on the other side. | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Journal Entry Synced with incremental and full sync per the Stacksync docs. | Invoices and payments is specific to Brightpearl and Journal Entry to Rillet — 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. | Invoice Payment Synced with incremental and full sync per the Stacksync docs. | Products is specific to Brightpearl and Invoice Payment to Rillet — 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. | Charge Synced with incremental and full sync per the Stacksync docs. | Sales orders is specific to Brightpearl and Charge to Rillet — each maps to any object or custom field on the other side. |
How changes propagate between Brightpearl and Rillet
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 Rillet 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 Rillet through its API, with automatic retries and rate-limit backoff.
Rillet Brightpearl Sub-second propagation
DetectionRillet pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking.
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.
- Rillet: Subject to the platform's API rate limits.
What ships with Brightpearl ⇄ Rillet
Connect Brightpearl and Rillet for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Rillet connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or Rillet 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 Rillet record.
Observability
Monitoring
Track your Brightpearl ⇄ Rillet 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 Rillet.
How the Brightpearl and Rillet 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
Rillet
- Integration surface
- REST API (OpenAPI-specified, with production and sandbox environments)
- Authentication
- API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync
- Change detection
- Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h)
- Capabilities
- read · write · CDC · webhooks
- Rate limits
- Subject to the platform's API rate limits.
How it works
How to connect Brightpearl to Rillet — 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 Rillet 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
Rillet
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and Rillet 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 ⇄ RilletCustomers 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 RilletCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and Rillet integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Rillet: authenticate both systems, choose the objects to sync (such as Brightpearl's Custom fields and Inventory and warehouses), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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. Rillet: REST API (OpenAPI-specified, with production and sandbox environments). Authentication: API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync. Stacksync manages authentication, retries, and rate limits on both sides.
-
Rillet: Only 17 documented objects are supported. 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 Rillet 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 Rillet records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Brightpearl and Rillet connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Brightpearl–Rillet integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Brightpearl and Rillet. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 428 integrations available for Brightpearl and Rillet.
Popular · 7 of 428
-
Brightpearl ⇄ Chargebee -
Brightpearl ⇄ Hyperline -
Brightpearl ⇄ Pigment -
Brightpearl ⇄ QuickBooks -
Rillet ⇄ Microsoft Dynamics GP - Rillet ⇄ Microsoft Dynamics NAV
-
Rillet ⇄ Plex ERP
No integrations match .
