To start and identify an interchange of zero or more functional groups and interchange-related control segments
AT&T Inc. X12 754 Routing Instructions
X12 754 (Routing Instructions) is the EDI transaction exchanged between AT&T Inc. (AT&T (New ISA ID: 108024050B2B)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 16
- Loops
- 2
- X12 754
- All partners ↗
Transaction context
Where 754 Routing Instructions fits on AT&T (New ISA ID: 108024050B2B)
- AT&T Inc. channels
- 2 of 2
- Trading partners
- 5
- Channels
- 6
2 of AT&T Inc.'s 2 channels carry 754
partners across the Stacksync network trade 754
channels network-wide carry 754
Most common alongside 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
| 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 2 loops · X12 754 Routing Instructions
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To indicate the beginning of a transaction set
N1 Loop Repeat: 5
To identify a party by type of organization, name, and code
To specify additional names
To specify the location of the named party
To specify the geographic place of the named party
LX Loop Repeat: 9,999
To reference a line number in a transaction set
To specify instructions in this business relationship or a reference number
To transmit the identifying SCAC code and effective date and time for the data in the transaction set
To transmit shipment manifest data
To specify order information detail
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To specify pertinent dates and times
To specify multi-stop shipment information
Trading partners
1+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
No trading partner matches your search.
Browse the full directory
Trading partners
6+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
PU Purchase Order PU Purchase Order Acknowledgment SH Ship Notice Manifest IN Invoice AP Application Advice WA Warehouse Shipping Order
No trading partner matches your search.
Browse the full directory
AT&T Inc. AT&T (New ISA ID: 108024050B2B) EDI 754 FAQ
Common questions about 754 Routing Instructions on the AT&T (New ISA ID: 108024050B2B) channel.
What is X12 754 Routing Instructions?
X12 754 (Routing Instructions) is the EDI transaction set used to exchange routing instructions data. AT&T Inc.'s AT&T (New ISA ID: 108024050B2B) channel requires it from trading partners.
Does AT&T Inc. AT&T (New ISA ID: 108024050B2B) require 754 for trading partners?
Yes, AT&T Inc. (AT&T (New ISA ID: 108024050B2B)) supports X12 754 Routing Instructions. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate AT&T Inc. 754 with Stacksync?
Most companies go live with AT&T Inc. 754 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which other AT&T Inc. channels accept 754?
X12 754 runs on 2 of AT&T Inc.'s 2 channels. Besides AT&T (New ISA ID: 108024050B2B), it is accepted on AT&T (Legacy ISA ID: 108024050NHP). Each channel carries its own implementation guideline; Stacksync validates outbound documents against the correct guideline automatically.
Ready to automate your AT&T Inc. EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
