Skip to content
AVRA
Book a demo
Book a demo

For printers and packaging companies

You already print what goes on the pack. Add the code that proves it.

AVRA is the software under what you already print — labels, sleeves, cartons, pouches, security print, foil. Your name on the scan page, your portal, your customers, your invoice. We do not sell to your brands.

Apply as a partnerSee what a brand sees →

Written for printers, converters and packaging companies: label converters, flexible-packaging printers, carton and corrugated printers, security printers, hologram makers and packaging suppliers.

How AVRA reaches a brand

1 credit = 1 label

AVRA sells credits to a partner — a printer, converter or packaging company. The partner prints the codes into what it already makes and sells protection to the brand under its own name. The brand puts one label on each unit. A consumer scans with a phone camera and no app; every scan reaches AVRA, and the brand sees the results in its own console.

  1. AVRA

    Issues the codes. Records every scan.
  2. credits

  3. Your partner

    A printer or converter. White-labelled console.
  4. labels

  5. Brand

    Buys protection by the label.
  6. one label per unit

  7. Consumer

    Phone camera, no app.

every scan reaches AVRA

The brand sees, in its own console:

Scans by city

Suspicious-scan alerts

Consumer fake reports

FIG 1How the three sides fit. You buy credits from us and sell labels to your brand. Every scan goes to the brand. You see your brands and no one else's.

What changes on your line

Nothing. The code is one more element in the artwork.

What you already do, and what AVRA hands you for it
You already do thisWhat we hand you
Variable data — a roll, a sheet, a web, a cartonOne CSV per batch: label, qr, then qr2 or scratch
Registered printing15 mm minimum at 600 dpi, quiet zone intact
A scratch panel, or a second code under a flap or a capError correction M outside, H under a panel, because scratching abrades
Job-bag paperworkmanifest.csv — one row, everything QC needs to match a roll to a batch
Checking a file arrived wholeSHA256SUMS.txt, a digest per file

No new press. No new software on the line. No ink change, no varnish change and no substrate change — with one exception: a matte, light area under the code, with no gloss varnish, no lamination gloss and no holographic film over it. A phone camera cannot read a code through a glare, and finding that out on a customer's first run is an expensive way to learn it.

Which press you run does not matter. Flexo on a roll, rotogravure on film, offset on board, digital on anything: if you can put variable data on it and hold registration, you can print an AVRA code. What differs between substrates is not the code — it is how much the pack can carry, and that is the next section.

The print spec, for a production head

  • One CSV per batch. Columns: label, qr, then either qr2 or scratch. Nothing else.
  • label is an integer and it stays in the file on purpose. An imposition job that loses row order mis-pairs a QR with another label's hidden code, and every mis-pair is either a reward paid on a pack nobody bought or a genuine pack that reads as used. One integer column is the cheapest defence there is, and QC needs it to find label 4,312 on a roll.
  • 15 mm minimum at 600 dpi. Quiet zone intact. A matte, light area under the code. No gloss varnish.
  • Error correction M on the shelf QR, H on the one under the foil.
  • manifest.csv — one row per batch: batch id, brand, product, line, mode, which second factor, the label range, the verification limit, lot number, the dates, generated-at in IST, and the scan URL the codes were built against.
  • SHA256SUMS.txt — a digest per file, taken as each file is written. If a file arrives short, you find out before the press does.
  • An Excel bundle with the QR images embedded at 338 dpi, for handover. Somebody always prints from the Excel whatever the banner says, so it is at print resolution.

Seven lines, because that is what an owner needs to decide. Your prepress team wants the whole thing: the artwork spec — placement per substrate, the scratch panel, the quiet zone, and a die-line to check against.

What the code sits on

The code prints on anything you can hold registration on. What changes between substrates is how much the pack can carry.

