ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

X12 250 — Purchase Order Shipment Management Document

The 250 transmits the shipment management details tied to a purchase order: split shipments, partial deliveries, multi-DC allocations, shipping instructions.

Purpose

The 250 documents how a PO will be shipped: split across warehouses, partial shipment planning, drop-ship instructions, special carrier routing, customer DC allocations. It is a supply-chain coordination instrument between supplier, carrier, and receiving DC.

It is used after receipt of the 850 and before issuance of the 856. Acknowledged by 997; serves as input for 856 production.

Envelope structure

The 250 travels within the three X12 envelope levels (ISA/IEA, GS/GE with functional group PM, and ST/SE). Didactic example in release 004010:

x12 example-250.x12 
ISA*00*          *00*          *ZZ*SUPPLIER      *ZZ*BUYERCORP      *260514*1100*U*00401*000000250*0*P*>~
GS*PM*SUPPLIER*BUYERCORP*20260514*1100*1*X*004010~
ST*250*0001~
BGN*00*PM-2026-0042*20260514~
PO1*1*100*EA*9.99**UP*012345678905~
LX*1~
N1*SH*WAREHOUSE A*92*WH-A~
QTY*ZZ*60~
DTM*002*20260520~
LX*2~
N1*SH*WAREHOUSE B*92*WH-B~
QTY*ZZ*40~
DTM*002*20260522~
SE*12*0001~
GE*1*1~
IEA*1*000000250~

Common segments

  • Header — ST, BGN, PO1 (reference to original PO).
  • Allocations — repeated LX loop per split: N1*SH (source warehouse), QTY*ZZ (allocated quantity), DTM*002 (planned date).
  • Instructions — REF*ZZ (routing, carrier preference), MSG (special handling).
  • Summary — SE.

Common pitfalls

  • Coherent total: the sum of QTY*ZZ per split must equal PO101; an over-total commits overship, an under-total forces backorder.
  • Allocation window: DTM*002 must respect the original PO delivery date — diverging without pre-approval exposes to retailer chargebacks.
  • Routing vs supplier choice: if the buyer mandates a carrier (collect terms), the 250 cannot re-assign; always validate the routing guide before sending.

Documentation

The code 250 and the name Purchase Order Shipment Management Document are public and listed on x12.org/products/transaction-sets. The complete structure of loops, qualifiers and code lists is distributed by DISA via the proprietary Implementation Guides (TR3). ediverse.io covers only public concepts, the envelope and didactic examples.