Warehouse integration
Orders in your warehouse in minutes, despatches back without retyping
FTP EDI sits between the retailer and your WMS. Clarus connects natively; any system that can move a file or call an API connects in hours. The people on the despatch desk never see an EDI message.
The problem
The retailer and the warehouse never talk directly
Orders land in an EDI mailbox. Someone prints them, or exports them, and keys them into the WMS. Despatches happen in the warehouse and someone else builds the ASN from a spreadsheet, hours later.
Every handover is a delay and a chance to get a quantity wrong. When the retailer changes a depot code or a message version, the whole chain breaks and nobody is sure which link failed.
The fix is not more EDI. It is one system that owns the order from the retailer to the pick face and back again, and knows what state it is in.
Orders from Tesco, Sainsbury's, Lidl and Amazon flow into FTP EDI, which translates and checks them and routes them to Clarus WMS or any SFTP or API warehouse system. Despatch confirmations flow back the same way to become ASNs and invoices.
How it works
Connected in three steps
- 01
Tell us what your WMS speaks
Clarus connects natively. For anything else we take a sample export and import file, or your API documentation, and map it to the canonical order and despatch documents.
- 02
Replay real documents in test
We push last month's retailer orders through the mapping into your test environment and compare the despatch confirmations coming back, until both sides agree.
- 03
Switch to live and watch
Orders arrive in the warehouse within minutes of the retailer sending them. Despatches flow back to build ASNs and invoices. Every hop is on the document timeline.
What you get
One order, one state, every system agrees
Native Clarus WMS connector
Orders straight into the Clarus queue, despatch confirmations and stock back out, no file drops to babysit.
SFTP and file-based systems
CSV, fixed-width, XML or JSON on an SFTP folder. We poll, validate, archive and acknowledge each file.
REST and SOAP APIs
We call your API or you call ours. Idempotent, retried, logged with request and response for every call.
Field mapping you can see
Mappings are documented in the portal with test fixtures you can replay when you change your WMS.
Status both ways
Order accepted, picked, despatched, delivered, invoiced. Your WMS and the retailer see the same state.
Multiple sites and 3PLs
Route by retailer, depot or product range to different warehouses, including third-party ones on their own systems.
Retailers
What each retailer needs from your warehouse data
Best-before per line, batch numbers, pallet types and heights all come from the warehouse. The retailer pages list what each one insists on.
EDIFACT D96A orders, ASNs and invoices, with the ASN mandatory for every palletised load and EPOD replacing paper TRNs.
RequirementsTradacoms orders, delivery notes and invoices, with EDIFACT DESADV available for ASN-enabled depots.
RequirementsEDIFACT D96A with strict PO number patterns, best-before on every DESADV line and an approved pallet label specimen.
RequirementsANSI X12 4010: 850 orders, 855 acknowledgements, 856 ASNs and 810 invoices with 997 functional acknowledgements both ways.
RequirementsEDIFACT D96A orders, ASNs and invoices with GS1 logistic labels and a standard UK delivery note.
RequirementsEDIFACT D96A orders, ASNs and invoices with GS1 pallet labels and per-depot pallet rules.
RequirementsQuestions
Integration questions
Which warehouse systems does FTP EDI integrate with?
Clarus WMS natively. Any WMS or ERP that can exchange files over SFTP or expose an API connects through a mapping we build during onboarding, including SAP, NetSuite, Sage, Mintsoft, Peoplevox, Unleashed and in-house systems.
How long does a warehouse integration take?
Clarus is same day. File and API integrations typically take one to two weeks, most of which is replaying test documents and agreeing edge cases such as short picks and substitutions.
Can I use FTP EDI without a WMS?
Yes. Orders appear in the portal, you confirm despatch quantities and pallets on screen and FTP EDI builds the ASN, labels and invoice from that. Many suppliers start this way and connect a WMS later.
My 3PL runs the warehouse. Can they connect instead of me?
Yes. A 3PL can be connected as a warehouse for your company, with their own login and only their sites visible. FTP EDI began inside a 3PL, so this is the setup we know best.
Ready to connect your warehouse?
Tell us who you trade with and what you ship. We'll come back with a plan, a price and a go-live date within one working day.
No software to install. Live in days. UK-based support.