EDIFACT
EDIFACT (Electronic Data Interchange for Administration, Commerce and Transport) is the United Nations’ international EDI standard — the message dictionary that defines how purchase orders, invoices, and shipping documents are structured when systems in different countries and industries talk to each other.
What is EDIFACT?
EDIFACT (Electronic Data Interchange for Administration, Commerce and Transport) is the United Nations’ international EDI standard — the message dictionary that defines how purchase orders, invoices, and shipping documents are structured when systems in different countries and industries talk to each other.
Amazon supports it as one of the official EDI formats: it’s the standard of record across EMEA vendor operations (Europe, Middle East, Africa) and in several other regions — the dialect your integration speaks if your supply chain lives outside North America’s ANSI X12 orbit.
EDIFACT in the Amazon context
What flows in an Amazon EDIFACT setup: purchase orders in, confirmations out, despatch advices (the European cousin of the ASN) ahead of every delivery, invoices transmitted electronically, delivery confirmations synchronized, and inventory updates where programs require them. The messages themselves have cryptic names (ORDERS, ORDRSP, DESADV, INVOIC) — your integration partner’s job is that you never need to memorize them. What matters managerially: EMEA vendor programs assume EDIFACT-capable connectivity, and the chargeback categories around confirmation and despatch timing treat failures exactly as the North American flows do.
Choosing and running an EDIFACT setup
The practical path for a vendor expanding into EMEA: decide between a managed EDI provider (they operate the translation and monitoring; you get portal visibility) versus in-house integration (more control, more engineering), confirm which document types Amazon requires for your specific program, and test end-to-end with Amazon’s onboarding process before the first live PO. The operational discipline afterward is identical to any EDI: transmission monitoring, failure alerts, and exception paths. The specific EDIFACT trap is regional mapping drift — variations in how partners implement the standard — so the integration’s testing phase deserves real purchase-order scenarios, not just a successful ping.
In practice
A vendor lands its first EMEA listings and discovers the local vendor team expects EDIFACT for orders and despatches. A managed provider is engaged; the onboarding maps their catalogue and tests ORDERS, ORDRSP, and DESADV flows against real scenarios; live POs begin three weeks later with zero confirmation misses in month one. The vendor never learns the message names — the provider’s monitoring console shows green. That invisibility is the success condition.
How Harpy Media helps
Multi-region vendor onboarding — EDI standard selection, provider management, and live-scenario testing — is part of how we take clients into EMEA without operational surprises.
EDIFACT FAQ
What is EDIFACT?
The United Nations’ international EDI message standard, used widely in EMEA — defining the formats for orders, invoices, and shipping documents.
How is EDIFACT different from X12?
Two dialects of the same idea: X12 is the North American standard, EDIFACT the international one; Amazon supports both, with EDIFACT dominant in EMEA programs.
Do Amazon vendors need EDIFACT?
Vendors operating in EMEA programs generally need EDIFACT-capable EDI — for purchase orders, confirmations, despatches, and invoices.
Want these numbers watched for you, every week?
Book Free Consultation