Skip to main content

EDI 943: Warehouse Stock Transfer Shipment Advice

A shipper’s notice to a warehouse that inbound inventory is on its way to be received. Shipper (the owner of the goods) to the warehouse or 3PL. This page covers what the 943 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 943 Is For

The 943 is the inbound counterpart of the 940. When a company sends inventory to a third-party warehouse, it sends a 943 ahead of the shipment so the warehouse knows what is arriving, from where, by which carrier, and in what quantities, and can plan receiving and put-away.

The warehouse confirms what it actually received with a 944. Together the 943 and 944 keep the owner’s view of inventory at the warehouse in step with the warehouse’s own count.

The Segments You Meet First

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

W06

Warehouse shipment identification: shipment id, date, and references.

N1

Parties: ship-from and the receiving warehouse.

N9

Additional references such as a purchase order or bill of lading.

W04

Item detail for a warehouse shipment: quantity and product identifiers.

W03

Total shipment information: units, weight, and volume.

Where It Goes Wrong

A 943 that never arrives, so the warehouse receives blind and the owner’s inventory shows stock the warehouse has not confirmed. Item identifier mismatches between the owner’s system and the WMS are the everyday failure.

The Documents It Travels With

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

944 · Warehouse Stock Transfer Receipt Advice

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

See The 944

940 · Warehouse Shipping Order

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

See The 940

945 · Warehouse Shipping Advice

A warehouse’s confirmation that an order shipped: what, when, by which carrier, with tracking.

See The 945

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

How The 943 Moves On Files.com

A partner sends the 943 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 943 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 943 that was due never arrives. The full picture is on the EDI software page.

EDI 943 Questions

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

An EDI 943 is the X12 Warehouse Stock Transfer Shipment Advice. The owner of goods sends it to a third-party warehouse to announce an inbound shipment of inventory, with the items, quantities, and carrier, so the warehouse can plan receiving.

The 943 announces inventory shipped to the warehouse. The 944 is the warehouse confirming what it received.

Yes. Files.com is a standards-compliant RFC 4130 AS2 endpoint, and a 943 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 943 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 943 from your system’s export and drops it in the partner’s outbox for delivery.

Exchange The 943 Without The Legacy Stack

Start the 7-day trial, turn AS2 on, and exchange certificates with your partner. The 943 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