Specific transaction sets, real production volume.
Not a generic EDI subset — the exact X12 sets, EDIFACT messages, and file formats your trading partners actually send, running in production today.
- 28 X12 sets in production
- 14 EDIFACT messages
- New doc types in 24 hours
- 28
- X12 transaction sets in production
- 14
- EDIFACT message types supported
- 100M+
- EDI transactions processed in 2025
- 24 hours
- to support a new document type
How it works
From transaction to action, automatically
When you receive an 830, Comparatio automatically creates orders, changes, or releases against existing orders in your ERP — no re-keying, no manual matching. The same document-driven logic runs across every X12 set, EDIFACT message, and file format below.
X12
28 X12 transaction sets, in production today
Every set below is running in real customer traffic — a production list backed by actual ticket data, not a roadmap.
- EDI 850
- EDI 855
- EDI 810
- EDI 856
- EDI 997
- EDI 820
- EDI 830
- EDI 832
- EDI 846
- EDI 852
- EDI 860
- EDI 861
- EDI 867
- EDI 844
- EDI 824
- EDI 753
- EDI 754
- EDI 180
- EDI 210
- EDI 214
- EDI 865
- EDI 870
- EDI 875
- EDI 940
- EDI 943
- EDI 944
- EDI 945
- EDI 947
EDIFACT
14 EDIFACT message types for international trade
For trading partners on the international standard, the same automation runs against EDIFACT messages instead of X12 sets.
- ORDERS
- ORDRSP
- ORDCHG
- INVOIC
- DESADV
- RECADV
- PRICAT
- INVRPT
- CONTRL
- APERAK
- REMADV
- SLSRPT
- DELFOR
- DELJIT
Beyond X12 and EDIFACT
Whatever format your partner sends, it’s covered
cXML, SAP IDOC, GS1/UCC-128 shipping labels, flat files, and JSON/REST all move through the same platform as X12 and EDIFACT — one system, not a separate integration project per format.
- cXML
- SAP IDOC
- GS1/UCC-128 labels
- CSV
- Excel
- Fixed-length
- Tab-delimited
- EZXML
- NAMM XML
- JSON/REST
FAQ
Transaction types, in practice
How does a document like an 830 actually get processed?
When you receive an 830, Comparatio automatically creates orders, changes, or releases against existing orders in your ERP — the same document-driven pattern runs across all 28 X12 sets and 14 EDIFACT messages the platform supports.
What if a trading partner sends a transaction set that isn’t on this list?
New document types are typically supported within 24 hours, and a brand-new trading-partner connection goes live in 2–4 weeks — so an unlisted set is a scheduling question, not a blocker.
Do you handle non-EDI formats like cXML or flat files?
Yes. Beyond X12 and EDIFACT, Comparatio processes cXML, SAP IDOC, GS1/UCC-128 shipping labels, CSV, Excel, fixed-length and tab-delimited files, EZXML, NAMM XML, and JSON/REST — all through the same platform, not a bolt-on tool.
How much of this runs in real production volume?
Comparatio processed more than 100 million EDI transactions in 2025 across 5,000+ trading-partner maps — these transaction sets aren’t a supported-in-theory list, they’re what’s moving today.
Send us your transaction set list.
If a partner sends it, chances are it’s already running in production — or it will be within 24 hours.