Skip to content

Bundle

Shopify + BrightPearl

Shopify orders become BrightPearl sales orders, split one per fulfillment location; goods-out shipments fulfill only their own slice of the order, and stock changes update Shopify inventory by SKU.

ShopifyBrightPearl
  • Shopify
  • BrightPearl
3
Pre-built flows
6
Steps in total
1 + 2
Flows into BrightPearl + flows back to Shopify
7
Settings sections

Flows

What installs

Each template becomes an editable flow in your account. Direction, trigger and step count are read from the template itself.

FlowDirectionTriggerSteps
Shopify order → BrightPearl sales order (split by location)Split
Shopify
BrightPearl
Order createdWebhook
3
BrightPearl goods-out shipped → Shopify fulfillment (per location)
BrightPearl
Shopify
Goods-out shippedWebhook
1
BrightPearl stock change → Shopify inventory level
BrightPearl
Shopify
Inventory changedPolling
2

Settings tab

Configured before it runs

This bundle ships a settings tab the merchant works through first. Its flows are blocked until the tab is confirmed — a mapping nobody set is a failure, not a default.

7 sections42 fields18 required6 mapping tables
  • General

    Fields
    2
    Required
    2
    Mapping tables
    0
  • Inventory

    Toggle

    Switched on by “Enable inventory updates”; its other fields are required only while it is on.

    Fields
    4
    Required
    2
    Mapping tables
    1

    3 fields are filled from live account data.

  • Prices

    Toggle

    Switched on by “Enable price updates”; its other fields are required only while it is on.

    Fields
    2
    Required
    1
    Mapping tables
    0

    1 field is filled from live account data.

  • Orders

    Toggle

    Switched on by “Enable order downloads”; its other fields are required only while it is on.

    Fields
    24
    Required
    9
    Mapping tables
    3

    16 fields are filled from live account data.

  • Fulfillment

    Toggle

    Important: fulfilment updates depend on the multi-location mapping under Inventory. Without it, this store receives no fulfilment updates from Brightpearl at all.

    Fields
    2
    Required
    1
    Mapping tables
    1

    1 field is filled from live account data.

  • Payments

    Fields
    2
    Required
    1
    Mapping tables
    1

    2 fields are filled from live account data.

  • Refunds

    Toggle

    Switched on by “Create sales credits from returns”; its other fields are required only while it is on.

    Fields
    6
    Required
    2
    Mapping tables
    0

    2 fields are filled from live account data.

Questions

About Shopify + BrightPearl

What does 'split by location' mean?
Shopify groups an order's lines by fulfillment location into Fulfillment Orders. The order flow reads those groups and runs once per group, creating one BrightPearl sales order each. A two-location order shows as two runs in the run log.
How does a shipment fulfill the right part of the order?
The sales order carries the Shopify order id and fulfillment order id in its reference field. When BrightPearl marks the goods-out note shipped, the trigger reads them back and the fulfillment is created against that fulfillment order only.
Why must I set a Shopify location for the inventory flow?
BrightPearl warehouses and Shopify locations share no identifier, so the template cannot guess. It ships with a placeholder that Shopify rejects until you replace it with your real location id — a loud failure rather than a silent write to the wrong location.
What is in the settings tab?
The sections listed on this page. Most selects are filled from live BrightPearl and Shopify data, and the mapping tables enforce their own uniqueness rules. Flows do not run until the tab is confirmed.

Install Shopify + BrightPearl on a store you control.

Thirty minutes: connect both systems, confirm the settings tab, and watch the first order flow through in the run record.