Integration combo
Magento to Brightpearl integration
Magento (Adobe Commerce) is the storefront. Brightpearl is the retail operations spine: inventory, orders, purchasing, accounting, the lot. Connecting them well means Magento drives orders into Brightpearl as real sales documents, Brightpearl pushes the only authoritative stock number back, and the integration negotiates the long list of edge cases around B2B pricing, multi-warehouse routing and tax. We design, build and support Magento-to-Brightpearl integrations as a Patchworks Partner Agency, with SLA-backed support from go-live.
Flow shape
Order sync: Magento to Brightpearl
Magento orders land in Brightpearl as proper sales orders with the right customer record, pricing context and warehouse routing.
- Trigger Magento Order placed sales_order_place event
- Extract Patchworks Ingest order queue, dedupe
- Decision Patchworks Customer exists? lookup by email
- Transform Patchworks Map order SKUs, pricing, tax, warehouse
- Action Brightpearl Create sales order with allocation
- Writeback Magento Tag order store Brightpearl ID
Illustrative only. The diagram above shows how an integration of this shape works in concept. It is not a screenshot or export of the actual Patchworks process flow; the production flow has more nodes, more branches and more error handling than a marketing page can usefully render.
What we sync
5 synchronisations between Magento and Brightpearl.
Only the data flows that both platforms actually support. Each section below describes what’s in scope, the gotchas we watch for, and how the flow is shaped inside Patchworks.
- 01
Order sync
Magento Brightpearl
Orders raised in Magento flow into Brightpearl on creation, status change and edit. The flow normalises Magento's order schema into the record shape Brightpearl expects, including line-level discounts, taxes, gift cards, shipping methods and multi-currency. Partial cancellations and post-capture edits are handled with idempotent updates so Brightpearl stays the system of record without double-counting. Edge cases that come up most often on this pair: backorders, pre-orders, subscription rebills and orders placed through guest checkout with no matching customer record on the destination side.
- 02
Inventory sync
Brightpearl Magento
Stock levels in Brightpearl push to Magento on a schedule, on movement events, or both. The flow handles multi-location and multi-warehouse split, safety stock buffers, in-transit and committed quantities, and channel-specific availability rules. Where Magento has its own location model we map Brightpearl's locations onto it explicitly rather than relying on default behaviour. Throttling protects both sides during bulk recalculations; deltas only during normal operation. The goal is one source of truth for sellable inventory across the estate, with Brightpearl retaining authority.
- 03
Product sync
Brightpearl Magento
Product master data syncs from Brightpearl to Magento on publish, with channel-aware enrichment so Magento only receives the attributes it can act on. Variants, option sets, media, locale-specific copy, category mappings and metafield or extension data are handled explicitly. New SKUs flow in; deprecated SKUs are flagged rather than hard-deleted so historical orders stay intact. Where Magento has channel-specific requirements that Brightpearl does not natively model (typing rules, required attributes, image dimensions), the integration enforces them at the boundary rather than asking the merchandising team to.
- 04
Pricing sync
Brightpearl Magento
Price lists in Brightpearl push to Magento with currency, tax-class and customer-group awareness intact. Promotional pricing, contract pricing and tiered B2B pricing are handled as first-class concepts rather than overrides applied at the storefront. Where Brightpearl runs effective-dated pricing, the flow coordinates the cutover so Magento's catalogue switches at the same instant as the finance side rather than drifting by hours. Currency rounding and display-tax rules are reconciled at the integration boundary to avoid the classic 1p / 1c off-by-one that haunts multi-currency rollouts.
- 05
Customer sync
Magento Brightpearl
Customers created or updated in Magento flow into Brightpearl with a stable cross-system identifier so the same shopper isn't fragmented into duplicates across the estate. Addresses, marketing preferences, B2B account hierarchies, tax exemption flags and channel attribution are mapped explicitly rather than left to Brightpearl's defaults. Where Brightpearl is the customer system of record (CRM or ERP) we publish back into Magento so storefront personalisation and segmentation reflect the canonical state. GDPR deletion and rectification are propagated across the integration in both directions.
Typical delivery
6 to 9 weeks for a standard delivery.
Up to 5× faster using PatchBuddy- Week 1 Discovery: catalogue depth, customer groups, warehouse model, tax setup.
- Weeks 2 to 4 Build: products, inventory, orders, customers, fulfilment writeback.
- Weeks 5 to 6 Integration testing with real Magento and Brightpearl sandbox data.
- Weeks 7 to 8 UAT with operations and finance; sign-off on edge cases.
- Week 9 Cutover and hyper-care; transition into support retainer.
Patchworks delivery
How Patchworks shapes Magento to Brightpearl.
Brightpearl has a Magento connector of its own, and for many merchants that's the right place to start. Patchworks earns its place where Magento's catalogue depth pushes the native connector against its limits: large attribute sets, configurable products with non-trivial variant trees, customer-group pricing, multi-source inventory. We build those flows in Patchworks, version them with the merchant's release cadence, and hand over runbooks that cover the cases the native connector glosses past.
Got more connectors that need to live in this flow? A 3PL, a marketplace, returns, a PIM, anything. We can do it. Most live integrations end up larger than a pair, all built and supported as one estate. More on multi-platform estates →
Our Patchworks practiceQuestions
Common questions.
-
01 Do you handle configurable products and their child SKUs?
Yes. We map Magento's configurable + simple-product pattern onto Brightpearl's parent/variant model explicitly at scoping. The integration treats the simple-product SKU as authoritative for stock and pricing, with the configurable used for storefront display. -
02 What about customer-group pricing in Magento?
Customer groups map to Brightpearl price lists. Orders carry the right effective price for the customer at checkout, and Brightpearl posts the matching invoice without finance having to override anything. -
03 How is multi-source inventory handled?
Brightpearl is the source of truth for sellable stock. Magento Multi-Source Inventory receives availability by source so customer-facing stock reflects the warehouse split rather than a single aggregate number. -
04 Do you support this under SLA after go-live?
Yes. The same team that builds the integration runs it under retainer. Monitoring on every shipped flow, on-call cover, monthly health checks and tiered response SLAs from £750/month.
Get in touch
Tell us what you’re trying to connect.
And what’s in the way. We will tell you whether we are the right people to do it. Drop us a line below, or open the chat in the corner of the screen.
Direct: contact@ecirql.com
Message sent
Thanks. We’ll be in touch.
Your message is in our inbox. A human will read it and reply within a working day. For anything urgent, drop us a line at contact@ecirql.com or open the chat in the corner of the screen.