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

Free working tool

SSCC Validator for GS1 Check Digits and ASN Labels

Validate an 18-digit SSCC and compare the message value with the printed logistics label.

Use the free validator See batch and API plans

Direct answer

Direct answer

An SSCC is an 18-digit GS1 logistics-unit identifier. The final digit is calculated from the preceding 17 digits using alternating weights of three and one from the right. A valid check digit proves arithmetic consistency, not that the carton carries the same label. ASN control should normalize accepted GS1 application-identifier notation, reject malformed length or characters, calculate the check digit independently, and compare the message with the physical label source.

Why a parser is not enough

The useful unit is not a file that parses; it is a business document with a known decision, an owner, a source trail and a matched downstream response. This page connects the technical structure to that operating workflow.

What the control should check

  1. 01Normalize optional (00) application-identifier notation.
  2. 02Require exactly 18 digits after normalization.
  3. 03Calculate the check digit from the first 17 digits.
  4. 04Compare MAN value with the printed label.
  5. 05Detect duplicate SSCC values inside one shipment.

Working example

(00)000123456789012343 → body 00012345678901234 / check digit 3

The excerpt is intentionally compact. Use the working validator or authenticated gateway with the complete interchange to obtain a decision.

Failure modes worth catching

  • A transport receipt is mistaken for business acceptance.
  • Control identifiers are regenerated between validation and submission.
  • A warning has no owner and becomes a recurring manual investigation.
  • The document is checked alone even though the truth exists in a purchase order, label or acknowledgement.

Put it into the dispatch workflow

  1. 1Validate the source document before transport.
  2. 2Block deterministic failures and assign every review item.
  3. 3Release with a recorded owner and timestamp.
  4. 4Match functional and application acknowledgements.
  5. 5Reconcile confirmed outcomes back into fixtures and rules.
Use batch validation and acknowledgement tracking

Questions

Implementation answers

Does Shipment Sentry replace my EDI provider?

No. It sits before the existing transport as a validation and evidence sidecar.

What does cleared mean?

The document has no blocking finding in the current rule pack. It is not a guarantee of trading-partner or receiving acceptance.

How are repeat requests kept safe?

The API requires an idempotency key, stores only a token hash, scopes every record to one workspace and rejects reuse with different content.

Sources and limits

Reviewed 2026-07-18. Public references cannot establish every partner-specific rule. Current implementation guides and agreements remain controlling.

Keep investigating

Related EDI controls

View the library
Validate the PDF/A-3 layer of a ZUGFeRD or Factur-X invoice Validate an X12 824 Application Advice before it enters production Validate an X12 810 Invoice before it enters production Online EDI File Validator for X12 Documents Validate an X12 997 Functional Acknowledgement before it enters production Validate an X12 855 Purchase Order Acknowledgement before it enters production