What each substrate can carry. The print constraints are what we have observed on these formats — confirm them with your own process.

  • Pressure-sensitive label

    paper or filmic

    Which codes it can carry
    Both: shelf QR on the face, hidden code under a scratch panel.
    Tamper-evidence available
    Destructible or brittle face stock, VOID-release adhesive, or a tamper-evident die cut. A plain paper label on permanent adhesive gives none.
    Print constraints
    A matte, light window; no gloss varnish or lamination over the code. Below about 25 mm container diameter the curve starts costing reads.

  • Hologram / OVD foil

    optically variable device

    Which codes it can carry
    Both.
    Tamper-evidence available
    The strongest generally available. Hard to source, expensive to originate, and a registered design is traceable.
    Print constraints
    A matte, non-metallised window for the QR is mandatory — on metallised foil the code has poor contrast and mirrors shop lighting into the camera.

  • Shrink sleeve

    PVC / PETG / OPS

    Which codes it can carry
    Shelf code, reliably. A hidden code needs a cap seal, a perforated tear-off, or a second label under the sleeve.
    Tamper-evidence available
    Only from a perforated tamper band. A plain full-body sleeve can be slit, removed and replaced.
    Print constraints
    Distortion mapping. Put the code in the lowest-shrink band, pre-distort it with the artwork, and proof it on a shrunk bottle, never flat.

  • Folding carton / mono-carton

    board

    Which codes it can carry
    Both: shelf QR outside, hidden code on the inside face or under a glued flap.
    Tamper-evidence available
    None from the board. It must come from a seal across the flap, a tearing glue closure, or a shrink band.
    Print constraints
    Dot gain on uncoated board — allow for it at plate stage rather than shrinking the code. Off the crease, off the glue flap, out of any spot-UV.

  • Flexible pouch / laminate

    film

    Which codes it can carry
    Shelf code outside; hidden code on the inside web or under a zipper flap — genuinely unreachable until opened.
    Tamper-evidence available
    Only from the seal, and a carefully re-sealed pouch is hard to detect. None from the film.
    Print constraints
    On rotogravure the cylinder is fixed: variable data comes from a separate inkjet or laser station. Metallised film needs a white base under the code.

  • Corrugated shipper

    outer

    Which codes it can carry
    Shelf code only.
    Tamper-evidence available
    None. A logistics outer carries no evidence; treat any claim otherwise as false.
    Print constraints
    Low contrast and heavy dot gain on kraft: 18–20 mm, not 15, on white-lined board or a preprinted liner — or apply a pressure-sensitive label to the corrugate.

  • Direct mark on the product

    laser, thermal inkjet

    Which codes it can carry
    Shelf code only, unless a second surface exists.
    Tamper-evidence available
    None from the mark.
    Print constraints
    Contrast is everything; a laser mark on a dark or shiny surface usually fails. Proof on the real material at real line speed.

A code is not tamper-evidence, and nothing about this platform makes it one. The code proves that this label was issued for this unit and has not been claimed. Proving that the pack has not been opened is a job for something physical — a destructible face stock, a VOID adhesive, a hologram, a perforated band, a seal that tears. Choose one, or state that you have not.

The format decides which verification mode a brand can have. Dual Code — a visible shelf code plus a hidden one the buyer reaches only after purchase — is the strongest thing AVRA offers, and it needs somewhere on the pack to hide the second code. Where a format cannot hide one (a bare shrink sleeve, a corrugated outer, a direct mark), the brand runs single mode instead: the first N verifications answer GENUINE and the next answers SCANNED BEFORE. That is a weaker position and it should be sold as one. Limits are frozen per batch: by default 1 for dual, 3 for single.

What holds on every substrate is Batch Activation. Codes are dead until someone activates the batch after printing QC, so a stolen print file and a press overrun verify nothing — on foil, on board, on film, on kraft. It is the one mechanism that does not care what you print.

Whose brand is on it

