Skip to content
EDI X12 753

X12 transaction code

X12 753 Request For Routing Instructions

Stop Mapping. Start Trading.

Standard
X12
Code
753
Trading partners
4

Specification summary

X12 753 Request For Routing Instructions at the element level

The X12 753 specification defines 20 segments carrying 70 data elements, 37 of which are mandatory.

Segments
20
Data elements
70
Mandatory elements
37
Segments with mandatory elements
Segment Elements Mandatory
BGN 5 3
PER 4 1
N1 4 1
N2 2 1
N3 2 1
LX 1 1
USI 3 2
Key identifiers in 753
  • Transaction Set Purpose Code
  • Reference Identification
  • Date
  • Contact Function Code
  • Entity Identifier Code
  • Name
  • Address Information
  • Assigned Number

Usage breakdown

Who trades X12 753 Request For Routing Instructions

753 is used most heavily in retail, e-commerce & marketplaces and apparel & footwear.

The X12 753 is a supplier's request for routing instructions on orders where the buyer controls inbound transportation. The supplier reports what is ready to ship (cartons, weight, volume, ready date, order references) so the retailer's transportation team can assign a carrier and pickup. Retailers require it because it lets them consolidate inbound freight and move goods on their own carrier contracts instead of the supplier's. A supplier or vendor sends the 753 to the retailer or the buyer's transportation organization, which answers with an EDI 754 Routing Instructions. A supplier has an order picked and ready to ship on a collect or buyer-managed freight program and needs the retailer to assign the carrier before booking pickup.

By industry

  • retail 2 channels
  • e-commerce & marketplaces 2 channels
  • apparel & footwear 1 channel

FAQ

X12 753 questions

What is X12 753 Request For Routing Instructions?

X12 753 (Request For Routing Instructions) is an EDI transaction set defined by ANSI ASC X12 for exchanging request for routing instructions between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 4 Stacksync trading partners support this code across 5 channels.

Which trading partners use X12 753?

4 Stacksync partners accept X12 753: Amazon, Bealls Inc., JCPenney, NEXCOM (Navy Exchange Service Command). Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.

How do I integrate X12 753 with my ERP?

Stacksync handles the full X12 753 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.

Ready to automate your EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.