To start and identify an interchange of zero or more functional groups and interchange-related control segments
Bealls Inc. X12 753 Request for Routing Instructions
X12 753 (Request for Routing Instructions) is the EDI transaction exchanged between Bealls Inc. (Bealls Inc (Temporary)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 12
- Loops
- 2
- X12 753
- All partners ↗
Transaction context
Where 753 Request for Routing Instructions fits on Bealls Inc (Temporary)
- Bealls Inc. channels
- 1 of 2
- Trading partners
- 4
- Channels
- 5
1 of Bealls Inc.'s 2 channels carries 753
partners across the Stacksync network trade 753
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
| 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 — 12 segments 2 loops · X12 753 Request for 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
To identify a person or office to whom administrative communications should be directed
N1 Loop Repeat: 1
To identify a party by type of organization, name, and code
To specify the location of the named party
To specify the geographic place of the named party
To reference a line number in a transaction set
To specify pertinent dates and times
OID Loop
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)
Trading partners
8+ 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.
RO Routing Instructions IN Invoice SH Ship Notice Manifest PU Purchase Order Acknowledgment PU Purchase Order Change Acknowledgment Request Seller Initiated PU Purchase Order Change Request Buyer Initiated PU Purchase Order IN Inventory Inquiry Advice
No trading partner matches your search.
Browse the full directory
Bealls Inc. Bealls Inc (Temporary) EDI 753 FAQ
Common questions about 753 Request for Routing Instructions on the Bealls Inc (Temporary) 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. Bealls Inc.'s Bealls Inc (Temporary) channel requires it from trading partners.
Does Bealls Inc. Bealls Inc (Temporary) require 753 for trading partners?
Yes, Bealls Inc. (Bealls Inc (Temporary)) supports X12 753 Request for Routing Instructions. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Bealls Inc. 753 with Stacksync?
Most companies go live with Bealls Inc. 753 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 753 on Bealls Inc (Temporary)?
On Bealls Inc (Temporary), X12 753 is typically exchanged alongside 850 Purchase Order, 855 Purchase Order Acknowledgment, 810 Invoice, 856 Ship Notice Manifest. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your Bealls Inc. EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
