Connect SnapFulfil to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between SnapFulfil and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with SnapFulfil EDI
XEDI connects SnapFulfil with retailer and carrier EDI so orders arrive into the warehouse ready to pick, and despatch confirmations go back carrying the pallet detail and labels each retailer requires.
One managed platform, no custom code
XEDI maps SnapFulfil to your trading partners and validates every document, so data flows straight into the systems your teams already use.
A configurable WMS rewards getting the document boundary right
SnapFulfil is built to be configured to an operation rather than the other way round, which is its strength. It also means the shape of the warehouse changes as you tune it: zones move, pick strategies change, sites are added.
An EDI connection built tightly against a particular configuration inherits all of that churn. Keeping the retailer-specific half outside the warehouse means what SnapFulfil receives is one consistent order per type, and re-tuning the operation does not put trading relationships at risk.
Inbound is half the problem and usually the neglected half
Most EDI attention goes on despatch, but a warehouse lives or dies on what it knows is arriving. An advance shipping notice from your own supplier lets goods-in book labour, pre-allocate space and receive against an expectation rather than counting a lorry into an aisle.
The same messages that tell a retailer what you sent can tell you what is coming, and SnapFulfil can act on it. Where a supplier sends nothing, the portal gives you somewhere to record what is expected so receipt is still checked against something.
What your warehouse sees day to day
You get an EDI mailbox and a portal that works like an inbox. Orders arrive, your team is notified, and the warehouse can work them before the SnapFulfil integration is finished.
The order becomes the despatch advice from what was actually picked, amended where quantities differ, 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 SnapFulfil ready to pick and despatch raises the outbound documents. Smaller operations run the portal alone; our API suits businesses wanting finer granularity; a configured warehouse usually wants the integration.
Documents you can exchange
- Retailer orders landing as SnapFulfil orders
- Order acknowledgements returned to the retailer
- Despatch advice and ASN messages from SnapFulfil despatch
- Advance shipping notices for inbound goods
- Invoices raised against the despatch
Built for SnapFulfil teams
Whoever owns SnapFulfil in your business, XEDI keeps EDI accurate and hands-off.
- Warehouse and operations managers
- Third party logistics operators
- Retail suppliers with their own distribution
- Inbound and goods-in teams
- Businesses scaling warehouse volume quickly
SnapFulfil EDI document types
Outbound and inbound both matter here, which is not true of every integration on this site.
| Document | What it carries | Direction |
|---|---|---|
| Purchase orders | Retailer demand landing as a SnapFulfil order against the right products, quantities and delivery requirement. | Retailer to SnapFulfil |
| Order acknowledgements | What will be supplied once stock is committed in the warehouse. | SnapFulfil to retailer |
| Advanced shipping notices | Pallet and carton structure from the actual despatch, with SSCC labels for the retailer's receiving bay. | SnapFulfil to retailer |
| Inbound shipping notices | What a supplier is sending you, so goods-in can plan labour and receive against an expectation. | Supplier to SnapFulfil |
| Receiving advice | What was actually received against what was expected, in either direction. | Either direction |
| Invoices | Raised against the despatch and referenced so the retailer can match them. | SnapFulfil to retailer |
How to connect SnapFulfil with EDI using XEDI
The build covers both directions, because a warehouse needs to know what is arriving as much as what it is sending. The sequence below is what onboarding looks like from your side.
-
01
We scope which SnapFulfil sites, zones and clients each retailer relationship runs through.
-
02
We build the mapping between each retailer's documents and your SnapFulfil products, locations and despatch configuration.
-
03
We configure validation so an order is checked against the retailer's rules before it enters the warehouse.
-
04
We prove the order, despatch and inbound flows against what each retailer requires and against how your site is configured.
-
05
You get orders arriving ready to pick, and we keep the configuration aligned as your operation is retuned.
Ready to connect SnapFulfil?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about SnapFulfil EDI
Common requirements
- SnapFulfil site and integration access
- Product, location and zone structure
- Pallet and carton configuration
- Inbound booking and receipt rules
- 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 warehouse is configured.
- SnapFulfil access
- Integration credentials with rights to the order, stock, receipt and despatch functions on the sites in scope.
- Site and zone structure
- Which sites and zones each relationship draws on, since allocation and despatch follow them.
- Pallet and carton configuration
- Units per carton and cartons per pallet with barcodes at each level, because the retailer's goods-in reads that hierarchy.
- Inbound expectations
- Which suppliers send advance notice and which do not, so goods-in has something to receive against either way.
- Which retailers you supply
- The relationships in scope now and next. Their requirements are already ours.
Why suppliers choose XEDI for SnapFulfil
- Partners on both sides are commonly connected already, so inbound and outbound can begin before the SnapFulfil work concludes.
- Re-tuning the warehouse does not put trading relationships at risk, because the retailer-specific half sits outside it.
- Inbound notices are handled as well as outbound, so goods-in receives against an expectation rather than counting a lorry in.
- Pallet hierarchy and SSCC labels are produced to each retailer's format rather than a generic template.
- A new retailer is built and verified by us before it carries live volume.
- If a retailer raises a problem, we are told on your behalf and put it right before it reaches your operation.
Can XEDI handle inbound as well as outbound?
Yes. Advance shipping notices from your own suppliers can reach SnapFulfil so goods-in can plan and receive against an expectation, which most EDI implementations neglect in favour of despatch alone.
Will re-configuring our warehouse break the EDI flow?
It should not. Retailer-specific rules sit with us rather than inside SnapFulfil, so zones, pick strategies and sites can change while what the retailer receives stays constant.
Do you support multi-site operations?
Yes. Each retailer relationship is mapped to the sites and zones that service it, so orders are allocated where they can actually be fulfilled.
Plan your SnapFulfil EDI setup
Everything you need to scope, map and go live with SnapFulfil, in one place.