ONE CODE,
ONE ITEM'S HISTORY.

Being built

A barcode says what a product is. It does not say which one, where it came from or what has happened to it — and almost every question worth asking about a specific item needs that distinction.

GET STARTED →

SCAN A LOT

Where has it been?

What to know

Item identity, not product identity

A GTIN identifies a product line. Unit-level identity identifies this one, which is what recall scoping, warranty, resale provenance and counterfeit detection all actually require.

What it makes possible

Each of these is impossible with product-level identity alone and straightforward with unit-level identity.

Recall a lot instead of a line
Verify an item is what it claims before buying it secondhand
Carry a repair history with the object
Prove a chain of custody for a regulated product

The record has to start at the beginning

A history that begins when somebody decides to resell has a gap exactly where the authenticity question lives. Unit identity is assigned at manufacture or first sale, or it is worth substantially less.

Status

Designed, not built. The append-only event log is the right substrate for an item history and exists today; unit-level identity and the scan surface do not.

Where to go next

RESALE WITH PROVENANCE.

Secondhand markets are limited by one thing: the buyer cannot verify what they are buying.

Read it

A RECORD NOBODY CAN EDIT.

Every meaningful action on GRAJ is written to a log that only ever grows.

Read it

THE HEALTHCARE SUPPLY CHAIN.

Healthcare supply chains are built around traceability and substitutability.

Read it

CHECKING GOODS BEFORE THEY MOVE.

Inspecting goods before they leave the factory is the single highest-return check in cross-border trade.