# SSCC — Serial Shipping Container Code

> The SSCC registry row: eighteen digits naming one logistic unit, the mod-10 rail, AI (00), and the custody join into AggregationEvents.

- page: https://barcoding.dev/schemes/sscc/
- machine row: https://barcoding.dev/schemes/sscc.json
- scheme (dotted registry name): gs1.sscc

## Reference
- grammar: 18 digits — extension digit, GS1 company prefix, serial reference, check digit. Carried as AI (00); names exactly one logistic unit, serialized by construction.
- check: GS1 mod-10, right-anchored — the same rail as every GS1 key.
- canonical: The 18-digit form; EPC form urn:epc:id:sscc.
- barcode types: GS1-128 on the logistics label; the AI (00) line is the scannable spine of the SSCC-18 label
- enrichment: identity is open; shipment context is per-caller — the ASN that names this SSCC belongs to the parties on it
- join: AggregationEvent parentID (CBV 2.0 §8.5): the pallet gains and loses its cases against this one identifier — the unit of custody.

## Registry rows (engine artifacts, digest-stated)
### gs1.sscc
- grammar: `^\d{18}$`
- check: mod10 → "mod10 pass" (GS1 GenSpecs 26.0 §3.3.1, §7.9)
- canonical: 18 digits
- segments: extension digit · GS1 company prefix · serial reference · check
- generate: gs1-128
- hand-off: read here · resolved by id.org.ai
- digest: sha256:2cc9a5e60d67ffe766f2b7228b3f8269ad7e8c9d925146e6a027a989061ce122

## Resolution stance
barcoding.dev detects, parses, verifies, enriches and generates — the codec and the data layer. Resolution — an identifier answered with identity and its linkset of live doors — is ONE capability family-wide, served by the family's identity layer, id.org.ai; vertical estates project the same one capability (vehicles: auto.dev). This registry row is the data that resolution consumes.

## Posts
- https://barcoding.dev/blog/sscc-the-unit-of-custody/
- https://barcoding.dev/blog/the-case-and-the-pallet/
- https://barcoding.dev/blog/tracking-numbers-scheme-family/