--- title: "EDI 753 Request for Routing Instructions | X12 | Stacksync" description: "EDI 753 is the X12 Request for Routing Instructions, used when a supplier needs shipping instructions. See key segments (BGN, PER, N1) and mapping checks." canonical: https://www.stacksync.com/edi/x12/753-request-for-routing-instructions last_modified: 2026-09-29 --- X12 transaction code # EDI 753 Request for Routing Instructions (X12 753) > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md EDI 753 is the X12 Request for Routing Instructions transaction set, used when a supplier needs shipping instructions. A supplier or vendor sends the 753 to the retailer or the buyer's transportation organization, which answers with an EDI 754 Routing Instructions. Standard X12 Code 753 Partner references 4 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) At a glance ## EDI 753 at a glance What the 753 carries, who sends it to whom, when it goes out, and the segments trading partners list for it. **X12 753 Request for Routing Instructions summary** | | | | --- | --- | | Document | X12 753 Request for Routing Instructions | | Business record | Routing request | | Who sends it to whom | 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 is sent | 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. | | Match on | Routing request, purchase order and ready-to-ship date | | Partner references | 4 trading partners in this directory | | Related documents | [X12 754 Routing Instructions](https://www.stacksync.com/edi/x12/754-routing-instructions), [X12 850 Purchase Order](https://www.stacksync.com/edi/x12/850-purchase-order), [X12 856 Ship Notice/Manifest](https://www.stacksync.com/edi/x12/856-ship-notice-manifest) | ### Key segments in an EDI 753 The business segments that appear in at least half of the 5 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send. | Segment | Name | Purpose | Partner references | | --- | --- | --- | --- | | BGN | Beginning Segment | To indicate the beginning of a transaction set. | 5 of 5 | | PER | Administrative Communications Contact | To identify a person or office to whom administrative communications should be directed. | 5 of 5 | | N1 | Party Identification | To identify a party by type of organization, name, and code. | 5 of 5 | | LX | Transaction Set Line Number | To reference a line number in a transaction set. | 5 of 5 | | G62 | Date/Time | To specify pertinent dates and times. | 5 of 5 | | OID | Order Information Detail | To specify order information detail. | 5 of 5 | | N3 | Party Location | To specify the location of the named party. | 4 of 5 | | N4 | Geographic Location | To specify the geographic place of the named party. | 4 of 5 | | L11 | Business Instructions and Reference Number | To specify instructions in this business relationship or a reference number. | 4 of 5 | | USI | Unitized Shipment Information | To specify the quantity, number of pallet spaces and stackability of unitized units. | 3 of 5 | Stacksync connects EDI documents such as the X12 753 to your ERP, CRM and databases with two-way sync. Read the [EDI overview](https://www.stacksync.com/edi), check [pricing](https://www.stacksync.com/pricing) and [security](https://www.stacksync.com/security), or [book a demo](https://www.stacksync.com/book-a-demo) to walk through your partner guide. Implementation guide ## X12 753 mapping and validation X12 753 Request for Routing Instructions is used when a supplier needs shipping instructions. Preserve routing request, purchase order and ready-to-ship date so the routing request in your business system stays connected to the original document. Use the version and implementation guide agreed with your trading partner to confirm required fields and responses. **Map records and test the business result** | Document or decision | Record and matching IDs | What to test | | --- | --- | --- | | Match the business record | **routing request** routing request, purchase order and ready-to-ship date | Define which combination of routing request, purchase order and ready-to-ship date identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the routing request** ID assigned by the receiving system and processing result | Test an order split into two pickups and keep each routing request distinct. Handle a changed ready date while the original routing request is still open. | | Check the processing result | **Processing status for the routing request** Original document reference and matching response | Reconcile the routing request with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document. | ### How the related documents differ Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately. - [X12 754 Routing Instructions](https://www.stacksync.com/edi/x12/754-routing-instructions) **routing instruction:** routing details are issued in response to a shipment need. - [X12 850 Purchase Order](https://www.stacksync.com/edi/x12/850-purchase-order) **purchase order or sales order:** a buyer places an order. - [X12 856 Ship Notice/Manifest](https://www.stacksync.com/edi/x12/856-ship-notice-manifest) **shipment notice (ASN):** an order ships, before the goods arrive. ### Implementation steps 1. #### Choose the starting event and owner Decide which application acts when a supplier needs shipping instructions. Name the operational owner of the routing request and the team that resolves rejected or ambiguous messages. 2. #### Keep record IDs connected Map routing request, purchase order and ready-to-ship date. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier. 3. #### Test failures before launch Run the failure cases in the mapping table against realistic routing request data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate. 4. #### Track every document to completion Record transport delivery and document validation separately from successful routing request processing. Give unresolved errors an owner and check the receiving system before approving retries. ### Go-live checklist - An approved 753 sample and the agreed version and partner guide are available. - The mapping tests pass with realistic routing request data. - Each submitted document can be traced through delivery, validation and processing in the receiving system. - Your team knows how to investigate and recover a rejected or timed-out routing request without processing it twice. ### Related documents and resources - [X12 754 Routing Instructions](https://www.stacksync.com/edi/x12/754-routing-instructions) - [X12 850 Purchase Order](https://www.stacksync.com/edi/x12/850-purchase-order) - [X12 856 Ship Notice/Manifest](https://www.stacksync.com/edi/x12/856-ship-notice-manifest) - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) **Sources.** Sources reviewed 2026-09-15. - [X12 transaction-set directory](https://x12.org/products/transaction-sets) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) Document structure ## X12 753 Request for Routing Instructions at the element level The X12 753 reference contains 20 segment entries and 70 data elements; 37 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields. Segments 20 Data elements 70 Mandatory elements 37 **Segments with elements marked mandatory in this reference** | 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 ## Find your trading partner for X12 753 4 partners, 5 channels. Choose a channel to inspect its listed document reference and implementation context. - [Amazon](https://www.stacksync.com/edi/amazon) [Amazon Retail - Canada](https://www.stacksync.com/edi/amazon/amazon-retail-canada/x12-753-request-for-routing-instructions) [Amazon Retail - US](https://www.stacksync.com/edi/amazon/amazon-retail-us/x12-753-request-for-routing-instructions) - [Bealls Inc.](https://www.stacksync.com/edi/bealls-inc) [Bealls Inc (Temporary)](https://www.stacksync.com/edi/bealls-inc/bealls-inc-temporary/x12-753-request-for-routing-instructions) - [JCPenney](https://www.stacksync.com/edi/jcpenney) [JCPenney (eCom Catalog | Store Retail | TMS) (753)](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-store-retail-tms-753/x12-753-request-for-routing-instructions) - [NEXCOM (Navy Exchange Service Command)](https://www.stacksync.com/edi/nexcom-navy-exchange-service-command) [NEXCOM Trans](https://www.stacksync.com/edi/nexcom-navy-exchange-service-command/nexcom-trans/x12-753-request-for-routing-instructions) Catalog breakdown ## Where X12 753 Request for Routing Instructions appears in this catalog The largest groups of classified 753 catalog entries are in retail, e-commerce & marketplaces and apparel & footwear. ### By industry - retail 2 channels - e-commerce & marketplaces 2 channels - apparel & footwear 1 channel Partner entries with the most listed channels - [Amazon](https://www.stacksync.com/edi/amazon) - [Bealls Inc.](https://www.stacksync.com/edi/bealls-inc) - [JCPenney](https://www.stacksync.com/edi/jcpenney) - [NEXCOM (Navy Exchange Service Command)](https://www.stacksync.com/edi/nexcom-navy-exchange-service-command) FAQ ## EDI 753 questions ### What is an EDI 753? EDI 753 is the X12 Request for Routing Instructions transaction set. Trading partners use it when a supplier needs shipping instructions. It carries the data for the routing request, and your system matches it on routing request, purchase order and ready-to-ship date. ### Who sends an EDI 753 and who receives it? A supplier or vendor sends the 753 to the retailer or the buyer's transportation organization, which answers with an EDI 754 Routing Instructions. Your trading partner agreement confirms the direction and version for your account. ### When is an EDI 753 sent? 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. Your partner guide sets any deadline or schedule for the document. ### What are the key segments in an EDI 753? Across 5 partner document references listed here, the business segments that appear most often include BGN (Beginning Segment), PER (Administrative Communications Contact), N1 (Party Identification), LX (Transaction Set Line Number), G62 (Date/Time), OID (Order Information Detail). Each partner guide sets which segments and elements your account must send. ### What is the difference between EDI 753 and EDI 754? The 753 carries the routing request and is used when a supplier needs shipping instructions. The 754 carries the routing instruction and is used when routing details are issued in response to a shipment need. ### What should I map for X12 753? Start with routing request, purchase order and ready-to-ship date and the target routing request. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats. ### How should I test 753 error handling? Test an order split into two pickups and keep each routing request distinct. Handle a changed ready date while the original routing request is still open. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment. ### Which partners list X12 753? The directory on this page links 4 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires. ## Connect EDI to your business systems See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout. [Book an EDI demo](https://www.stacksync.com/book-a-demo) [Explore the EDI platform](https://www.stacksync.com/edi)