Connect OnBuy to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between OnBuy and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with OnBuy EDI
XEDI connects OnBuy alongside your EDI trading partners, so UK marketplace demand and retail demand are worked in one place and fulfilled from a single stock position.
One managed platform, no custom code
XEDI maps OnBuy to your trading partners and validates every document, so data flows straight into the systems your teams already use.
A second marketplace is where channel management starts to hurt
One marketplace is manageable from its own dashboard. A second, plus a website, plus a retail account or two, is where it stops working. Each has its own screen, its own despatch process and its own view of stock, and the person reconciling them is usually the person who should be doing something else.
OnBuy is frequently that second channel for UK sellers. The value here is not in OnBuy specifically, it is in stopping each new channel from adding another separate routine.
Retail accounts change the stakes
Marketplace demand is forgiving in a way retail is not. A consumer order fulfilled late is a poor review; a retail delivery that falls short is a deduction and a conversation about your listing.
So when both draw on the same stock, the retail commitment has to be protected deliberately. Bringing OnBuy into the same place as your EDI accounts makes that trade-off something you decide rather than something you discover.
What your team sees day to day
You get an EDI mailbox and a portal that works like an inbox, carrying retail orders, with marketplace demand visible beside them rather than behind another login.
For retail accounts the chain runs as usual: the order becomes the despatch advice, amended where the delivery differs, with SSCC labels for the pallets, and becomes the invoice on delivery, whose arrival is confirmed in the dashboard.
Where you run a system that can carry it, the integration automates both sides. Many sellers at this stage work the portal alone, which is a perfectly reasonable place to stay.
Documents you can exchange
- Marketplace orders retrieved from OnBuy
- Despatch and tracking confirmations returned to the marketplace
- Stock and price updates kept consistent across channels
- Retailer EDI orders alongside marketplace demand
- Invoices where your retail partners require them
Built for OnBuy teams
Whoever owns OnBuy in your business, XEDI keeps EDI accurate and hands-off.
- UK sellers across several channels
- Small and mid-sized brands
- Operations and despatch teams
- Customer service teams
- Finance teams reconciling channel income
OnBuy EDI document types
Marketplace flows are retrieved from OnBuy; the EDI documents belong to your retail accounts.
| Document | What it carries | Direction |
|---|---|---|
| Marketplace orders | Consumer demand retrieved from OnBuy and brought alongside retail demand rather than handled in isolation. | OnBuy to you |
| Despatch confirmations | Shipment and tracking returned so the customer is updated and your seller metrics hold up. | You to OnBuy |
| Stock and price updates | One position across channels, so marketplace sales do not consume stock promised to a retail account. | You to each channel |
| Retailer purchase orders | EDI demand from retail accounts, arriving in the same place as marketplace volume. | Retailer to you |
| Despatch advice | Pallet and carton detail for retail deliveries, carrying the labels their goods-in scans. | You to retailer |
| Invoices | Raised for retail accounts against the despatch; marketplace settlement comes from OnBuy. | You to retailer |
How to connect OnBuy with EDI using XEDI
The aim is that adding a channel does not add another separate routine. The sequence below is what onboarding looks like from your side.
-
01
We scope how you sell on OnBuy and how those orders are fulfilled today.
-
02
We connect OnBuy alongside your existing partner connections.
-
03
We map marketplace listings to the same product records your retail accounts order against.
-
04
We prove marketplace and retail flows together so stock and despatch stay consistent.
-
05
You get one place for demand, and we keep it aligned as your channel mix changes.
Ready to connect OnBuy?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about OnBuy EDI
Common requirements
- OnBuy seller account and API access
- How marketplace orders are fulfilled
- Product identifiers across channels
- Stock allocation between channels
- Your retail relationships
What we need from you to build it
Only what we cannot hold for you. Retail account requirements are already ours; what we need is how you sell and ship today.
- OnBuy account
- Seller account and API access, and whether you fulfil directly or through a third party.
- Fulfilment routine
- How marketplace orders are picked and despatched today, since that is what the integration replaces.
- Product identity across channels
- OnBuy listings mapped to the same records your retail accounts order against.
- Stock allocation
- How much stock is protected for retail commitments against marketplace sales.
- Your retail relationships
- The accounts you supply or are pitching to. What each of them requires is already held by us.
Why suppliers choose XEDI for OnBuy
- The retailers you supply are very likely connected already, so adding retail alongside a marketplace is not a long job.
- Adding a channel stops meaning adding another screen and another despatch routine.
- Retail commitments are protected against marketplace velocity by a rule rather than by memory.
- Your retail accounts connect through the same platform, so a listing win is not a separate project.
- You can run entirely from the portal at this stage and add an integration later without the retailer noticing.
- If a retail account raises a problem, it comes to us rather than to a small team already stretched.
Does OnBuy use EDI?
No. It is a consumer marketplace and orders are retrieved through its seller interfaces. The EDI in your business belongs to your retail accounts, and both are handled in one place here.
We are small. Is this overkill?
Usually not, because the alternative is a separate routine per channel. Many sellers work entirely from the portal and add an integration only when re-keying becomes the constraint.
Can you connect our other marketplaces too?
Yes. The point is one place for demand rather than a dashboard each, and retail accounts run through the same platform.
Plan your OnBuy EDI setup
Everything you need to scope, map and go live with OnBuy, in one place.