Connect OrderWise to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between OrderWise and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with OrderWise EDI
XEDI connects OrderWise with retailer EDI so orders arrive at the right point in your workflow, and despatch confirmations and invoices go back out carrying what each retailer requires.
One managed platform, no custom code
XEDI maps OrderWise to your trading partners and validates every document, so data flows straight into the systems your teams already use.
OrderWise is more than a warehouse system, which changes the question
OrderWise spans stock control, sales order processing, warehouse management and often accounts, in a modular way that differs by customer. That means an inbound retailer order has somewhere to go, but there is a genuine decision about where.
Drop it too early and it sits outside the controls your team relies on. Drop it too late and you have skipped a stage that decides pricing, allocation or credit. The right stage depends on which modules you run and how your order desk actually works.
Workflow stages are where an integration quietly goes wrong
The failure is rarely dramatic. An order lands, looks correct, and is missing something a later stage would have applied: a price break, an allocation rule, a customer-specific despatch instruction. It ships, and the discrepancy surfaces as a deduction.
So the stage an order enters at is decided deliberately at the start and validated against, rather than being whichever stage was easiest to write to. What OrderWise receives is a document that has already been checked against the retailer's rules.
What your team sees day to day
You get an EDI mailbox and a portal that works like an inbox, so retailer orders arrive in one place while the OrderWise work is still in progress.
The order becomes the despatch advice rather than being re-entered as one, amended where you are sending more or less than ordered, with SSCC labels for the pallets, and becomes the invoice on delivery, whose arrival is confirmed in the dashboard.
The integration sits over that workflow and automates it, so orders enter OrderWise at the agreed stage and despatch raises the outbound documents. Smaller operations run the portal alone; our API suits businesses wanting finer granularity; an OrderWise site normally wants the integration.
Documents you can exchange
- Retailer orders landing at the right OrderWise workflow stage
- Order acknowledgements returned to the retailer
- Despatch advice and ASN messages from OrderWise despatch
- Invoices raised from OrderWise
- Stock and price data where a retailer requires it
Built for OrderWise teams
Whoever owns OrderWise in your business, XEDI keeps EDI accurate and hands-off.
- OrderWise administrators
- Distributors and wholesalers
- Warehouse and despatch teams
- Sales order processing teams
- Finance teams handling invoice runs
OrderWise EDI document types
The set varies by retailer, but a distributor running OrderWise normally trades these.
| Document | What it carries | Direction |
|---|---|---|
| Purchase orders | Retailer demand entering OrderWise at the agreed workflow stage against the right customer, products and warehouse. | Retailer to OrderWise |
| Order acknowledgements | What OrderWise confirms after pricing and allocation, including amended and refused lines. | OrderWise to retailer |
| Advanced shipping notices | Pallet and carton detail from the OrderWise despatch, with SSCC labels for the retailer's goods-in. | OrderWise to retailer |
| Invoices | Raised from OrderWise and referenced to the order and despatch so the retailer can match them. | OrderWise to retailer |
| Credit notes | Credits issued from OrderWise against the invoice being corrected. | OrderWise to retailer |
| Stock and price data | Product, pack and price data published to retailers maintaining a catalogue against your range. | OrderWise to retailer |
How to connect OrderWise with EDI using XEDI
The build turns on where an order should enter your workflow, which is a decision rather than a default. The sequence below is what onboarding looks like from your side.
-
01
We scope which OrderWise modules you run and where in the workflow an inbound order should land.
-
02
We build the mapping between each retailer's documents and your OrderWise customers, products and warehouses.
-
03
We configure validation so an order is checked against the retailer's rules before it enters the workflow.
-
04
We prove the order, despatch and invoice flows against what each retailer requires and against how your workflow is configured.
-
05
You get documents landing at the right OrderWise workflow stage, and we keep them there.
Ready to connect OrderWise?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about OrderWise EDI
Common requirements
- OrderWise version, modules and integration access
- Customer, product and warehouse structure
- Workflow stages an inbound order should enter at
- Despatch and part-shipment handling
- The trading partners you deal with, or plan to
What we need from you to build it
Only what we cannot hold for you. Retailer requirements are already ours; what we need is how your OrderWise workflow runs.
- OrderWise access
- Version, modules in use and an integration account with rights to the order, despatch and invoice functions in scope.
- Workflow entry point
- Which stage an inbound retailer order should enter at, so nothing downstream that applies pricing or allocation is skipped.
- Customer and warehouse records
- Each retailer mapped to an OrderWise customer, with delivery points resolvable to the warehouse servicing them.
- Product and pack data
- Product codes against retailer identifiers at each packaging level, and the unit a retailer orders in.
- Which retailers you supply
- The relationships in scope now and next. What each requires is already ours.
Why suppliers choose XEDI for OrderWise
- Most retailers are connected already, so trading starts before the OrderWise workflow question is settled.
- Where an order enters your workflow is decided deliberately, so no stage that applies pricing or allocation is skipped.
- Documents are checked against the retailer's rules before they enter OrderWise, so a discrepancy does not surface later as a deduction.
- A new retailer is our build rather than another change request against your OrderWise configuration.
- SSCC labels and pallet hierarchy are produced to each retailer's format from the actual despatch.
- If a retailer raises a problem, they raise it with us and we correct it on your behalf.
Where in OrderWise do EDI orders land?
At the workflow stage you choose, which is decided during scoping rather than defaulted. The aim is that nothing downstream applying pricing, allocation or despatch rules is bypassed by an order arriving electronically.
Does it work with our OrderWise modules?
The build is scoped against the version and modules you run, because OrderWise is modular and where documents attach depends on which parts you have.
Can it handle part shipments?
Yes. How OrderWise represents a part shipment and what the retailer expects to see are agreed up front, so the despatch advice and invoice reflect what actually went out.
Plan your OrderWise EDI setup
Everything you need to scope, map and go live with OrderWise, in one place.