Real-time
Two-way sync
Changes in Brightpearl or Rollworks instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Marketing
Brightpearl to Rollworks integration — real-time, two-way sync
Keep Brightpearl and Rollworks 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 Rollworks
Feed the real customer, order, and revenue records from Brightpearl into Rollworks so campaigns run on who actually bought what, and let contact and consent changes flow back in real time.
Marketing runs on lists of people, but the list rarely knows which of those people are paying customers, what they ordered, or what they are worth. Brightpearl holds exactly that: Goods-out notes, Invoices and payments, Custom fields, Products that record who the customer is, what they bought, and what they owe. When the two are joined only by a periodic export, campaigns go out against stale audiences, existing customers get prospecting emails, high-value accounts look the same as cold leads, and a canceled order still counts toward a segment.
Stacksync syncs Goods-out notes, Invoices and payments, Custom fields, Products in Brightpearl with Campaigns, Ad Groups and Ads, Reporting and Attribution, Target Account Lists in Rollworks in real time, and where both sides accept writes, in both directions. Customer, order, and invoice data maps field by field onto the contacts, audiences, or accounts Rollworks works with, so segmentation and personalization run on current purchase history instead of a month-old snapshot. Contact details and consent changes that originate in Rollworks flow back onto the record in Brightpearl.
The strongest bridge between the two is identity and purchase history, who the customer is and what they have bought, so that is where most of the value sits. Because the sync is field-level, each system keeps the attributes the other has no use for; only the shared records are held in agreement.
Common use cases
- 01 Push invoices and payments into an accounting platform for reconciliation.
- 02 Keep the product catalog aligned between Brightpearl and e-commerce channels, including price list changes.
- 03 Consolidate account-level ad engagement by domain into a reporting database to join RollWorks spend against CRM Opportunities.
- 04 Push a Target Account List from a CRM or warehouse into RollWorks, keeping Accounts (domains) and their Account Tiers aligned as the source data changes.
Common sync patterns
Suppress or target existing customers
Because Brightpearl knows who is already a paying customer, Rollworks can exclude them from acquisition campaigns or single them out for renewal and cross-sell.
One customer identity across both systems
A person or company's contact details corrected in either system update the other, so marketing and the back office stop maintaining separate versions of the same record.
Lifecycle triggers from back-office events
A first order, a renewal, or a lapsed account recorded in Brightpearl appears in Rollworks within seconds, ready to start or stop a lifecycle campaign.
What you can sync between Brightpearl and Rollworks
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 | Rollworks objects | How this pairing syncs | |
|---|---|---|---|
| Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. | Accounts (TAL Items) Individual accounts identified by domain; added or removed via the tier items endpoint (POST/DELETE) so an operational database can control which domains are targeted. | Inventory and warehouses is specific to Brightpearl and Accounts (TAL Items) to Rollworks — 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. | Audience Segments CRM (email), custom (cookie or ID), and lookalike segments created via /audience/v1/segments; membership is written from a warehouse with a duration of 1 to 540 days. | Goods-out notes is specific to Brightpearl and Audience Segments to Rollworks — each maps to any object or custom field on the other side. | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Campaigns Prospecting v2 campaigns running on Web and LinkedIn with budget, KPI, and flight settings; created and edited via API and read back for status and pacing. | Invoices and payments is specific to Brightpearl and Campaigns to Rollworks — each maps to any object or custom field on the other side. | |
| Custom fields Per-object custom attributes included in field mappings. | Ad Groups and Ads Campaign subdivisions carrying attribute, contextual, geo, and device targeting plus creative; read and written to keep targeting aligned with an internal planning system. | Custom fields is specific to Brightpearl and Ad Groups and Ads to Rollworks — 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. | Reporting and Attribution Delivery and attribution metrics (impressions, clicks, cost, conversions, view-throughs) from the GraphQL Reporting API; read-only, aggregated by campaign, ad, and account domain. | Products is specific to Brightpearl and Reporting and Attribution to Rollworks — 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. | Target Account Lists Named lists of B2B accounts for ABM; managed through /audience/v1/target_accounts so a CRM or warehouse can push and reconcile the accounts RollWorks advertises against. | Sales orders is specific to Brightpearl and Target Account Lists to Rollworks — each maps to any object or custom field on the other side. |
How changes propagate between Brightpearl and Rollworks
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 Rollworks 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 Rollworks through its API, with automatic retries and rate-limit backoff.
Rollworks Brightpearl Interval-based propagation
DetectionStacksync polls Rollworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule.
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.
- Rollworks: NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.
What ships with Brightpearl ⇄ Rollworks
Connect Brightpearl and Rollworks for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Rollworks connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or Rollworks 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 Rollworks record.
Observability
Monitoring
Track your Brightpearl ⇄ Rollworks 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 Rollworks.
How the Brightpearl and Rollworks 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
Rollworks
- Integration surface
- REST APIs (Audience, Prospecting v2) plus a GraphQL Reporting API
- Authentication
- OAuth 2.0 via NextRoll (Authorization Code grant, Bearer tokens per RFC 6749/6750); Personal Access Tokens supported for server-side scripts
- Change detection
- Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule; no change webhooks or CDC feed is published
- Capabilities
- read · write
- Rate limits
- NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.
How it works
How to connect Brightpearl to Rollworks — 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 Rollworks 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
Rollworks
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and Rollworks 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 ⇄ RollworksCustomers 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 RollworksCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and Rollworks integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Rollworks: authenticate both systems, choose the objects to sync (such as Brightpearl's Inventory and warehouses and Goods-out notes), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Brightpearl and Rollworks: Suppress or target existing customers; One customer identity across both systems; Lifecycle triggers from back-office events. Because Brightpearl knows who is already a paying customer, Rollworks can exclude them from acquisition campaigns or single them out for renewal and cross-sell.
-
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. Rollworks: REST APIs (Audience, Prospecting v2) plus a GraphQL Reporting API. Authentication: OAuth 2.0 via NextRoll (Authorization Code grant, Bearer tokens per RFC 6749/6750); Personal Access Tokens supported for server-side scripts. Stacksync manages authentication, retries, and rate limits on both sides.
-
Brightpearl: Resource search endpoints return column-oriented result sets with filter parameters, which is the efficient way to poll for changed records. Rollworks: Only one OAuth scope (all) exists today, granting access to every resource; fine-grained scopes are not yet available. Stacksync's field mapping accounts for these differences between Brightpearl and Rollworks 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 Rollworks records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Brightpearl and Rollworks connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Brightpearl–Rollworks integration in-house.
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
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 371 integrations available for Brightpearl and Rollworks.
Popular · 7 of 371
-
Brightpearl ⇄ Iterable -
Brightpearl ⇄ Bingads -
Brightpearl ⇄ Twitter Ads -
Brightpearl ⇄ Marketo -
Rollworks ⇄ Sage 100 - Rollworks ⇄ Sage 300
- Rollworks ⇄ Sage Intacct
No integrations match .
