Skip to content

Glossary

Core terms used across the platform and this documentation.

The record of a single product check, carrying an outcome, a state, the product and brand it belongs to, where and when it was captured, and the evidence behind the result.

The result of a check: Authentic (genuine), Not Authentic (failed; likely counterfeit), Uncertain (ambiguous; needs a human decision), or Error (the check could not be completed).

Where an event is in its lifecycle: Pending, In Progress, Completed, or Expired.

Whether a record is an Authentication check (produces an outcome) or a Data Collection capture (labelled training data; produces no verdict).

A protected product line within your organisation. Events, products, and configuration are organised under brands.

A specific item type under a brand that is being authenticated. A product is configured with the region(s) to capture and the pipeline used to verify it.

A specific area of the product to capture — for example a front label or a cap seal. Some products require more than one ROI; some ROIs are optional.

The configured method used to decide an outcome for a capture. Different brands and products may use different pipelines.

An isolated customer workspace. Each tenant’s data, users, and configuration are kept separate from every other tenant’s.

A field user who captures products in the mobile app and submits feedback on results. Inspectors have limited dashboard access.

A dashboard user who monitors brand health, investigates events, and resolves the Review Center queue. Analysts have access to everything an inspector has, plus Analytics, Review Center, and usage consumption. A supervisor can also grant an analyst access to KPIs.

A dashboard user with everything an analyst has, plus KPI and usage limits. Supervisors set inspector targets, the tenant’s monthly request limit, and its alert thresholds.

The authentication activity target a supervisor sets for inspectors. Each one has a metric, a target value, a period (day, week, month, or a custom range), and a scope (specific inspectors, brands, or products). The dashboard’s KPIs area shows fulfillment against the target and coverage gaps. Inspectors see their own progress on the mobile app’s Home screen.

How many requests your tenant has spent against its monthly limit. One request is one image authentication of one ROI. The dashboard’s Usage area shows consumption and a trend view. Supervisors set the limit and the alert thresholds.

The dashboard area where analysts resolve records that need a human decision — those marked Uncertain and those where an inspector disagreed with the result.

A mobile-app mode that captures labelled training images instead of running authentication. The inspector labels what was captured; no verdict is produced.

A mobile-app mode that lets you capture without a connection. Sessions are stored on the device and upload — automatically or when you choose — once a connection is available, at which point their results appear.

The mobile-app screen listing your recent and pending captures on a device, with each session’s status. It is where offline work is synced and results are revisited. It is per-device and distinct from the dashboard’s Live Events.

A support request raised from inside the mobile app or the dashboard, with a subject, category, description, and optional attachments. Replies are followed in the same thread.