Real-time
Two-way sync
Changes in Brightpearl or Pigment instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Accounting and finance
Brightpearl to Pigment integration — real-time, two-way sync
Keep Brightpearl and Pigment 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 Pigment
Keep Pigment 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 Tables, Scenarios, Data imports, Users and permissions in Pigment with Custom fields, Products, Sales orders, Purchase 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
- Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
- Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
- Sync Brightpearl sales orders and fulfillment status with a CRM so sales and support see order state without switching tools.
- Mirror inventory levels from Brightpearl into a database that feeds availability to storefronts and marketplaces.
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 Pigment serves a business unit and Brightpearl is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.
Where Pigment 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 Pigment
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 | Pigment objects | |
|---|---|---|
| Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | |
| Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | |
| Goods-out notes Fulfillment documents that carry picking and shipping status back to order sources. | Tables Row-based transactional data loaded into models from source systems | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | |
| Custom fields Per-object custom attributes included in field mappings. | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | |
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Users and permissions Access controls governing which model areas a sync can touch |
What ships with Brightpearl ⇄ Pigment
Connect Brightpearl and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or Pigment 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 Pigment record.
Observability
Monitoring
Track your Brightpearl ⇄ Pigment 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 Pigment.
How the Brightpearl and Pigment 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
Pigment
- Integration surface
- REST-based import and export API
- Authentication
- API keys, issued separately for import and export
- Change detection
- no change feed; syncs run scheduled imports and exports
- Capabilities
- read · write
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Brightpearl to Pigment — 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 Pigment 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
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and Pigment 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 ⇄ PigmentCustomers 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 PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Pigment: authenticate both systems, choose the objects to sync (such as Brightpearl's Contacts and Inventory and warehouses), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Pigment side: Tables, Scenarios, Data imports, Users and permissions, plus custom fields where Pigment exposes them. On the Brightpearl side: Custom fields, Products, Sales orders, Purchase 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 Pigment: One customer and vendor master; Subsidiary to headquarters; Where Pigment handles billing: invoices land in Brightpearl. Where both systems keep records of the same organizations, corrections made in either propagate to the other.
-
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. Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Stacksync manages authentication, retries, and rate limits on both sides.
-
Pigment: Pigment's model is multidimensional: metrics are sliced by dimension lists, so inbound records must map to those dimensions rather than flat columns. Brightpearl: Order and fulfillment state is modeled through linked documents (sales order, goods-out note, invoice) rather than a single status field, so syncs track several objects to represent one order lifecycle. Stacksync's field mapping accounts for these differences between Brightpearl and Pigment without custom code.
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 Pigment.
Popular · 8 of 386
-
Brightpearl ⇄ Chargebee -
Brightpearl ⇄ Hyperline -
Brightpearl ⇄ QuickBooks -
Brightpearl ⇄ Stripe -
Pigment ⇄ Oracle Fusion ERP -
Pigment ⇄ Acumatica -
Pigment ⇄ SAP S/4HANA -
Pigment ⇄ Odoo
No integrations match .
