Documentation
How AVRA works, written for the three people who have to make it work: the printer, the brand's team and the developer.
What AVRA is
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 one word — GENUINE, VALID, SCANNED BEFORE, NO MATCH, We can't verify this code, or RECALLED — each of which is evidence of one stated fact.
Codes are generated in batches, one brand and one product at a time, and a batch spends one credit per 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.
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.
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.
Start here
Everyone. The code lifecycle is the one concept the rest of the platform is built on.
- The life of a codeGenerated, exported, activated, blocked: the five states a batch of AVRA codes moves through, why codes are born dead, and what each state lets you do.
- Every verdict a scan can returnEach verdict an AVRA scan can return — GENUINE, VALID, SCANNED BEFORE, NO MATCH, We can't verify this code, RECALLED — what it means and what to tell a buyer.
- GlossaryThirty words in anti-counterfeiting defined precisely — batch activation, Dual Code, scan limit, 194R, DPDP — and the ones this category abuses, flagged.
Running a programme
The printer holding a job bag, and the brand's team running batches, rewards and warranty day to day.
- Generating a batchGenerating an AVRA batch: the line, the mode, the verification limit, the lot number and the product facts, and why each is frozen the moment the codes exist.
- Uploading batches from a spreadsheetMany AVRA batches for one product from an Excel file: the pre-filled template, a preview that writes nothing, a retyped total, and what a rejected row means.
- What is in the print fileWhat an AVRA print export contains, file by file and column by column — codes.csv, SVGs, the Excel bundle, the manifest, checksums — and the row-order rule.
- Artwork specPrinting an AVRA label: QR size, quiet zone, error correction, finish, the scratch panel, what changes per substrate, proofing and QC, and what fails a run.
- Activation and QCThe QC step before an AVRA batch goes live: what to test and on how many phones, what activating does, and why a test scan before it is supposed to fail.
- Running a rewards programmeCampaigns, budgets, rolling caps and holds, PAN and TDS under section 194R, and payouts on the brand's own Razorpay X or Cashfree account — how Rewards runs.
- Warranty registrationHow AVRA Warranty registers a purchase on the buyer's genuine scan: three questions, a frozen expiry, one registration per label, a masked care-desk export.
- CertificatesCertificates from your own records: one QR per record, matched by record ID, GENUINE with a separate status, revocation with a reason, and why forgery fails.
Integrating
A developer deciding whether this can be wired into an existing system — written to say what exists today and what does not.
- The API, stated honestlyAVRA's API is the one the console uses: JSON over HTTPS, a bearer session token, scoped to one tenant. No long-lived API keys yet, and this page says so.
- WebhooksWebhooks today are inbound only: signed payout callbacks from the brand's own gateway. Outbound webhooks, AVRA calling your system on a scan, do not exist yet.
- WhatsApp message templatesThe eight WhatsApp templates AVRA sends — seven Utility, one Authentication — their bodies, variables and triggers, and the two rules that silently break sends.
- Getting your data outEvery file the AVRA console produces today — print files, the TDS file, payout statements, the masked warranty export — and what is on screen, not yet a file.
Last reviewed 18 Sep 2026 · Something wrong? connect@avrascan.com