Skip to content
X12 EDI

JCPenney X12 754 Routing Instructions

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

Segments
16
Loops
3
X12 754
All partners ↗

Transaction context

Where 754 Routing Instructions fits on JCPenney (eCom Catalog / Store Retail / TMS) (754)

JCPenney channels
1 of 20

1 of JCPenney's 20 channels carries 754

Trading partners
5

partners across the Stacksync network trade 754

Channels
6

channels network-wide carry 754

The X12 754 carries the buyer's routing decision for a pending shipment: the assigned carrier and transportation method (TD5), pickup and delivery dates (G62), destination details, and party contacts. It normally answers a supplier's EDI 753 request and is binding; suppliers on buyer-managed freight programs must ship exactly as instructed. Retailers use it to enforce their inbound routing guides and control transportation spend. The retailer or the buyer's transportation organization sends the 754 to the supplier that requested routing, naming the carrier and pickup window for the shipment.

When it fires: The buyer's transportation team completes carrier assignment for a supplier's routing request and releases pickup instructions ahead of the scheduled ship window.

Common 754 rejection causes
  • Supplier non-compliance with the specified instructions, such as shipping before the 754 arrives or using a carrier other than the one assigned, which triggers compliance chargebacks.
  • Acting on superseded instructions; buyers issue updates and instructions become outdated, so shipments routed against an earlier 754 are misrouted.
  • Shipment details on the subsequent EDI 856 ASN that do not align with the 753 and 754, which retailers flag and penalize.

Specification summary

X12 754 Routing Instructions at the element level

The X12 754 specification defines 23 segments carrying 64 data elements, 40 of which are mandatory.

Segments
23
Data elements
64
Mandatory elements
40
Segments with mandatory elements
Segment Elements Mandatory
BGN 4 3
N1 2 1
N2 1 1
N3 1 1
LX 1 1
BLR 1 1
SMD 2 2
MSI 2 1
Key identifiers in 754
  • Transaction Set Purpose Code
  • Reference Identification
  • Date
  • Entity Identifier Code
  • Name
  • Address Information
  • Assigned Number
  • Standard Carrier Alpha Code
Full segment guideline — 16 segments 3 loops · X12 754 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 5 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: 5
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 Loop Repeat: 9,999
LX Assigned Number 1 element

To reference a line number in a transaction set

L11 Business Instructions and Reference Number 3 elements

To specify instructions in this business relationship or a reference number

BLR Transportation Carrier Identification 1 element

To transmit the identifying SCAC code and effective date and time for the data in the transaction set

OID Order Identification Detail 2 elements

To specify order identification detail

G62 Date/Time 4 elements

To specify pertinent dates and times

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)

MSI Multi-stop Shipment Information 2 elements

To specify multi-stop shipment information

QTY Loop Repeat: 25
QTY Quantity 2 elements

To specify quantity information

JCPenney JCPenney (eCom Catalog / Store Retail / TMS) (754) EDI 754 FAQ

Common questions about 754 Routing Instructions on the JCPenney (eCom Catalog / Store Retail / TMS) (754) channel.

What is X12 754 Routing Instructions?
X12 754 (Routing Instructions) is the EDI transaction set used to exchange routing instructions data. JCPenney's JCPenney (eCom Catalog / Store Retail / TMS) (754) channel requires it from trading partners.
Does JCPenney JCPenney (eCom Catalog / Store Retail / TMS) (754) require 754 for trading partners?
Yes, JCPenney (JCPenney (eCom Catalog / Store Retail / TMS) (754)) supports X12 754 Routing Instructions. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate JCPenney 754 with Stacksync?
Most companies go live with JCPenney 754 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.