--- title: "EDI 404 Rail Carrier Shipment Information | X12 | Stacksync" description: "EDI 404 is the X12 Rail Carrier Shipment Information, used when rail movement instructions are ready for carrier use." canonical: https://www.stacksync.com/edi/x12/404-rail-carrier-shipment-information last_modified: 2026-09-29 --- X12 transaction code # EDI 404 Rail Carrier Shipment Information (X12 404) > 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 404 is the X12 Rail Carrier Shipment Information transaction set, used when rail movement instructions are ready for carrier use. The shipper (consignor) or its agent sends the 404 to the railroad that will move the equipment, either directly or through a value-added network. Standard X12 Code 404 Partner references 8 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) At a glance ## EDI 404 at a glance What the 404 carries, who sends it to whom, when it goes out, and the segments trading partners list for it. **X12 404 Rail Carrier Shipment Information summary** | | | | --- | --- | | Document | X12 404 Rail Carrier Shipment Information | | Business record | Rail shipment | | Who sends it to whom | The shipper (consignor) or its agent sends the 404 to the railroad that will move the equipment, either directly or through a value-added network. | | When it is sent | A shipper finishes loading a railcar or intermodal unit and releases the equipment to the railroad for movement. | | Match on | Rail shipment reference, equipment and route | | Partner references | 8 trading partners in this directory | | Related documents | [X12 417 Rail Carrier Waybill Interchange](https://www.stacksync.com/edi/x12/417-rail-carrier-waybill-interchange), [X12 410 Rail Carrier Freight Details and Invoice](https://www.stacksync.com/edi/x12/410-rail-carrier-freight-details-and-invoice) | ### Key segments in an EDI 404 The business segments that appear in at least half of the 8 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 | | --- | --- | --- | --- | | BX | General Shipment Information | To transmit identification numbers and other basic shipment data. | 8 of 8 | | BNX | Rail Shipment Information | To transmit rail-specific shipment data. | 8 of 8 | | M3 | Release | To indicate that the equipment is or is not to be released. | 8 of 8 | | N9 | Reference Identification | To transmit identifying information as specified by the Reference Identification Qualifier. | 8 of 8 | | N7 | Equipment Details | To identify the equipment. | 8 of 8 | | F9 | Origin Station | To identify the rail origin of the shipment. | 8 of 8 | | D9 | Destination Station | To identify the rail destination of the shipment. | 8 of 8 | | N1 | Name | To identify a party by type of organization, name, and code. | 8 of 8 | | N3 | Address Information | To specify the location of the named party. | 8 of 8 | | N4 | Geographic Location | To specify the geographic place of the named party. | 8 of 8 | Stacksync connects EDI documents such as the X12 404 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 404 mapping and validation X12 404 Rail Carrier Shipment Information is used when rail movement instructions are ready for carrier use. Preserve rail shipment reference, equipment and route so the rail shipment 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 | **rail shipment** rail shipment reference, equipment and route | Define which combination of rail shipment reference, equipment and route identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the rail shipment** ID assigned by the receiving system and processing result | Test a route involving more than one carrier and retain interchange details. Separate repeated equipment numbers across different shipment dates. | | Check the processing result | **Processing status for the rail shipment** Original document reference and matching response | Reconcile the rail shipment 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 417 Rail Carrier Waybill Interchange](https://www.stacksync.com/edi/x12/417-rail-carrier-waybill-interchange) **rail waybill interchange:** rail shipment information passes between carriers. - [X12 410 Rail Carrier Freight Details and Invoice](https://www.stacksync.com/edi/x12/410-rail-carrier-freight-details-and-invoice) **rail-freight payable:** rail transport charges are ready to reconcile. ### Implementation steps 1. #### Choose the starting event and owner Decide which application acts when rail movement instructions are ready for carrier use. Name the operational owner of the rail shipment and the team that resolves rejected or ambiguous messages. 2. #### Keep record IDs connected Map rail shipment reference, equipment and route. 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 rail shipment 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 rail shipment processing. Give unresolved errors an owner and check the receiving system before approving retries. ### Go-live checklist - An approved 404 sample and the agreed version and partner guide are available. - The mapping tests pass with realistic rail shipment 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 rail shipment without processing it twice. ### Related documents and resources - [X12 417 Rail Carrier Waybill Interchange](https://www.stacksync.com/edi/x12/417-rail-carrier-waybill-interchange) - [X12 410 Rail Carrier Freight Details and Invoice](https://www.stacksync.com/edi/x12/410-rail-carrier-freight-details-and-invoice) - [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 404 Rail Carrier Shipment Information at the element level The X12 404 reference contains 117 segment entries and 755 data elements; 124 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields. Segments 117 Data elements 755 Mandatory elements 124 **Segments with elements marked mandatory in this reference** | Segment | Elements | Mandatory | | --- | --- | --- | | ZC1 | 9 | 6 | | BX | 12 | 3 | | M3 | 4 | 1 | | N9 | 6 | 1 | | M1 | 12 | 1 | | DTM | 4 | 1 | | N7 | 19 | 1 | | VC | 8 | 1 | | N1 | 4 | 1 | | N3 | 2 | 1 | | M7 | 4 | 1 | | IC | 9 | 2 | Key identifiers in 404 - Equipment Number - Transaction Reference Number - Transaction Reference Date - Correction Indicator Code - Standard Carrier Alpha Code - Transportation Method/Type Code - Transaction Set Purpose Code - Shipment Method of Payment Code ## Find your trading partner for X12 404 8 partners, 8 channels. Choose a channel to inspect its listed document reference and implementation context. - [Burlington Northern Santa Fe Railway (BNSF)](https://www.stacksync.com/edi/burlington-northern-and-santa-fe-railway-co) [Burlington Northern Santa Fe Railway (BNSF)](https://www.stacksync.com/edi/burlington-northern-and-santa-fe-railway-co/burlington-northern-santa-fe-railway-bnsf/x12-404-rail-carrier-shipment-information) - [Canadian National Railway](https://www.stacksync.com/edi/canadian-national-railway) [Canadian National Railway](https://www.stacksync.com/edi/canadian-national-railway/canadian-national-railway/x12-404-rail-carrier-shipment-information) - [Canadian Pacific Railway](https://www.stacksync.com/edi/canadian-pacific-railway) [Canadian Pacific Railway](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway/x12-404-rail-carrier-shipment-information) - [COFC](https://www.stacksync.com/edi/cofc) [COFC](https://www.stacksync.com/edi/cofc/cofc/x12-404-rail-carrier-shipment-information) - [CPKC (formerly Kansas City Southern)](https://www.stacksync.com/edi/kansas-city-southern) [Kansas City Southern](https://www.stacksync.com/edi/kansas-city-southern/kansas-city-southern/x12-404-rail-carrier-shipment-information) - [CSX Transportation](https://www.stacksync.com/edi/csx-transportation) [CSX Transportation](https://www.stacksync.com/edi/csx-transportation/csx-transportation/x12-404-rail-carrier-shipment-information) - [Norfolk Southern](https://www.stacksync.com/edi/norfolk-southern) [Norfolk Southern](https://www.stacksync.com/edi/norfolk-southern/norfolk-southern/x12-404-rail-carrier-shipment-information) - [Union Pacific Railroad](https://www.stacksync.com/edi/union-pacific-railroad) [Union Pacific Railroad](https://www.stacksync.com/edi/union-pacific-railroad/union-pacific-railroad/x12-404-rail-carrier-shipment-information) Catalog breakdown ## Where X12 404 Rail Carrier Shipment Information appears in this catalog The largest groups of classified 404 catalog entries are in logistics & transport. ### By industry - logistics & transport 8 channels Partner entries with the most listed channels - [Burlington Northern Santa Fe Railway (BNSF)](https://www.stacksync.com/edi/burlington-northern-and-santa-fe-railway-co) - [Canadian National Railway](https://www.stacksync.com/edi/canadian-national-railway) - [Canadian Pacific Railway](https://www.stacksync.com/edi/canadian-pacific-railway) - [COFC](https://www.stacksync.com/edi/cofc) - [CPKC (formerly Kansas City Southern)](https://www.stacksync.com/edi/kansas-city-southern) - [CSX Transportation](https://www.stacksync.com/edi/csx-transportation) - [Norfolk Southern](https://www.stacksync.com/edi/norfolk-southern) - [Union Pacific Railroad](https://www.stacksync.com/edi/union-pacific-railroad) FAQ ## EDI 404 questions ### What is an EDI 404? EDI 404 is the X12 Rail Carrier Shipment Information transaction set. Trading partners use it when rail movement instructions are ready for carrier use. It carries the data for the rail shipment, and your system matches it on rail shipment reference, equipment and route. ### Who sends an EDI 404 and who receives it? The shipper (consignor) or its agent sends the 404 to the railroad that will move the equipment, either directly or through a value-added network. Your trading partner agreement confirms the direction and version for your account. ### When is an EDI 404 sent? A shipper finishes loading a railcar or intermodal unit and releases the equipment to the railroad for movement. Your partner guide sets any deadline or schedule for the document. ### What are the key segments in an EDI 404? Across 8 partner document references listed here, the business segments that appear most often include BX (General Shipment Information), BNX (Rail Shipment Information), M3 (Release), N9 (Reference Identification), N7 (Equipment Details), F9 (Origin Station). Each partner guide sets which segments and elements your account must send. ### What is the difference between EDI 404 and EDI 417? The 404 carries the rail shipment and is used when rail movement instructions are ready for carrier use. The 417 carries the rail waybill interchange and is used when rail shipment information passes between carriers. ### What should I map for X12 404? Start with rail shipment reference, equipment and route and the target rail shipment. 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 404 error handling? Test a route involving more than one carrier and retain interchange details. Separate repeated equipment numbers across different shipment dates. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment. ### Which partners list X12 404? The directory on this page links 8 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)