Skip to content
EDI JCPenney JCPenney (eCom Catalog | Store Retail | TMS) (753) 753
X12 EDI

JCPenney X12 753 Request for Routing Instructions

X12 753 (Request for Routing Instructions) is the EDI transaction exchanged between JCPenney (JCPenney (eCom Catalog | Store Retail | TMS) (753)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.

Segments
14
Loops
2
X12 753
All partners ↗
Book a demo ← All JCPenney (eCom Catalog | Store Retail | TMS) (753) transactions

Transaction context

Where 753 Request for Routing Instructions fits on JCPenney (eCom Catalog | Store Retail | TMS) (753)

JCPenney channels
1 of 20

1 of JCPenney's 20 channels carries 753

Trading partners
4

partners across the Stacksync network trade 753

Channels
5

channels network-wide carry 753

Most common alongside 753

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.

When it fires: 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.

Common 753 rejection causes
  • Routing requests whose items do not correlate to an open EDI 850 purchase order are rejected by the retailer's routing system.
  • Weight, carton, or order details on the 753 that do not align with the later 754 and EDI 856 ASN; retailers require these documents to match and penalize discrepancies with chargebacks.
  • Missing the retailer's submission lead time; the routing cycle can run as little as 24 hours before shipment, and late or non-compliant requests drive chargebacks and lowered vendor scorecards.

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
Full segment guideline — 14 segments 2 loops · X12 753 Request for Routing Instructions
ISA Interchange Control Header 16 elements

To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header 8 elements

To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header 2 elements

To indicate the start of a transaction set and to assign a control number

BGN Beginning Segment 4 elements

To indicate the beginning of a transaction set

PER Administrative Communications Contact 8 elements

To identify a person or office to whom administrative communications should be directed

N1 Loop Repeat: 1
N1 Name 4 elements

To identify a party by type of organization, name, and code

N3 Address Information 2 elements

To specify the location of the named party

N4 Geographic Location 4 elements

To specify the geographic place of the named party

LX Assigned Number 1 element

To reference a line number in a transaction set

L11 Business Instructions and Reference Number 2 elements

To specify instructions in this business relationship or a reference number

G62 Date/Time 4 elements

To specify pertinent dates and times

OID Loop
OID Order Identification Detail 9 elements

To specify order identification detail

SE Transaction Set Trailer 2 elements

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

CMC Commodity Classification 1 element

To specify freight commodity code and freight classification

JCPenney JCPenney (eCom Catalog | Store Retail | TMS) (753) EDI 753 FAQ

Common questions about 753 Request for Routing Instructions on the JCPenney (eCom Catalog | Store Retail | TMS) (753) channel.

What is X12 753 Request for Routing Instructions?
X12 753 (Request for Routing Instructions) is the EDI transaction set used to exchange request for routing instructions data. JCPenney's JCPenney (eCom Catalog | Store Retail | TMS) (753) channel requires it from trading partners.
Does JCPenney JCPenney (eCom Catalog | Store Retail | TMS) (753) require 753 for trading partners?
Yes, JCPenney (JCPenney (eCom Catalog | Store Retail | TMS) (753)) supports X12 753 Request for Routing Instructions. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate JCPenney 753 with Stacksync?
Most companies go live with JCPenney 753 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.

Ready to automate your JCPenney EDI?

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

Book a JCPenney EDI demo Tour the platform on your own