Convert JSON shipment files into retailer-ready EDI

What the control should check

1. 01Detect the source format from the uploaded bytes, not only its filename.
2. 02Show every proposed source-to-canonical field and confidence before activation.
3. 03Require purchase order, shipment reference, item, quantity and container confirmation.
4. 04Store the approved recipe per workspace and retailer route.
5. 05Quarantine unknown layouts without consuming the rest of a 1,000-file batch.
6. 06Render and validate each partner output independently.

Working example

{"shipment":"ASN-1042","po":"PO-77821","lines":[{"sku":"SKU-104","qty":12,"uom":"EA","sscc":"000123456789012343"}]}

This is representative source evidence, not a universal schema. The first file creates a proposal; only an explicitly confirmed exact layout becomes reusable.

Failure modes worth catching

• A nested array is serialized as text instead of expanded to lines.
• The same key has different types in different records.
• Null and omitted values are treated as equivalent.
• A transport-level success is mistaken for retailer acceptance.

Put it into the dispatch workflow

1. 1Create the receiving partner route and enter its account-specific identifiers.
2. 2Upload one representative JSON file and inspect the proposed mapping.
3. 3Confirm the critical fields; optional fields may remain unmapped.
4. 4Send matching files over SFTP, authenticated email or API with the partner code.
5. 5Collect each converted output, validation result or quarantine reason from the channel response.