--- title: "EDI 754 Routing Instructions: X12 754 Guide | Stacksync" description: "EDI 754 is the X12 Routing Instructions, used when routing details are issued in response to a shipment need. See its key segments and mapping checks." canonical: https://www.stacksync.com/edi/x12/754-routing-instructions last_modified: 2026-09-29 --- X12 transaction code # EDI 754 Routing Instructions (X12 754) > 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 754 is the X12 Routing Instructions transaction set, used when routing details are issued in response to a shipment need. 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. Standard X12 Code 754 Partner references 5 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) At a glance ## EDI 754 at a glance What the 754 carries, who sends it to whom, when it goes out, and the segments trading partners list for it. **X12 754 Routing Instructions summary** | | | | --- | --- | | Document | X12 754 Routing Instructions | | Business record | Routing instruction | | Who sends it to whom | 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 is sent | The buyer's transportation team completes carrier assignment for a supplier's routing request and releases pickup instructions ahead of the scheduled ship window. | | Match on | Routing reference, order and shipment | | Partner references | 5 trading partners in this directory | | Related documents | [X12 753 Request for Routing Instructions](https://www.stacksync.com/edi/x12/753-request-for-routing-instructions), [X12 856 Ship Notice/Manifest](https://www.stacksync.com/edi/x12/856-ship-notice-manifest) | ### Key segments in an EDI 754 The business segments that appear in at least half of the 6 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. | 6 of 6 | | N1 | Party Identification | To identify a party by type of organization, name, and code. | 6 of 6 | | N3 | Party Location | To specify the location of the named party. | 6 of 6 | | N4 | Geographic Location | To specify the geographic place of the named party. | 6 of 6 | | LX | Transaction Set Line Number | To reference a line number in a transaction set. | 6 of 6 | | L11 | Business Instructions and Reference Number | To specify instructions in this business relationship or a reference number. | 6 of 6 | | G62 | Date/Time | To specify pertinent dates and times. | 6 of 6 | | OID | Order Information Detail | To specify order information detail. | 5 of 6 | | PER | Administrative Communications Contact | To identify a person or office to whom administrative communications should be directed. | 4 of 6 | | BLR | Transportation Carrier Identification | To transmit the identifying SCAC code and effective date and time for the data in the transaction set. | 4 of 6 | Stacksync connects EDI documents such as the X12 754 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 754 mapping and validation X12 754 Routing Instructions is used when routing details are issued in response to a shipment need. Preserve routing reference, order and shipment so the routing instruction 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 instruction** routing reference, order and shipment | Define which combination of routing reference, order and shipment identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the routing instruction** ID assigned by the receiving system and processing result | Match instructions to the correct open routing request. Test a carrier reassignment after warehouse planning and require the shipping record to be updated. | | Check the processing result | **Processing status for the routing instruction** Original document reference and matching response | Reconcile the routing instruction 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 753 Request for Routing Instructions](https://www.stacksync.com/edi/x12/753-request-for-routing-instructions) **routing request:** a supplier needs shipping instructions. - [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 routing details are issued in response to a shipment need. Name the operational owner of the routing instruction and the team that resolves rejected or ambiguous messages. 2. #### Keep record IDs connected Map routing reference, order and shipment. 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 instruction 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 instruction processing. Give unresolved errors an owner and check the receiving system before approving retries. ### Go-live checklist - An approved 754 sample and the agreed version and partner guide are available. - The mapping tests pass with realistic routing instruction 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 instruction without processing it twice. ### Related documents and resources - [X12 753 Request for Routing Instructions](https://www.stacksync.com/edi/x12/753-request-for-routing-instructions) - [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 754 Routing Instructions at the element level The X12 754 reference contains 23 segment entries and 64 data elements; 40 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields. Segments 23 Data elements 64 Mandatory elements 40 **Segments with elements marked mandatory in this reference** | 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 ## Find your trading partner for X12 754 5 partners, 6 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-754-routing-instructions) - [AT&T Inc.](https://www.stacksync.com/edi/att) [AT&T (Legacy ISA ID: 108024050NHP)](https://www.stacksync.com/edi/att/at-t-legacy-isa-id-108024050nhp/x12-754-routing-instructions) [AT&T (New ISA ID: 108024050B2B)](https://www.stacksync.com/edi/att/at-t-new-isa-id-108024050b2b/x12-754-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-754-routing-instructions) - [JCPenney](https://www.stacksync.com/edi/jcpenney) [JCPenney (eCom Catalog / Store Retail / TMS) (754)](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-store-retail-tms-754/x12-754-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-754-routing-instructions) Catalog breakdown ## Where X12 754 Routing Instructions appears in this catalog The largest groups of classified 754 catalog entries are in electronics & technology, retail and apparel & footwear. ### By industry - electronics & technology 2 channels - retail 2 channels - apparel & footwear 1 channel - e-commerce & marketplaces 1 channel Partner entries with the most listed channels - [AT&T Inc.](https://www.stacksync.com/edi/att) - [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 754 questions ### What is an EDI 754? EDI 754 is the X12 Routing Instructions transaction set. Trading partners use it when routing details are issued in response to a shipment need. It carries the data for the routing instruction, and your system matches it on routing reference, order and shipment. ### Who sends an EDI 754 and who receives it? 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. Your trading partner agreement confirms the direction and version for your account. ### When is an EDI 754 sent? The buyer's transportation team completes carrier assignment for a supplier's routing request and releases pickup instructions ahead of the scheduled ship window. Your partner guide sets any deadline or schedule for the document. ### What are the key segments in an EDI 754? Across 6 partner document references listed here, the business segments that appear most often include BGN (Beginning Segment), N1 (Party Identification), N3 (Party Location), N4 (Geographic Location), LX (Transaction Set Line Number), L11 (Business Instructions and Reference Number). Each partner guide sets which segments and elements your account must send. ### What is the difference between EDI 754 and EDI 753? The 754 carries the routing instruction and is used when routing details are issued in response to a shipment need. The 753 carries the routing request and is used when a supplier needs shipping instructions. ### What should I map for X12 754? Start with routing reference, order and shipment and the target routing instruction. 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 754 error handling? Match instructions to the correct open routing request. Test a carrier reassignment after warehouse planning and require the shipping record to be updated. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment. ### Which partners list X12 754? The directory on this page links 5 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)