Logistics Service Response
A logistics service provider sends this transaction to confirm the status and details of services requested by a shipper or freight forwarder. It responds to a Logistics Service Request (219) by detailing how the requested logistics activities will be or have been performed. The response structure uses the B9 (Beginning Segment for Logistics Services) segment to establish the service scope, the B9A (Service Request) segment to specify which services are being addressed, and the L11 (Business Instructions and Reference Number) segment to link the response back to the original request through reference numbers and tracking identifiers.
For example, when FreshCargo Logistics receives a request from TechShip Inc. to arrange pickup and consolidation of components from three supplier locations, FreshCargo sends a 220 transaction confirming acceptance of the logistics plan. The response includes stop-off details in the S5 loop for each pickup location with associated dates, container and tracking information in the LX loop to identify which shipments are assigned to which consolidation points, and line-item details in the LAD loop showing individual line items from each supplier location along with their handling requirements and charges. This allows TechShip Inc. to verify that FreshCargo has understood the complete multi-stop consolidation requirement before execution begins.
Logistics Service Response (AH220) contains 2 tables (Heading, Detail), 6 loops, and 39 segments. Sign up free or login to view every table, loop, and element in full, as well as download it in Markdown or console (text) formats.
Sign up free to see the full AH220 reference
See every segment, loop, and element across all 2 tables. Download it as a diagram or Markdown, or use the tedi CLI to access the full X12 reference from your terminal.