Skip to content
Independent EDI conversion and validation software. Retailer names identify interoperability targets; no retailer endorsement is implied.
Shipment Sentry

Validate an EDIFACT DESADV before dispatch.

Paste or upload the exact dispatch advice. Check the UNB/UNZ interchange, UNH/UNT message controls, DESADV identity, required segments and line-to-quantity pairing. Anonymous documents are never retained.

SUPPORTEDLive: DESADV structural preflight
Boundary: directory + partner profile
0 bytes
01

Your report appears here.

Start with a sample if you want to see the output before using a live document.

  • ✓ Exact segment or JSON pointer
  • ✓ Evidence class and source link
  • ✓ Concrete remediation
  • ✓ Versioned rule pack

This preflight checks EDIFACT syntax and public DESADV structure. The selected directory, EANCOM subset and current partner implementation guide remain controlling.

Structural DESADV preflight, honestly scoped.

The live pack verifies UNB/UNZ and UNH/UNT references, message identity, segment count, required BGM, DTM, RFF, LIN and QTY content, and one quantity for every line.

It does not claim complete directory, EANCOM or trading-partner conformance. Pin the production route to the receiving partner’s current directory and implementation guide.

Read the DESADV validation guide →

Interchange and message controls

UNB/UNZ controls, UNH/UNT references and the final emitted message count must agree.

Dispatch-advice structure

The live pack identifies DESADV and checks required header, reference, item and quantity segments.

No invented directory certainty

Directory, EANCOM and account-specific rules stay explicit partner-pack requirements.