Build a retail EDI 856 Advance Ship Notice (ASN) generator and submit it to a trading partner via Stedi after warehouse dispatch

Steps

1. Trigger ASN generation from your WMS or shipping system when a shipment is confirmed — capture shipDate, carrierCode (e.g., 'UPS', 'FDXE'), trackingNumber, BOL number, and packed carton contents (quantity per SKU per carton/pallet).
2. Map the shipment data to the JEDI JSON structure for X12 856: BSN segment (shipmentIdentificationNumber, date, time, hierarchicalStructureCode), HL loops for shipment > order > item hierarchy, TD1 for carrier/pack details, TD5 for routing, and REF segments for PO and order references.
3. POST the JEDI JSON to Stedi's translate endpoint with the 856 Guide ID to produce X12 EDI text; review the translated output for correct HL nesting (HL01 shipment, HL02 order, HL03 item parent-child references).
4. Send the translated 856 via the Stedi outbound API to the retailer's trading partner profile — many retailers require the ASN to be transmitted before or at the time of physical delivery.
5. Await and process the retailer's 997 Functional Acknowledgment — an accepted 997 does not mean the ASN was reconciled against the PO; monitor for any subsequent 824 Application Advice indicating content errors.
6. Store the BSN02 shipmentIdentificationNumber and the PO references in your order management system so the 810 invoice can cross-reference the same shipment.