2 Key concepts

A product line or model, such as "Heritage Chronograph 42". It defines the fields every item carries, the verification page design, fraud rules, forms and workflows. An asset can be limited to a fixed number of products.

One physical item of an asset, with its own values (serial number, batch…) and a short identifier such as 7eWb86L. Products can be blocked or deleted.

The carrier that proves a product is genuine: an NFC tag (NTAG 424, NTAG 215, EM4425) or a barcode/QR code. A product can have more than one.

One scan of an authentication by anyone. It is either valid or invalid, with a reason such as "Invalid CMAC" or "Product is blocked".

A piece of product data defined on the asset: Text, Email, Number, Select, Lookup, Date or Checkbox. Fields can be required, protected (encrypted), hidden from consumers, or editable later.

A reusable bundle of fields and a page template. Pick a preset when creating an asset to start from the same structure every time.

A managed list of values (materials, boutiques, markets…) that Lookup fields draw from, so everyone uses the same spelling.

A colored tag on a product or authentication, such as "Sold" or "In service". Labels drive templates, forms and workflows.

The verification page a customer sees. Each asset has a verified page, an optional unverified page and optional auth templates for specific countries, labels or tag types.

Workflows react to events (a scan, a block, a fraud alert, a form, a webhook) with actions. Forms collect customer input on the verification page.