Connect Celigo to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between Celigo and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with Celigo EDI
XEDI adds retailer EDI alongside Celigo, which typically already connects your ERP to ecommerce and fulfilment, covering the one relationship type its prebuilt connectors do not.
One managed platform, no custom code
XEDI maps Celigo to your trading partners and validates every document, so data flows straight into the systems your teams already use.
Celigo covers your channels; retail is a different kind of counterparty
A typical Celigo estate connects an ERP to a webstore, a marketplace or two and maybe a third party logistics provider. Those connections share a useful property: the systems on the other end are software, and software behaves consistently.
A retailer is not software. It is an organisation with commercial terms, compliance rules and a deduction policy, and it will change what it requires on its own timetable. That is why retail EDI is usually the gap in an otherwise well-connected estate, and why filling it with another connector rarely works.
The value is that retail lands in the same place as everything else
What makes an integrated estate worth having is that one ERP record is the truth regardless of which channel produced it. A retail order that arrives through a separate process, into different fields, with its own reconciliation, undermines exactly that.
So retailer documents are mapped to the same records your marketplace and webstore orders already write to. Finance sees one set of numbers, operations sees one queue, and retail stops being the channel everybody handles differently.
What your team sees day to day
Retailer orders arrive into your existing flows, with an EDI mailbox and portal available for anyone who wants to look at a document directly.
The order becomes the despatch advice built from the real shipment with SSCC labels where the retailer requires them, and the invoice follows on delivery with its arrival confirmed in the dashboard.
Your Celigo flows carry on as they are. The EDI capability is bolted onto the estate you already run, and retailer requirements remain ours to keep current.
Documents you can exchange
- Retailer orders delivered into your Celigo flows
- Acknowledgements and despatch advice submitted from those flows
- Invoices raised through your existing integrations
- Catalogue and stock data exchanged with retailers
- Exceptions surfaced alongside your other integration errors
Built for Celigo teams
Whoever owns Celigo in your business, XEDI keeps EDI accurate and hands-off.
- NetSuite-centred businesses
- Ecommerce and operations teams
- Integration administrators
- Finance teams reconciling channels
- Brands adding retail to existing online channels
Celigo EDI document types
These land in the same ERP records your other channels already use.
| Document | What it carries | Direction |
|---|---|---|
| Retailer orders | Demand arriving into the same order records your ecommerce channels write to. | XEDI to Celigo |
| Acknowledgements | Confirmation of what will be supplied, submitted from your flows. | Celigo to XEDI |
| Despatch advice | Shipment detail from fulfilment, labelled to each retailer's standard. | Celigo to XEDI |
| Invoices | Billing raised through your existing integrations and validated before sending. | Celigo to XEDI |
| Catalogue and stock data | Product and availability figures published to retailers expecting them. | Either direction |
| Exceptions | Retailer rejections surfaced alongside the integration errors your team already reviews. | XEDI to Celigo |
How to connect Celigo with EDI using XEDI
The goal is that a retail order is not handled differently from any other. The sequence below is what onboarding looks like from your side.
-
01
We establish what Celigo already connects, since retail EDI is usually the gap rather than the whole picture.
-
02
We agree where retailer documents enter and leave your flows.
-
03
We connect so trading data reaches the same ERP records your other channels already write to.
-
04
We prove the flows so a retailer order behaves consistently with a marketplace one.
-
05
You get retail trading covered without a second integration philosophy.
Ready to connect Celigo?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about Celigo EDI
Common requirements
- What Celigo connects today
- Where retailer documents should attach
- How ERP records are already written
- Error handling conventions in use
- The retailers in scope
What we need from you to build it
Only what we cannot decide for you. Retailer requirements are ours to hold and maintain.
- Existing connections
- What Celigo already connects, since retail EDI is normally the gap rather than a replacement.
- Attachment points
- Where retailer documents should enter and leave, so they reach the same records as other channels.
- ERP record conventions
- How your existing flows write orders, so retail does not create a second pattern.
- Error handling
- How integration errors are reviewed today, so retailer rejections appear in the same place.
- The retailers in scope
- Which relationships this covers. Their requirements are already held by us.
Why suppliers choose XEDI for Celigo
- Retailers are generally connected already, so filling the retail gap is quick rather than another integration project.
- Retail lands in the same ERP records as your other channels rather than becoming a parallel process.
- Retailer compliance and deduction rules are ours, which no connector covers.
- Your Celigo flows continue unchanged and see one consistent source.
- Adding a retailer does not require a new integration or a new flow.
- If a retailer raises a problem, it comes to us rather than into your error queue.
Does this replace our Celigo integrations?
No. Celigo continues connecting your ERP to ecommerce and fulfilment. What it adds is the retail relationship, which behaves unlike a software endpoint and is usually the gap in an otherwise connected estate.
Will retail orders look different in our ERP?
They should not, and that is the point. Retailer documents are mapped to the same records your other channels write to, so finance and operations see one set of numbers.
Can we handle retailers with a Celigo connector instead?
Connectors work well against software that behaves consistently. A retailer is an organisation with commercial terms and a deduction policy that changes on its own schedule, which is a different problem.
Plan your Celigo EDI setup
Everything you need to scope, map and go live with Celigo, in one place.