Browser-local warehouse-order conversion
Convert EDI 940 to CSV, Excel, JSON, or XML
Export the canonical 148-field Smart Mapping or a separate source-ordered Raw representation.
Upload or paste an EDI 940 and choose Smart Mapping or Raw Mode. Automatic detection requires exact ST01=940. Smart Mapping emits ITEM, LX_ONLY, or SUMMARY rows with 148 ordered string fields; Raw Mode preserves physical source segments and order without canonical flattening.
Choose Smart Mapping or Raw Mode
Smart Mapping is useful when you need labeled order, item, product, party, reference, date, packing, routing, mark, and quantity evidence across supported 004010, 004030, and 005010 files. It has no Key/All split. Raw Mode is useful for inspecting each physical segment and element. Switching modes changes the row representation; it does not claim a lossless X12 round trip.
String-safe CSV, Excel, and JSON
CSV uses all 148 headers in canonical order and escapes commas, quotes, and newlines. Excel output is a real XLSX workbook produced through the browser's SheetJS path. Cells remain strings so leading zeros, very long W05 or product identifiers, MAN values, lexical decimals, and compact collection JSON are not converted to scientific notation or rounded by JavaScript numbers. JSON retains every canonical row with all 148 named fields and exact string values.
Understand XML output
XML is a serialization of the active canonical Smart or Raw row representation. It is not native X12 hierarchy, implementation-guide XML, or a lossless X12 round trip. Ordinary production-sized browser XML generation is supported. Extreme synthetic monolithic preparation around 50,000 very wide canonical rows can encounter the V8 maximum string-length boundary; that environment characterization is not advertised as an arbitrary public row limit.
Multi-file, release, and privacy boundaries
Multi-file conversion preserves FileName, FileOrdinal, SourceIndex, and transaction identity. Mixed supported families are isolated through their own adapters and schemas. A malformed 940 remains bounded so clean neighboring transactions do not inherit its context. Source EDI parsing, Smart Mapping, generic validation, safe summary creation, and export generation occur locally in the browser. Normal page, static-asset, quota, and configured analytics requests may still use the network, but EDI payload values are not intentionally sent as conversion input.
Start conversion
Open the EDI Converter, choose Smart or Raw, review the Data Editor, and download the chosen format. Use the EDI 940 canonical data map for field semantics, the W05 and W01 reading guide for row ownership, and the 940 validation guide for generic check boundaries.