Real-time
Two-way sync
Changes in Brightpearl or Linnworks instantly reflect in both systems. No stale data, no manual imports.
ERP
Brightpearl to Linnworks integration — real-time, two-way sync
Keep Brightpearl and Linnworks 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 Linnworks
Two ERPs, one set of facts: Stacksync keeps Brightpearl and Linnworks consistent in real time, whether they split the business or one is replacing the other.
Companies run two ERPs for structural reasons: a two-tier setup with subsidiaries on lighter systems, an acquisition that brought its own stack, a split by function or region, or a migration that will take quarters. In all of these, some of the same organizations, people, and transactions exist in both systems, and keeping them aligned by hand is a standing tax on the back office.
Stacksync syncs Goods-out notes, Invoices and payments, Custom fields, Products in Brightpearl with Stock Levels, Locations, Purchase Orders, Suppliers in Linnworks bi-directionally and in real time, with field-level mapping across the two data models and conflict rules you define. A record changed in either system is reflected in the other within seconds, not at the next interface run.
Common use cases
- 01 Land order and margin data in a warehouse for retail performance reporting.
- 02 Sync Brightpearl sales orders and fulfillment status with a CRM so sales and support see order state without switching tools.
- 03 Mirror processed orders, refunds, and returns into a warehouse for margin reporting across channels
- 04 Sync product and listing data with a PIM so channel listings stay aligned with the catalog
Common sync patterns
Two-tier roll-up
Where subsidiaries run one system and headquarters runs the other, shared records and transactions flow up continuously, so consolidation starts from live data.
Migration in parallel
When one system is replacing the other, run both fully live during the transition and cut over without a data freeze.
Shared master data
Where both systems keep records of the same customers, suppliers, or organizations, a correction in either updates the other.
What you can sync between Brightpearl and Linnworks
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 | Linnworks objects | How this pairing syncs | |
|---|---|---|---|
| Purchase orders Supplier orders synced with procurement or accounting systems. | Purchase Orders Replenishment POs sync with suppliers and accounting systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Channel Listings Marketplace and webstore listing mappings tie channel products to internal SKUs. | Invoices and payments is specific to Brightpearl and Channel Listings to Linnworks — each maps to any object or custom field on the other side. | |
| Custom fields Per-object custom attributes included in field mappings. | Returns & Refunds Post-sale records flow to finance and support systems. | Custom fields is specific to Brightpearl and Returns & Refunds to Linnworks — 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. | Shipping Services Carrier and service definitions support label and tracking data in order syncs. | Products is specific to Brightpearl and Shipping Services to Linnworks — 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. | Open Orders Unshipped orders aggregated from sales channels sync into ERPs and fulfillment systems. | Sales orders is specific to Brightpearl and Open Orders to Linnworks — each maps to any object or custom field on the other side. | |
| Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. | Processed Orders Completed orders feed accounting and warehouse-based margin reporting. | Contacts is specific to Brightpearl and Processed Orders to Linnworks — each maps to any object or custom field on the other side. |
How changes propagate between Brightpearl and Linnworks
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 Linnworks 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 Linnworks through its API, with automatic retries and rate-limit backoff.
Linnworks Brightpearl Interval-based propagation
DetectionStacksync polls Linnworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling on order and stock endpoints.
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.
- Linnworks: Per-endpoint rate limits apply on the Linnworks API.
What ships with Brightpearl ⇄ Linnworks
Connect Brightpearl and Linnworks for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Linnworks connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or Linnworks 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 Linnworks record.
Observability
Monitoring
Track your Brightpearl ⇄ Linnworks 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 Linnworks.
How the Brightpearl and Linnworks 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
Linnworks
- Integration surface
- REST API
- Authentication
- Application credentials and an install token exchanged for a session token
- Change detection
- Polling on order and stock endpoints
- Capabilities
- read · write
- Rate limits
- Per-endpoint rate limits apply on the Linnworks API
How it works
How to connect Brightpearl to Linnworks — 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 Linnworks 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
Linnworks
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and Linnworks 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 ⇄ LinnworksCustomers 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 LinnworksCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and Linnworks integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Linnworks: authenticate both systems, choose the objects to sync (such as Brightpearl's Purchase orders and Invoices and payments), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Brightpearl side: Goods-out notes, Invoices and payments, Custom fields, Products, plus custom fields where Brightpearl exposes them. On the Linnworks side: Stock Levels, Locations, Purchase Orders, Suppliers. 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 Linnworks: Two-tier roll-up; Migration in parallel; Shared master data. Where subsidiaries run one system and headquarters runs the other, shared records and transactions flow up continuously, so consolidation starts from live data.
-
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. Linnworks: REST API. Authentication: Application credentials and an install token exchanged for a session token. Stacksync manages authentication, retries, and rate limits on both sides.
-
Brightpearl: The API is split into functional services (order-service, product-service, contact-service, warehouse-service, accounting-service), each with its own resource paths. Linnworks: The Linnworks API uses a token-exchange model: application credentials plus a per-account install token are exchanged for a session token that authorizes subsequent calls. Stacksync's field mapping accounts for these differences between Brightpearl and Linnworks without custom code.
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 505 integrations available for Brightpearl and Linnworks.
Popular · 7 of 505
-
Brightpearl ⇄ Infor CloudSuite - Brightpearl ⇄ Infor LN
- Brightpearl ⇄ Infor M3
-
Linnworks ⇄ Logiwa WMS -
Linnworks ⇄ Macola ERP -
Linnworks ⇄ Manhattan Associates WMS -
Linnworks ⇄ Microsoft Dynamics GP
No integrations match .
