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 219 — Logistics Service Notification

The 219 notifies a logistics actor — 3PL, broker, shipper — of an event or a service request outside pure transport (warehousing, cross-dock, repackaging).

Purpose

The 219 documents a logistics service notification: warehousing order, cross-dock instruction, return pickup, consignment placement. It complements the 211/204 on pure transport by covering value-added services of a 3PL.

It is used by retail and industrial shippers to orchestrate their multi-service logistics providers. Acknowledged by 997; a 220 (Logistics Service Response) follows for confirmation.

Envelope structure

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

x12 example-219.x12 
ISA*00*          *00*          *ZZ*ACMERETAIL    *ZZ*3PLPARTNER    *260515*0930*U*00401*000000219*0*P*>~
GS*LN*ACMERETAIL*3PLPARTNER*20260515*0930*1*X*004010~
ST*219*0001~
B2A*00*LN~
N9*SI*SVC-NOT-2026-4421~
N1*BY*ACME RETAIL CO*92*0001~
N1*3P*ACME 3PL PARTNER*92*PRV-001~
N7*XXXU*1234567~
L11*WO-2026-9988*ZZ*CROSS-DOCK INSTRUCTION~
SE*8*0001~
GE*1*1~
IEA*1*000000219~

Common segments

  • Header — ST, B2A (Beginning Segment for Application Transactions).
  • Service reference — N9*SI (Service Identifier).
  • Parties — N1*BY (Buyer), N1*3P (Third Party Logistics).
  • Equipment — N7 if container or trailer involved.
  • Instructions — L11 (Business Instructions and Reference Number).
  • Summary — SE.

Common pitfalls

  • Scope confusion: the 219 is not a load tender (204); sending it for pure transport misroutes the 3PL and stalls the TMS.
  • Service-level contracting: a 219 without an SLA referenced in L11 does not trigger correct priority handling — always carry the contract.
  • Missed confirmation: not waiting for the 220 reply exposes to poor visibility; pair 219 + 220 in monitoring.

Documentation

The code 219 and the name Logistics Service Notification 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.