Receive the raw EDI 214 X12 file from your VAN, AS2 connection, or EDI platform (e.g., Stedi, SPS Commerce) and acknowledge receipt with a 997 Functional Acknowledgment.
Parse the ST/SE envelope to identify the transaction set (214); extract the ISA and GS segments to identify the sender SCAC and interchange date/time.
Locate the B10 segment for the shipment reference numbers (BOL number, PRO number, carrier reference) and the AT7 segment for the shipment status code and status reason code.
Map the AT7 status code (e.g., X6=In Transit, AG=Estimated Delivery, D1=Delivered) to your internal delivery state machine and update the corresponding shipment record.
Handle the AT8 segment for equipment details and MS1/MS2 segments for geographic location if present; store latitude/longitude or city-state for last-known-location display.
Known gotchas
Carriers implement the 214 spec inconsistently — some send AT7 with status date/time in local carrier timezone without a timezone qualifier; always record the raw value and convert to UTC using the origin or destination timezone as a fallback heuristic.
A single 214 transaction can contain multiple AT7/AT8/MS1 loop iterations for multiple status events in chronological order; parse all iterations rather than stopping at the first AT7.
Some carriers send 214s out of chronological order due to batch processing delays; compare the status date/time on each event against the current recorded status before overwriting to avoid rolling back to an earlier state.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp