--- title: "EDI 104 Air Shipment Information: X12 104 Guide | Stacksync" description: "EDI 104 is the X12 Air Shipment Information, used when air-freight booking is ready for carrier processing. See mapping checks." canonical: https://www.stacksync.com/edi/x12/104-air-shipment-information last_modified: 2026-09-29 --- X12 transaction code # EDI 104 Air Shipment Information (X12 104) > 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 104 is the X12 Air Shipment Information transaction set, used when air-freight booking is ready for carrier processing. The shipper or freight forwarder sends the 104 to the air carrier that will move the freight. Standard X12 Code 104 Partner references 1 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) At a glance ## EDI 104 at a glance What the 104 carries, who sends it to whom, when it goes out. **X12 104 Air Shipment Information summary** | | | | --- | --- | | Document | X12 104 Air Shipment Information | | Business record | Air shipment | | Who sends it to whom | The shipper or freight forwarder sends the 104 to the air carrier that will move the freight. | | When it is sent | A shipper tenders freight to an air carrier and transmits the airbill and rating detail for that shipment electronically. | | Match on | Air waybill, shipment reference and piece identifiers | | Partner references | 1 trading partner in this directory | | Related documents | [X12 110 Air Freight Details and Invoice](https://www.stacksync.com/edi/x12/110-air-freight-details-and-invoice) | Stacksync connects EDI documents such as the X12 104 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 104 mapping and validation X12 104 Air Shipment Information is used when air-freight booking is ready for carrier processing. Preserve air waybill, shipment reference and piece identifiers so the air 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 | **air shipment** air waybill, shipment reference and piece identifiers | Define which combination of air waybill, shipment reference and piece identifiers identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the air shipment** ID assigned by the receiving system and processing result | Split a shipment across pieces and reconcile their weight with the shipment total. Send an unknown consignee and hold it for address resolution before dispatch. | | Check the processing result | **Processing status for the air shipment** Original document reference and matching response | Reconcile the air 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 110 Air Freight Details and Invoice](https://www.stacksync.com/edi/x12/110-air-freight-details-and-invoice) **air-freight payable:** carrier billing is ready to reconcile. ### Implementation steps 1. #### Choose the starting event and owner Decide which application acts when air-freight booking is ready for carrier processing. Name the operational owner of the air shipment and the team that resolves rejected or ambiguous messages. 2. #### Keep record IDs connected Map air waybill, shipment reference and piece identifiers. 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 air 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 air shipment processing. Give unresolved errors an owner and check the receiving system before approving retries. ### Go-live checklist - An approved 104 sample and the agreed version and partner guide are available. - The mapping tests pass with realistic air 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 air shipment without processing it twice. ### Related documents and resources - [X12 110 Air Freight Details and Invoice](https://www.stacksync.com/edi/x12/110-air-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/) ## Find your trading partner for X12 104 1 partner, 1 channel. Choose a channel to inspect its listed document reference and implementation context. - [Wiz](https://www.stacksync.com/edi/wiz) [Wiz gmail](https://www.stacksync.com/edi/wiz/wiz-gmail/x12-104-air-shipment-information) Catalog breakdown ## Where X12 104 Air Shipment Information appears in this catalog The largest groups of classified 104 catalog entries are in other industries. ### By industry - other industries 1 channel Partner entries with the most listed channels - [Wiz](https://www.stacksync.com/edi/wiz) FAQ ## EDI 104 questions ### What is an EDI 104? EDI 104 is the X12 Air Shipment Information transaction set. Trading partners use it when air-freight booking is ready for carrier processing. It carries the data for the air shipment, and your system matches it on air waybill, shipment reference and piece identifiers. ### Who sends an EDI 104 and who receives it? The shipper or freight forwarder sends the 104 to the air carrier that will move the freight. Your trading partner agreement confirms the direction and version for your account. ### When is an EDI 104 sent? A shipper tenders freight to an air carrier and transmits the airbill and rating detail for that shipment electronically. Your partner guide sets any deadline or schedule for the document. ### What is the difference between EDI 104 and EDI 110? The 104 carries the air shipment and is used when air-freight booking is ready for carrier processing. The 110 carries the air-freight payable and is used when carrier billing is ready to reconcile. ### What should I map for X12 104? Start with air waybill, shipment reference and piece identifiers and the target air 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 104 error handling? Split a shipment across pieces and reconcile their weight with the shipment total. Send an unknown consignee and hold it for address resolution before dispatch. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment. ### Which partners list X12 104? The directory on this page links 1 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires. ### How does 104 relate to other EDI messages? X12 110 Air Freight Details and Invoice is a related document linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete. ## 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)