Sent by suppliers to buyers or retailers before shipment to request approved carrier routing - preventing chargebacks and ensuring compliance with retail routing guides.
The EDI 753 is a pre-shipment document that a supplier sends to a buyer (typically a retailer or large distributor) to ask: "I'm ready to ship - which carrier and routing method do you want me to use?" Rather than making their own carrier selection, the supplier waits for the buyer's explicit approval before booking freight. This is critical in retail supply chains where buyers have negotiated carrier contracts, routing guides, and preferred freight programs.
A 753 contains details about what's being shipped - purchase order references, item quantities, weight, cube, hazmat flags - along with the origin location and desired ship date. The buyer's transportation management system or logistics team processes this and responds with a 754 Routing Instructions that specifies the exact SCAC code (Standard Carrier Alpha Code), PRO number if pre-assigned, and any special handling requirements.
Without a proper 753/754 exchange, suppliers often default to using their own preferred carriers, which violates routing compliance requirements and triggers chargebacks. Many major retailers - including Target, Walmart, and Home Depot - require 753 for collect shipments above threshold weights or order values.
Vendors shipping to major retailers (Walmart, Target, Costco, Home Depot) use 753 to comply with routing guides for collect shipments. Skipping this step can result in routing chargebacks of $250–$1,500 per shipment. The 753 creates an auditable record of routing compliance.
Consumer packaged goods suppliers sending to grocery DCs (Kroger, Albertsons, UNFI) submit 753s before palletized LTL or truckload shipments. Grocery DCs are particularly strict about carrier compliance since they manage tightly scheduled inbound dock appointments.
High-value electronics suppliers use 753 to get routing approvals for shipments to Best Buy, Amazon FCs, or specialty retailers. The buyer often mandates specific carriers with insurance requirements, which the 753/754 exchange formalizes.
Apparel vendors fulfilling seasonal purchase orders from department stores or specialty chains use 753 to coordinate inbound freight routing. Timing is critical in apparel, and the 753 helps ensure goods arrive in the correct ship window without triggering late-shipment penalties.
Opens the 753 transaction. Contains the transaction set purpose code (00 = original, 05 = replace), a unique shipment ID assigned by the supplier, and the transaction date. The shipment ID in BSN01/BSN02 becomes the cross-reference key when matching against the 754 response.
Carries the purchase order number (REF01 = PO, REF02 = PO number), bill of lading number, or other document references. A single 753 can reference multiple POs via repeating REF segments. Common qualifier: PO for purchase order, BM for bill of lading.
Identifies the ship-from location (N101 = SF) and ship-to destination (N101 = ST). Includes street address, city, state, and ZIP. Accurate address data here directly affects which carrier routing is assigned in the 754 response - wrong addresses cause routing errors.
Describes the commodity being shipped: packaging code (e.g., CTN for cartons, PLT for pallets), number of packages, weight qualifier, and gross weight in pounds. TD1 also carries the lading description. This segment is what triggers the buyer's TMS to select the appropriate carrier and service level.
Optional but commonly used to indicate a preferred routing or carrier SCAC the supplier already has. TD501 = routing sequence code, TD502 = SCAC code (e.g., FXFE for FedEx Freight, UPGF for UPS Freight). The buyer may override this in the 754 response.
Specifies the ready-to-ship date (DTM01 = 037 = Ship Not Before) and must-ship-by date (DTM01 = 038 = Ship Not After). These dates allow the buyer's routing team to schedule inbound appointments and assign a ship window that aligns with DC receiving capacity.
The direct response to a 753. The buyer sends back the approved carrier SCAC, any pre-assigned PRO number, and specific delivery instructions. The 754 must be received and its routing followed before booking freight.
The original purchase order that triggered the need for routing instructions. PO numbers from the 850 are referenced in the 753 REF segment so the buyer can match the routing request back to their open orders.
Sent after routing instructions are received and the shipment is booked. The ASN references the carrier and PRO number assigned in the 754, completing the pre-shipment routing compliance loop.
Better EDI handles 753 mapping, testing, and trading partner certification so you don't have to.
Talk to an EDI Expert