Yours

  • “Powered by <you>” on every scan page
  • Your own portal login
  • Your brands, products, batches and credit balance
  • Your customers. Yours. Another partner does not know they exist

Not yours, and we will say so

  • The domain the code points at — not available yet, and a printed code cannot be re-pointed
  • The WhatsApp sender number — messages come from AVRA and read “Powered by <you> on AVRA”
  • The console's own name and login page
  • Transactional email from the platform

Credits and margin

You buy credits. You quote your brand. We never see that number.

You prepay credits, and you quote your brand whatever the label, your service and the programme are worth. We never see that number and we do not set a floor on it. Wholesale credit pricing starts from 500,000 credits — talk to us; the rate card is in the partner agreement, not on a web page a brand can read.

One credit is one label. What you add is the pack itself, your printing, any security feature you put on it, your artwork time, your QC and the fact that you will pick up the phone when the brand's plant calls at 11 p.m. Most of the value the brand is buying is that last thing.

Credits for the run
your credit cost
Your pack, printing and service
your number
What you invoice the brand
both — and we never see it

If a partner stops trading with us, its brands' codes keep verifying — a credit was spent when each code was made, and we do not switch off a label on a shelf — and the brand may be served directly so its programme does not stop. That is the platform rule this category has no answer for, and it is why a brand can say yes to you without betting on you.

Getting started

Five steps. The slowest one is your own press.

  1. Account and credits — Same day

    We create your partner account and issue your first credits against an invoice.

  2. Your first brand and product — An hour

    You create the brand and the product: logo, care number, product photo, and up to five facts a buyer can check.

  3. A test batch of 200 — Minutes

    You generate a test batch of 200 and download the print file.

  4. Print, scratch, scan, activate — Your press schedule

    You print it on the real substrate, scratch or open one, scan it on five different phones, then activate the batch.

  5. The first live batch — After QC passes

    Your first batch for the brand goes live.

Step 04 is the one that actually takes time, and it is the one we will not let you skip. Foil, board, shrink film and kraft behave differently on every line, and the only way to know a code reads on a cheap Android in a badly lit shop is to hold one. Run it on the substrate the brand actually buys — a code proofed on paper and printed on shrink film is a different scan.

The questions you are actually asking

I don't make holograms. Is this still for me?

Yes, and the two things AVRA actually sells do not come from a hologram. Batch Activation is a rule in a database — codes are dead until you activate the batch after QC — and it works identically on foil, board, film and kraft. Dual Code needs somewhere on the pack to hide the second code, which is a question about the format, not about who made it. See What the code sits on above for what each substrate can carry.

What a hologram adds is tamper-evidence and hard-to-source physical stock, and it is still the best commonly available answer to both. If you do not make one, the honest options are a destructible face stock, a VOID-release adhesive, a perforated band or a tamper-evident seal — or telling the brand plainly that the pack carries none, which is better than implying it does.

My brands buy cartons and pouches, not labels.

Then the code goes in the carton or pouch artwork. A folding carton carries a shelf code on the outside and a hidden code on the inside face or under a glued flap, which is a good Dual Code pack. A pouch carries the shelf code outside and the hidden code on the inside web — unreachable until the pack is opened, which is exactly what Dual Code wants. The constraints are dot gain on board and, on rotogravure, the fact that variable data has to come from a separate inkjet or laser station rather than the cylinder. Both are in the substrate table, and neither is a new machine.

What if another converter serves the same brand?

It happens, and pretending otherwise would be the fastest way to lose a partner. A brand is one tenant on the platform and it can be served by more than one of you — one prints the label, another prints the carton. What the platform guarantees is isolation: you see the brands you serve and nothing else, and a request for another partner's data returns not found, not forbidden, so you cannot even confirm the other party exists.

The commercial rule for two partners on one brand — who is billed for which batches, and what either side is told — belongs in the partner agreement, and we will put it there rather than improvise it on a web page.

What if my client leaves me?

