Skip to content

X12 transaction code

X12 945 Warehouse Shipping Advice

X12 945 Warehouse Shipping Advice: explore its business purpose, mapping identifiers, validation tests and 13 partner references across 14 listed channels.

Standard
X12
Code
945
Partner references
13

Implementation guide

X12 945 mapping and validation

X12 945 Warehouse Shipping Advice is used when a warehouse reports what it shipped. Preserve warehouse order, shipment and shipped line so the warehouse shipment confirmation 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 decisionRecord and matching IDsWhat to test
Match the business record warehouse shipment confirmation

warehouse order, shipment and shipped line

  • Define which combination of warehouse order, shipment and shipped line identifies one business record, its lines and any later revision.
Update the receiving system Processing the warehouse shipment confirmation

ID assigned by the receiving system and processing result

  • Test partial fulfillment and leave the unshipped order quantity open.
  • Reconcile shipped units and tracking references before preparing a customer-facing shipment notice.
Check the processing result Processing status for the warehouse shipment confirmation

Original document reference and matching response

  • Reconcile the warehouse shipment confirmation 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.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when a warehouse reports what it shipped. Name the operational owner of the warehouse shipment confirmation and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map warehouse order, shipment and shipped line. 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 warehouse shipment confirmation 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 warehouse shipment confirmation processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 945 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic warehouse shipment confirmation 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 warehouse shipment confirmation without processing it twice.

Document structure

X12 945 Warehouse Shipping Advice at the element level

The X12 945 reference contains 58 segment entries and 279 data elements; 68 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
58
Data elements
279
Mandatory elements
68
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
W06 12 1
N1 6 1
N2 2 1
N3 2 1
PER 9 1
N9 6 1
G61 5 2
NTE 2 1
W27 10 1
W6 4 1
W28 8 1
G72 11 2
Key identifiers in 945
  • Reporting Code
  • Entity Identifier Code
  • Name
  • Address Information
  • Contact Function Code
  • Reference Identification Qualifier
  • Description
  • Transportation Method/Type Code

Catalog breakdown

Where X12 945 Warehouse Shipping Advice appears in this catalog

The largest groups of classified 945 catalog entries are in logistics & transport, grocery & food and electronics & technology.

By industry

  • logistics & transport 6 channels
  • grocery & food 5 channels
  • electronics & technology 2 channels
  • manufacturing & industrial 1 channel

FAQ

X12 945 questions

What is X12 945 Warehouse Shipping Advice used for?

945 is used when a warehouse reports what it shipped. It carries information for the warehouse shipment confirmation. Match it to your business system using warehouse order, shipment and shipped line.

Which partners list X12 945?

The directory on this page links 13 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.

What should I map for X12 945?

Start with warehouse order, shipment and shipped line and the target warehouse shipment confirmation. 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 945 error handling?

Test partial fulfillment and leave the unshipped order quantity open. Reconcile shipped units and tracking references before preparing a customer-facing shipment notice. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does 945 relate to other EDI messages?

X12 940 Warehouse Shipping Order; X12 856 Ship Notice Manifest; X12 810 Invoice are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

What is the difference between 945 and 940?

945 is used when a warehouse reports what it shipped. 940 is used when stock is released to a warehouse for shipping. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

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.