Connect Brightpearl to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between Brightpearl and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with Brightpearl EDI
XEDI connects Brightpearl with retailer EDI so wholesale orders land against the right accounts and price lists, and despatch confirmations and invoices go back out without anyone re-entering them.
One managed platform, no custom code
XEDI maps Brightpearl to your trading partners and validates every document, so data flows straight into the systems your teams already use.
Brightpearl already runs several channels, and wholesale behaves unlike all of them
Brightpearl exists to hold orders, stock and accounting across a mix of channels: a webstore, marketplaces, sometimes physical retail. Wholesale looks like another channel and is not one, because the counterparty sets the terms rather than accepting yours.
A retailer specifies identifiers, delivery windows, document formats and labelling, and enforces them with deductions. So while the order can live in Brightpearl beside everything else, what surrounds it has obligations no other channel imposes.
Price lists and accounts decide whether an order is even right
Wholesale pricing in Brightpearl runs through price lists attached to accounts, which suits trade well. An EDI order arriving with a retailer's own item codes has to resolve to your products and to the price list agreed with that account.
If it resolves to the wrong list the order is created at a number nobody agreed, and the discrepancy usually surfaces at invoice rather than at order. That mapping is maintained by us, along with the retailer's identifiers, so it holds as your catalogue changes.
What your team sees day to day
You get an EDI mailbox and a portal that behaves like an inbox, so retailer orders arrive separately from your other channels and are handled to the retailer's requirements.
The order becomes the despatch advice built from goods-out, adjusted where the delivery differs, carrying SSCC pallet labels, and then the invoice once delivered, with its delivery confirmed in the dashboard.
The integration sits over that workflow and automates it, so orders land as Brightpearl sales orders and goods-out raises the outbound documents. Smaller brands run the portal alone; our API suits businesses wanting finer granularity across channels.
Documents you can exchange
- Retailer orders landing as Brightpearl sales orders
- Order acknowledgements returned to the retailer
- Despatch advice and ASN messages from goods-out
- Invoices raised from Brightpearl
- Stock availability where a retailer plans against your figures
Built for Brightpearl teams
Whoever owns Brightpearl in your business, XEDI keeps EDI accurate and hands-off.
- Multi-channel retail brands
- Wholesale and distribution teams
- Operations managers across channels
- Finance teams handling wholesale terms
- Brands adding retail alongside direct and marketplace sales
Brightpearl EDI document types
These are the wholesale flows; your other Brightpearl channels are unaffected.
| Document | What it carries | Direction |
|---|---|---|
| Purchase orders | Retailer demand landing as a Brightpearl sales order against the right account, products and price list. | Retailer to Brightpearl |
| Order acknowledgements | What Brightpearl can commit once stock across your warehouses is checked, including anything short. | Brightpearl to retailer |
| Advanced shipping notices | Pallet and carton detail from goods-out, with SSCC labels a retailer's receiving bay scans. | Brightpearl to retailer |
| Invoices | Raised from Brightpearl carrying the order and delivery references a retailer matches against. | Brightpearl to retailer |
| Credit notes | Raised in Brightpearl against the original invoice when a delivery is rejected or falls short. | Brightpearl to retailer |
| Stock availability | Available quantity by warehouse for retailers planning replenishment against your figures. | Brightpearl to retailer |
How to connect Brightpearl with EDI using XEDI
Most of the work is resolving retailer identifiers to your products and orders to the right price list. The sequence below is what onboarding looks like from your side.
-
01
We scope which Brightpearl channels, warehouses and price lists carry wholesale.
-
02
We build the mapping between each retailer's documents and your accounts, products and price lists.
-
03
We configure validation so an order is checked against the retailer's terms before it becomes a sales order.
-
04
We prove the order, goods-out and invoice flows against what each retailer requires and against how your account is set up.
-
05
You get wholesale arriving without re-entry, and we keep it right as channels and products change.
Ready to connect Brightpearl?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about Brightpearl EDI
Common requirements
- Brightpearl account and API access
- Channel, warehouse and price list structure
- Product and variant identifiers
- Goods-out and part-shipment rules
- The retail accounts you supply
What we need from you to build it
Only what we cannot hold for you. Retailer requirements sit with us; what we need is how your Brightpearl account is arranged.
- Brightpearl access
- Account and API access covering orders, products, stock and goods-out.
- Account and price list structure
- Which account each retailer maps to and which price list applies, because pricing resolves through them.
- Product identifiers
- Products and variants against retailer identifiers at each packaging level, and the unit they order in.
- Goods-out rules
- How despatch is recorded and what a retailer should see when a delivery is short.
- The retail accounts you supply
- Who you trade with now and intend to. What each of them requires is already ours.
Why suppliers choose XEDI for Brightpearl
- Most retail accounts are connected already, so a listing can start trading before Brightpearl is mapped.
- Wholesale orders resolve to the right account and price list rather than being created at a number nobody agreed.
- Retailer identifiers are maintained against your products as the catalogue changes.
- Wholesale is handled to the retailer's obligations rather than like another sales channel.
- A new retail account is our build rather than a job for a team already running several channels.
- If a retailer raises a problem, it comes to us and we resolve it before it becomes a deduction.
Can Brightpearl handle wholesale EDI orders?
Yes. Orders land as Brightpearl sales orders against the account and price list agreed with that retailer, and despatch and invoicing follow from goods-out as they would for any other order.
How is wholesale kept apart from our other channels?
Wholesale arrives separately and is handled to the retailer's requirements, because a retail account enforces identifiers, labelling and timing that no other channel imposes.
What if a retailer uses their own item codes?
They generally do. Their identifiers are mapped to your products at each packaging level and maintained by us, so a catalogue change does not quietly break their orders.
Plan your Brightpearl EDI setup
Everything you need to scope, map and go live with Brightpearl, in one place.