Integration combo
Shopify to Brightpearl integration
Brightpearl is a retail operations platform that does a lot in one place: orders, inventory, purchasing, accounting and CRM. Sitting it behind Shopify means deciding which side of that combined surface owns each piece of data, and enforcing that decision in every flow. We design, build and support Shopify-to-Brightpearl integrations as a certified Patchworks Partner Agency. Orders, customers, inventory, pricing, fulfilments and credit notes flow as one coherent estate rather than a stack of point-to-point connections.
Flow shape
Order sync: Shopify to Brightpearl
How a Shopify order lands as a Brightpearl sales order with the warehouse routing, accounting treatment and customer record in place from the first run.
- Trigger Shopify Order created order/create webhook
- Extract Patchworks Ingest payload queue, dedupe, normalise
- Decision Patchworks Customer exists? Brightpearl contact lookup
- Transform Patchworks Resolve warehouse SKU routing, location rules
- Transform Patchworks Map to sales order lines, taxes, payment status
- Action Brightpearl Create sales order via Brightpearl API
- Writeback Shopify Tag order store Brightpearl reference
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
7 synchronisations between Shopify 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
Shopify Brightpearl
Orders raised in Shopify flow into Brightpearl on creation, status change and edit. The flow normalises Shopify'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 Shopify
Stock levels in Brightpearl push to Shopify 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 Shopify 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 Shopify
Product master data syncs from Brightpearl to Shopify on publish, with channel-aware enrichment so Shopify 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 Shopify 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 Shopify
Price lists in Brightpearl push to Shopify 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 Shopify'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
Shopify Brightpearl
Customers created or updated in Shopify 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 Shopify so storefront personalisation and segmentation reflect the canonical state. GDPR deletion and rectification are propagated across the integration in both directions.
- 06
Returns sync
Shopify Brightpearl
Return authorisations created in Shopify flow into Brightpearl with reason codes, inspection state, restocking decisions and refund eligibility carried through. Where Brightpearl is the ERP or WMS, the return becomes an inbound record that affects available stock and accounts. Where Brightpearl is the storefront, the order record updates so the customer-facing return state stays honest. Exchanges are handled as a paired return-plus-outbound rather than collapsed into a refund-plus-new-order, which keeps the accounting clean and the operational picture accurate.
- 07
Refund sync
Shopify Brightpearl
Refund decisions raised in Shopify push into Brightpearl as the financial event they are, with original payment method, partial-versus-full handling, tax recalculation and currency intact. The flow waits on inspection outcome where the merchant policy requires it rather than firing on RMA creation. Refunds against gift cards, multi-tender orders and marketplace orders (where the marketplace owns the refund execution) each take a different path; the integration picks the right one based on the original order's tender mix rather than a single default rule.
Typical delivery
5 to 8 weeks for a standard delivery.
Up to 5× faster using PatchBuddy- Week 1 Discovery: Brightpearl account setup, warehouse map, accounting period rules, fulfilment workflow.
- Weeks 2 to 4 Build: order, customer, inventory, fulfilment and credit-note flows in Patchworks.
- Weeks 5 to 6 Integration testing against the Brightpearl sandbox using staged Shopify orders.
- Week 7 UAT with operations and finance; sign-off on edge cases and accounting mappings.
- Week 8 Cutover and hyper-care; transition into support retainer with monitoring and SLA.
Patchworks delivery
How Patchworks shapes Shopify to Brightpearl.
Brightpearl has a clear opinion about how retail operations should run, and integrations that respect that opinion are the ones that stay clean. We build the Shopify-to-Brightpearl flows in Patchworks with explicit handling for Brightpearl's order lifecycle, pick-and-pack model, and accounting treatment. Inventory rules per warehouse, automatic SKU routing, and the events that Brightpearl emits on shipment all flow back into Shopify so the storefront reads the same state operations and finance do.
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 Can Brightpearl own inventory while Shopify shows availability?
Yes. Brightpearl is typically the source of truth for stock, with channel-aware availability publishing to Shopify on a delta cadence plus event-driven updates on movement. Safety stock buffers are configurable per SKU group and per warehouse. -
02 How are Brightpearl's automation rules respected?
We build the integration around Brightpearl's automation rather than fighting it. Order status transitions, allocation rules and accounting period locks are treated as authoritative; the Patchworks flows trigger and respect Brightpearl's lifecycle rather than bypassing it. -
03 What about Shopify subscriptions and pre-orders?
Supported. Subscription rebills post as discrete orders with the subscription metadata mapped onto Brightpearl custom fields. Pre-orders carry a flag so allocation waits for available stock; the order stays open in Brightpearl rather than being auto-cancelled. -
04 Can we use Brightpearl's POS alongside the Shopify integration?
Yes. The integration is scoped around the Shopify channel; Brightpearl POS sales sit alongside it in Brightpearl as their own channel and the inventory model accounts for both. Where you also use Shopify POS we model that as a third channel. -
05 Do you support Shopify-to-Brightpearl 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: [email protected]
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 [email protected] or open the chat in the corner of the screen.