EDI Reader — EDIFACT & X12 decoder

Your partner rejected the file. You have 400 segments, a 300-page implementation guide, and a cut-off time.

Counting component positions by hand to find out what QTY+12:480:PCE means is not hard. It is slow, and you do it again at every incident.

EDI Reader opens any EDIFACT or X12 file in VS Code and shows it as a named tree: every segment titled, every qualifier and code translated, every element in its place. One second, no setup, nothing leaves your machine.

What you get for free

• Decode EDIFACT and X12 — any directory version; segment and code names come from the UN/EDIFACT (D93A→D01B) and ANSI X12 (4010→8030) dictionaries
• Every segment named — NAD becomes Name and address, BY becomes Buyer, 12 in QTY becomes Despatch quantity
• A tree you can navigate — click a node, jump to the exact characters in the file; fold a group, follow the loop structure
• Big interchanges — 190,000 segments (4 MB) decode in about a second; files up to 8 MB are handled
• 100% local — no account, no upload, no telemetry. Your trading data never leaves your machine.

Open a .edi, .edifact or .x12 file, or run EDI: Decode the current file from the command palette.

What EDI Reader Pro adds — EUR 19, one-off

Get EDI Reader Pro — EUR 19 · one payment, no subscription, up to 5 machines, no expiry.

The key is verified once online, then the extension works offline. Refund within 14 days, no questions asked.

Why not just the syntax highlighter you already have

Highlighting colours the delimiters. It does not tell you that UNH+1+DESADV:D:96A:UN is a despatch advice, that a mandatory segment is missing, or that the partner's trailer announces 18 line items when the file has 17. That is the difference between reading the file and knowing what is wrong with it.

Checking a message against its type is a Pro feature.

Frequently asked

Does my data go anywhere? No. Parsing, validation and export all run inside VS Code. The only network call the extension ever makes is the licence check when you activate Pro, then at most once a day. No file content, ever.

Which message types are supported? Decoding works on any EDIFACT or X12 interchange, whatever the message type. Validation covers the common message types first — EDIFACT ORDERS, DESADV, INVOIC and X12 850, 856, 810 — and grows with each release. Unknown types still decode and still get the structural checks (control counts, reference matching, segment terminators).

Is this an EDI translator or a certification tool? No. EDI Reader reads, decodes and checks files against public message dictionaries. It does not map to your ERP, it does not send anything to a VAN, and it does not certify compliance with a partner's implementation guide.

Does it work in Cursor, VSCodium, Windsurf, code-server? Yes — the extension is also published on Open VSX.

One key, several machines? Up to 5 machines with the same key. Laptop, desktop, work VM.

Install

Search EDI Reader in the Extensions view, or:

ext install novair.edi-reader

En français

EDI Reader décode vos fichiers EDIFACT et X12 directement dans VS Code : chaque segment nommé, chaque code traduit, rien n'est envoyé nulle part. L'interface est en français si VS Code l'est.

Gratuit : décoder un fichier en arbre lisible, sans limite. Pro, 19 € en une fois : contrôle du message selon son type, export CSV/JSON, contrôle d'un dossier entier, rapport de contrôle. Clé valable sur 5 postes, sans limite de durée, remboursement 14 jours sans justification.

Page produit et documentation : edi.novair.app/fr/

Publisher: Maxime Martin — pro.maximemartin@gmail.com · Privacy · Support