Documentation

AVRA puts a serialised code on a label, carton, sleeve or pouch you already print, so that one unit of a product can be checked by anybody with a phone camera. There is no app. The camera opens a page, the page asks our servers, and the answer is a verdict — GENUINE, VALID, SCANNED BEFORE, NO MATCH, RECALLED, or We can't verify this code — plus a few line-specific answers. Each is evidence of one stated fact; see every verdict.

Codes are generated in batches, one brand and one product at a time, and a batch spends one credit per label (a Dual Code label, with its two codes, is one label) when it is generated, not when it is scanned. Every code is born dead: it answers nothing until the printed run has passed QC and somebody activates the batch. That is why a leaked print file or a press overrun verifies nothing. Every code verifies for three years from the day its batch is switched on, whatever happens to your plan. After that it shows a neutral “verification period has ended” page with your care number — never “fake” or “expired”. Our promises lists the rest.

A label can carry one code or two. With two — the Dual Code — the shelf code answers anybody without spending anything, and the hidden code under a scratch panel claims the unit once. What a genuine scan does is chosen per batch: verify the unit, register a warranty, pay a reward to the trade, or show a certificate's own fields (certificates have one code and their own page).

Every scan lands in the brand's console with the date and an approximate place, and the platform watches for the patterns that mean a copy — one code claimed from many networks, unactivated labels being scanned, codes that were never issued. The scan data is the brand's; AVRA processes it.

Pick the path that is yours.