EDI 753 and 754: Routing Request and Routing Instructions
An EDI 753 is the supplier's request for routing instructions. An EDI 754 is the buyer's reply, naming the carrier and pickup. Both sit between the 850 and 855 and the 856 ship notice. We build both inside your ERP for Amazon Vendor Central Wholesale, read and generated with the EdiFabric .NET library.
+ RULES
What the 753 and 754 do, and where they fit
-
850Purchase order. The buyer orders. On Amazon Vendor Central Wholesale, Amazon orders stock it will own. -
855Acknowledgment. The supplier confirms what it can actually ship, with quantities and dates. -
753Request for routing instructions. Used when the buyer arranges the freight. The supplier tells the buyer what is ready to move: the purchase orders, cartons or pallets, weight and where it ships from. -
754Routing instructions. The buyer replies naming the carrier and the pickup. On a collect shipment the goods do not move until this arrives. -
856Advance ship notice. Sent once the goods ship. It has to describe the same shipment that was routed. -
810Invoice. Bills for what shipped, matched line for line against the ship notice.
Key data in a 753 routing request
A 753 is a description of freight that is ready to move. In plain terms it answers three questions: what is shipping, from where, and when it can be picked up. The segments below are the ones that usually carry that information.
-
BGNBeginning segment. Identifies the request: its purpose, a reference number and the date it was created. -
N1Parties and locations. Who is shipping and where from, plus the destination, with address details in the segments that follow. -
G62Dates. When the freight is ready to be picked up. -
OIDOrder detail. One entry per purchase order: the PO number, the count of cartons or pallets, the weight and the volume.
Key data in a 754 routing instructions reply
A 754 is the buyer's answer. It tells the supplier how the freight will move and when it will be collected. Which segments are required, and how each field is filled, is set by the buyer's implementation guide, not by the X12 standard alone, so check the current guide for your own program.
-
BGNBeginning segment. Identifies the instructions and ties them back to the request. -
TD5Carrier and routing. The carrier the buyer has assigned, and how the freight is routed. -
G62Pickup date and time. When the carrier will collect, the appointment the warehouse has to be ready for. -
OIDOrder detail. Which purchase orders and quantities the instructions cover.
How we build 753 and 754 inside your ERP
Generated from the shipment record
The 753 is built from the cartons, pallets, weights and ship-from location your ERP already holds for the shipment. Nobody retypes them into a portal.
Appointment data kept with the order
The carrier and pickup details from the 754 are stored against the purchase order, so the warehouse and the ship notice work from the same appointment.
Every file logged
Each 753 and 754 is read and generated inside your ERP using the EdiFabric .NET library, and the raw file is stored next to the parsed result. A rejection is traced to the exact value that caused it.
Tied to the 856
The 856 goes after the 754 arrives, and it has to describe the shipment that was actually routed: the same purchase orders, cartons and carrier.
753 and 754 in a live Amazon Vendor Central connection
- Amazon Vendor Central Wholesale EDI including 753 routing requests and 754 routing instructions, alongside 850, 855, 856, 810, 846, 997, 824 and 812.
- Every X12 file read and generated inside the ERP using the EdiFabric .NET library, with the mapping in the ERP's own code.
- Amazon Vendor Central connected directly, with no network in between.
- A routing request was rejected because its delivery appointment slot did not match what the client had actually scheduled. The mismatch was diagnosed, the client corrected the slot, and the resend was accepted.
What goes wrong with 753 and 754 routing
- A routing request rejected on the appointment slot The delivery appointment time slot on the routing request did not match what the client had actually scheduled, so Amazon rejected it. Comparing the transaction against the scheduled appointment showed the mismatch. The client corrected the slot, and the resend was accepted.
- Carton or pallet counts on the 753 do not match the later 856 A common pattern. The routing request goes out with the planned pack, then the warehouse packs differently. The ship notice then disagrees with what was routed. Checking both documents against the actual pack, and checking the routing again when the pack changes before pickup, keeps them in line.
- The routing request goes out late A common pattern when the 753 is keyed in by hand after the goods are already packed. The shipment then sits waiting for its 754. Generating the request from the ERP as soon as the shipment is planned removes that wait. Check your own program for the timing it expects.
- Ship-from or freight details do not match the purchase order A common pattern. The 753 carries a ship-from location or freight detail that differs from the order, for example a different warehouse. Pickup is then planned against the wrong details. Comparing the 753 with the 850 and the warehouse record shows which side is wrong.
EDI 753 and 754 questions
What is EDI 753?
The X12 Request for Routing Instructions. The supplier sends it to the buyer when the buyer arranges the freight. It describes what is ready to ship: the purchase orders, cartons or pallets, weight and ship-from location.
What is EDI 754?
The X12 Routing Instructions. It is the buyer's reply to a 753, naming the carrier and the pickup details for the shipment.
Is 753 and 754 needed for Amazon Direct Fulfillment?
The 753 and 754 are used with Wholesale shipments, where Amazon arranges the freight. Direct Fulfillment ships orders to individual customers and runs as a separate program. Check what your own program requires.
What happens if a routing request is rejected?
The shipment cannot be routed until the request is fixed. The rejection points at the value that did not match, often an appointment slot, a count or a location. Correct it at the source, then resend. In the case above, the appointment slot was corrected and the resend was accepted.
How do the 753 and 754 relate to the 856?
The 754 comes first. The 856 goes after it and should describe the same shipment: the same purchase orders, cartons and carrier that were routed. Checking each document against the actual shipment keeps them consistent.
Can this be built into an ERP we did not build?
Often yes. What matters is whether your order, shipment and warehouse data is reachable, not who wrote the ERP. We confirm that during scoping.
Who owns the mapping code?
You do. It sits in your ERP codebase.
Related to EDI 753 and 754
Are routing requests still being keyed into a portal by hand?
Tell us how your 753s go out today and what the last rejection said. We will tell you where the routing data should come from in your own system.