Connect Blue Yonder to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between Blue Yonder and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with Blue Yonder EDI
XEDI connects Blue Yonder with the EDI traffic a warehouse actually runs on: inbound notices telling you what is arriving, receiving advice confirming what did, despatch advice going out, and inventory reported to whoever plans against it.
One managed platform, no custom code
XEDI maps Blue Yonder to your trading partners and validates every document, so data flows straight into the systems your teams already use.
A warehouse cares about what is arriving, not only what it sends
Most EDI work is written from the supplier's point of view: how to send a retailer an order confirmation and a despatch advice. A Blue Yonder site is frequently on the other side of that, receiving goods rather than shipping them to a buyer.
So the documents that matter are different. An inbound shipping notice lets goods-in book labour and space against a known delivery. Receiving advice tells the sender what actually turned up. Inventory reports let a partner plan against your real position rather than an estimate.
Handling units are the vocabulary, and they have to survive the journey
Blue Yonder thinks in handling units, locations and nested containers, which is exactly what a distribution operation needs. A trading partner sends a hierarchy in their own terms, and if the two do not reconcile the delivery is broken down and counted manually.
That is the expensive outcome, because it consumes the labour the notice was supposed to save. The mapping resolves each partner's structure to yours so a pallet arrives as a pallet rather than as a puzzle.
What your site sees day to day
Partner documents reach an EDI mailbox and a portal that behaves like an inbox, so an unexpected delivery or a missing notice is visible to the people who need it rather than buried in a queue.
Outbound, what leaves becomes the despatch advice built from the actual movement, adjusted where quantities changed, carrying SSCC labels at pallet level, with the invoice following where you raise one and its delivery confirmed in the dashboard.
The integration sits over that workflow and automates it against Blue Yonder. Larger operations commonly take our API as well, since planning teams want finer granularity than documents alone provide.
Documents you can exchange
- Inbound shipping notices from your suppliers
- Receiving advice confirming what was booked in
- Despatch advice and ASN messages to customers and carriers
- Inventory reports to partners planning against your figures
- Purchase orders and invoices where Blue Yonder carries them
Built for Blue Yonder teams
Whoever owns Blue Yonder in your business, XEDI keeps EDI accurate and hands-off.
- Warehouse and distribution centre managers
- Supply chain planners
- Goods-in and despatch teams
- Third party logistics operators
- Retailers running their own distribution
Blue Yonder EDI document types
Inbound matters as much as outbound here, which is not true of most integrations on this site.
| Document | What it carries | Direction |
|---|---|---|
| Inbound shipping notices | What a supplier is sending you, so goods-in can plan labour and space before the vehicle arrives. | Supplier to Blue Yonder |
| Receiving advice | What was actually booked in against what was expected, returned to the sender. | Blue Yonder to supplier |
| Despatch advice | Handling unit and pallet detail for what is leaving, with SSCC labels for the receiving site. | Blue Yonder to customer |
| Inventory reports | Stock by location for partners planning replenishment against your position. | Blue Yonder to partner |
| Purchase orders | Demand where Blue Yonder carries ordering as well as execution. | Either direction |
| Invoices | Raised where you bill for goods or for the handling itself. | Blue Yonder to customer |
How to connect Blue Yonder with EDI using XEDI
The build covers both directions because a distribution site is judged on what it receives as much as what it ships. The sequence below is what onboarding looks like from your side.
-
01
We scope which Blue Yonder modules you run and which sites carry EDI traffic.
-
02
We build the mapping between partner documents and your locations, items and handling unit structures.
-
03
We configure validation so an inbound notice is checked before goods-in plans against it.
-
04
We prove the inbound, receiving and despatch flows against what each partner requires and against how your sites operate.
-
05
You get goods-in working from expectations rather than surprises, and despatch documented accurately.
Ready to connect Blue Yonder?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about Blue Yonder EDI
Common requirements
- Blue Yonder modules and site scope
- Location and item structure
- Handling unit and pallet configuration
- Booking and receipt rules
- The suppliers and customers whose documents you exchange
What we need from you to build it
Only what we cannot hold for you. Partner requirements are already ours; what we need is how your sites are organised.
- Modules and sites
- Which Blue Yonder modules you run and which sites exchange documents, since execution and planning are separate concerns.
- Location and item structure
- How locations and items are identified, against the references partners use on their documents.
- Handling unit configuration
- Pallet and carton nesting, so a partner's hierarchy resolves to yours rather than being broken down by hand.
- Booking and receipt rules
- How deliveries are booked and received, so an inbound notice can be checked against something meaningful.
- The suppliers and customers whose documents you exchange
- Both directions, now and next. Their formats are already held by us.
Why suppliers choose XEDI for Blue Yonder
- The suppliers and customers you exchange documents with are frequently connected already, so inbound notices can start before the Blue Yonder work is done.
- Inbound notices are treated as first-class, so goods-in plans against expectations rather than reacting to arrivals.
- Handling unit structures are reconciled in the mapping, which is what stops a pallet being counted manually.
- Receiving advice goes back to senders automatically, so discrepancies are raised while they can still be resolved.
- Adding a trading partner is our work rather than a change request against your Blue Yonder configuration.
- If a partner reports a problem, it comes to us and is rectified before it reaches your operations team.
Can you handle inbound as well as outbound documents?
Yes, and for a Blue Yonder site that is usually the more valuable half. Inbound shipping notices let goods-in plan labour and space, and receiving advice tells the sender what actually arrived.
Do you support handling unit hierarchies?
Yes. Each partner's pallet and carton structure is reconciled to how Blue Yonder holds handling units, so a delivery does not have to be broken down and counted to be understood.
We run several sites. Does that complicate it?
Site scope is established at the start, since partners often deal with specific locations. Documents are routed to the site that will actually handle the goods.
Plan your Blue Yonder EDI setup
Everything you need to scope, map and go live with Blue Yonder, in one place.