The brand is yours while it is yours. If a brand moves to another printer, their codes keep verifying — we do not switch off labels on shelves — and we re-point the brand to the new account. We will not do that quietly: you are told.

Who owns the scan data?

The brand owns it. We process it. You see the brands you serve and nothing else — a request for another partner's data returns not found, not forbidden, so a competitor cannot even confirm that a brand exists on the platform. That isolation is tested rather than promised.

We do not sell scan data, we do not use one brand's data for another, and we do not market to your brands.

What do I have to support, and what do you?

What you support, and what AVRA supports
YouUs
The pack: substrate, any security feature, adhesive or seal, print qualityThe platform: codes, scan pages, dashboards, payouts, uptime
The brand's artwork and their plant's questionsYour portal, your logins, your credit balance
Applying the labels correctly, and QC before activationPrint-file generation, exports, the scan URL
The first call when a brand's buyer says a code will not scanThe second call, if it turns out to be us

Realistically, most support calls are about a code that was varnished over by mistake, applied to a curve too tight for it, or placed in a high-shrink zone on a sleeve. That is why the split falls where it does, and why we would rather you run the test batch in step 04 than trust a spec sheet.

What if AVRA disappears?

A fair question to ask a young company, and one we would rather answer than deflect.

Codes are opaque strings in a Postgres database. They are not derived from anything proprietary and they are not locked in a format only we can read. What a printer and a brand need if we are gone is the serial registry, the activation state and the scan history, in a form somebody else can host. That export is specified on What happens if you leave, including what it contains and when you can take it.

Will you go around me to my brand?

No. AVRA sells credits to partners. The one exception is the one written under Credits and margin: if a partner stops trading with us, its brands' labels keep verifying and the brand may be served directly, so a programme on a shelf does not stop.

What if a brand wants a different printer?

See What if my client leaves me, above: the codes keep verifying, the brand is re-pointed, and you are told.

Do I need a developer?

No. Everything is a browser: create the brand, create the product, generate the batch, download the file, activate after QC. A month of runs can be one CSV upload instead of a hundred forms. There is no API today for the print line; it is on the roadmap and it is not required for anything on this page.

What does a brand pay me?

You decide. See Credits and margin.

Six shorter ones

Can I white-label the domain?

Not yet, and when it arrives it applies to batches generated after the change. A printed code carries its URL inside it.

Can two of my staff have logins?

One live login per partner today.

How fast can I get credits?

Ask from your Wallet; a platform admin is emailed and the request shows on their dashboard. Online checkout is not built.

Can I get the print file after the batch is live?

Freely until activation. Afterwards it is platform-admin only, audited, and purged 30 days after activation — because after activation that file is a list of live codes.

Can I run rewards for a brand?

Only if that brand switches it on for you, from their own login. Money access is a second switch, off by default, and it is theirs to flip, not yours and not ours.

What does it cost me to try?

The credits for a test batch of 200 labels. Ask us and we will quote them with your first credits.

Apply as a partner

Tell us what you print — labels, sleeves, cartons, pouches, security print, foil — roughly how many units a month, and which brands you already serve. We will come back with a sample batch on your own substrate and a credit quote.

What you print (pick any)

10 digits; +91 is added for you.

What we do with it → · Withdraw any time at connect@avrascan.com.

We reply within 24 hours — usually the same day. Monday to Saturday, 10:00 to 19:00 IST.

In a hurry? WhatsApp +91 91737 47583 or call +91 91737 47583. A founder answers that number, not a call centre.

Want the label in your hand before you talk to anyone? Ask for a sample sheet — live codes you can scratch and scan yourself. We post it anywhere in India, free.

Print one batch and scan it yourself.

The fastest way to judge this is a sheet of real labels and a phone.

Book a demoTalk to us

Trust, made visible.

connect@avrascan.com · +91 91737 47583 · Navacara Infotech, Ahmedabad, Gujarat, India