Skip to main content

EDI 945: Warehouse Shipping Advice

A warehouse’s confirmation that an order shipped: what, when, by which carrier, with tracking. Warehouse or 3PL to the shipper (the owner of the goods). This page covers what the 945 is for, the segments you meet when you open one, the documents it travels with, where it tends to go wrong, and how it moves over AS2 into your systems on Files.com, which receives, parses, validates, and routes it as configuration.

No credit card required · 7-day free trial · Live in minutes

#1 MFT vendor in Gartner Peer Insights
Trusted by 4,000+ companies
Every protocol included

What The 945 Is For

The 945 is the warehouse telling the owner of the goods that the 940 it received has shipped. It carries the shipment identification and date, the carrier and tracking or PRO number, the ship-to, and each item with the quantity actually shipped, which can differ from the quantity ordered when stock is short.

The shipper uses the 945 to build the customer-facing documents: the 856 ship notice to the buyer and the 810 invoice, both of which need the real shipped quantities and the carrier reference. It also closes the 940 in the shipper’s system and drives inventory relief at the warehouse location.

The Segments You Meet First

In document order, the segments that carry the 945's meaning. A partner's implementation guide says which are required and which fields each must hold.

W06

Warehouse shipment identification: shipment id, the depositor order number, ship date, and the customer PO.

N1

Parties: ship-to and ship-from.

W27

Carrier detail: the carrier, mode, and service level used.

W12

Warehouse item detail: quantity shipped and product identifiers, one per line.

W03

Total shipment information: units, weight, and volume.

Where It Goes Wrong

Quantity shipped short of quantity ordered without a clear indication is the recurring one; the shipper’s system builds an 856 and 810 for the full order and the customer receives less. Missing or malformed tracking references in the W27 loop are the other, because the downstream 856 needs them.

The Documents It Travels With

The 945 rarely moves alone. These are the documents that precede, answer, or settle it.

940 · Warehouse Shipping Order

A shipper’s instruction to a warehouse or 3PL to ship goods to a customer.

See The 940

856 · Ship Notice / Manifest (ASN)

The advance ship notice: what is in the shipment, how it is packed, and how it is labeled, sent before it arrives.

See The 856

810 · Invoice

The supplier’s bill for goods or services delivered against a purchase order.

See The 810

943 · Warehouse Stock Transfer Shipment Advice

A shipper’s notice to a warehouse that inbound inventory is on its way to be received.

See The 943

944 · Warehouse Stock Transfer Receipt Advice

A warehouse’s confirmation of inventory received: what arrived, in what quantity and condition.

See The 944

How The 945 Moves On Files.com

A partner sends the 945 over AS2, SFTP, or FTPS, and it lands in that partner’s inbox folder on Files.com with the transport receipt recorded. From there it is a workflow, not a project: TransformScript parses the X12 natively into the JSON, CSV, or XML your ERP or WMS reads, content validation flags a document whose contents are wrong before anything ingests it, and an automation routes the result to the system and the people who act on it.

Outbound is the mirror image. Your system exports its record, TransformScript builds the 945 the partner’s guide specifies, and the file dropped in the partner’s outbox goes out over AS2 with automatic retries until the MDN confirms delivery. Every transmission in both directions is in the audit log, and delivery monitoring alerts when a 945 that was due never arrives. The full picture is on the EDI software page.

EDI 945 Questions

What teams ask about the 945 and how it moves on Files.com.

An EDI 945 is the X12 Warehouse Shipping Advice. A warehouse or 3PL sends it to the owner of the goods to confirm that a shipping order (the 940) has shipped, with the quantities shipped, the carrier, and the tracking reference.

The 945 goes from the warehouse to the shipper; the 856 Ship Notice goes from the shipper to the buyer. The 945 is often the source data for the 856.

Yes. Files.com is a standards-compliant RFC 4130 AS2 endpoint, and a 945 sent by a trading partner lands in that partner’s inbox folder with a signed MDN receipt returned to the sender. Partners who exchange over SFTP or FTPS connect to the same platform and the document lands in the same place.

Yes. TransformScript parses the X12 945 natively and writes the JSON, CSV, or XML your systems ingest, as a step in the workflow that fires when the document arrives. Outbound, the same engine builds a 945 from your system’s export and drops it in the partner’s outbox for delivery.

Exchange The 945 Without The Legacy Stack

Start the 7-day trial, turn AS2 on, and exchange certificates with your partner. The 945 lands in their folder, parses into the record your system reads, and every transmission carries a signed receipt.

No credit card required • Free for 7 days • Live in minutes