CSV
One ordered 215-column header and one record per canonical row.
Ship-notice converter guide
Convert EDI 856 to CSV, Excel, JSON, or XML
Export supported shipment hierarchy and logistics facts through one canonical 215-field Smart Mapping schema.
Upload or paste an EDI 856 and choose Smart Mapping or Raw Mode. Smart Mapping emits one row per physical HL, or one SUMMARY row when no HL exists, for generic 004010, 004030, and 005010 files. Review the resolved hierarchy in the Viewer or Data Editor before downloading.
Smart Mapping versus Raw Mode
Smart Mapping resolves supported shipment, order, tare, pack, item, other, and summary row types while retaining source provenance and deterministic JSON collection fields. Raw Mode remains a physical segment-and-element representation; it is not an “All Fields” Smart schema.
CSV, XLSX, JSON, and XML use the current rows
Excel (XLSX)
A real workbook whose lexical identifiers, including leading zeros and long MAN/SSCC values, remain strings.
JSON
Canonical row objects with collection columns retained as deterministic JSON strings.
XML
Escaped canonical-row XML, not native X12 hierarchy XML, lossless EDI XML, or an implementation-guide schema.
Review hierarchy, validation, and safe summary evidence
Before download, inspect hierarchy-resolution statuses, source locations, generic X12/856 findings, and conservative counts or distributions. The summary does not calculate authoritative shipment totals, fulfillment, delivery performance, ASN acceptance, partner compliance, or GS1 compliance.
Browser-local processing and next steps
Parsing, mapping, validation, summary, editing, and export occur in the browser; source EDI is not uploaded for conversion. Ordinary site, account, and quota requests can still use application services, so this wording is a processing boundary rather than an absolute security guarantee.
Use the EDI 856 canonical data map for field semantics, the HL hierarchy reading guide for source ownership, and the 856 validation guide for check scope.