EDI

The EDI editor opens the interchanges trading partners send each other - UN/EDIFACT, ANSI X12 and TRADACOMS - as a tree of envelopes, messages, segment groups and segments, with the chosen segment's elements laid out by name, code meaning and format to read and change; as text coloured by its own delimiters; and as JSON or XML to take into other systems.

The envelopes are always checked: headers and trailers paired, counts and control references right. Give it a partner's implementation guide, as JSON, and every message is checked against it too - segments in order, mandatory elements present, values of the right kind and length, codes from their lists - each problem with its path. Acknowledge writes the CONTRL, 997, 999 or TA1 the receiver sends back. No standards content ships with it: the guides are yours.

Try it with your own files in confidence: they are opened by your browser, on your device. Nothing is uploaded, no copy reaches us or anyone else, and nothing is kept once you close this tab.

A buyer's orders, against its guide

A made-up EDIFACT order interchange, checked against the made-up buyer's own order guide, written for this page. One line's quantity is not a number and one party's role is not one the guide allows. Go to them, put them right, and write the CONTRL the sender would get back - before and after.

Go to the bad quantity Put both right Acknowledge Show it as JSON
Keyboard: in the tree, the arrow keys move and open, Enter goes to the segment's first value, Alt+Up and Down move a segment, Delete deletes it - and the counts are put right as you go.

An X12 purchase order, envelopes first

The same buyer's order as an ANSI X12 850, opened with no guide: the envelopes are still checked, and the transaction's segment count is one short. Correct the counts, write the 997 the supplier sends, put it all on one line as it travels, or take it as XML.

Correct the counts Write a 997 One line Show it as XML