Skip to content
X12 EDI

Wiz X12 104 Air Shipment Information

Plan X12 104 Air Shipment Information for Wiz gmail. Connect document identifiers to your business records, test exception handling and track each exchange to completion.

Segments
Not listed
Loops
Not listed
X12 104
Partner references ↗

Implementation guide

Wiz gmail: 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.

This document is listed for Wiz gmail. Confirm the version, required fields and responses that apply to your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat 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.

Segment and field details are not available for this document here. Request the current partner guide and a sample document to complete the field mapping.

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 Wiz 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.

Transaction context

Where 104 Air Shipment Information fits on Wiz gmail

Wiz channels
1 of 2

1 of Wiz's 2 channels list 104

Trading partners
1

partner references list 104

Channels
1

channel entries list 104

Wiz gmail EDI 104 questions

Common questions about 104 Air Shipment Information on the Wiz gmail channel.

What is X12 104 Air Shipment Information used for?

104 is used when air-freight booking is ready for carrier processing. It carries information for the air shipment. Match it to your business system using air waybill, shipment reference and piece identifiers.

Is 104 required for Wiz gmail?

104 is listed for Wiz gmail. Confirm the required version and direction for your business unit and account with the partner.

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.

How does 104 relate to other EDI messages?

Keep 104 business processing separate from transport receipt and technical validation. Agree which preceding record, response or reconciliation completes the air shipment workflow; confirm any required companion messages with your partner.

Connect Wiz 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.