AVRA product
AVRA Warranty: Purchase Registration
The scan that proves the product registers the purchase — no card, no bill.
01 /Overview
The card nobody posts back.
A brand sells lakhs of units through distribution and learns the name of almost no buyer. The warranty card in the box is filled in by a fraction of a percent of them, the rest is a call to a care desk with a torn invoice and a model number read out over a bad line.
AVRA Warranty uses the scan that is already happening. On a warranty batch, a genuine scan opens a short registration instead of a product page. The buyer verifies a phone number, answers three questions, and the cover is recorded against that exact unit. The code on the label is the serial, so there is no second number to invent and nothing for the buyer to keep.
- questions asked
- 3
- registration per label, enforced
- 1
- PDFs to download or lose
- 0
- every date shown in Indian time
- IST
Registration, end to end
One WhatsApp message. No card to keep.
The buyer scans the label on the box. Warranty batches register only on a genuine verdict. The buyer verifies a phone number by OTP — one phone is one AVRA identity across every brand — and answers three questions: when they bought it, which shop, and the shop pincode. The registration records the serial and an expiry date that is computed once and frozen, and one WhatsApp message confirms it.
Scan
The buyer scans the label on the box.Verdict
Genuine
It registers only on a genuine scan.Phone + OTP
One phone is one identity, across every brand.Three questions
When you bought it, which shop, the shop pincode.Registered
serial 7XK2M9PQ4R
exp 14 Sep 2028
WhatsApp confirmation: one message. There is no card to keep.
The expiry is computed once and frozen — shortening the term next year does not shorten this buyer's.
02 /How it works
The term is on the product. The record is on the unit.
- 1
Set the term once, on the product.
“This model is covered for 24 months” is a property of the model, not of a print run. Set it on the product and every batch of it inherits it. Change it next year and you have changed what you sell going forward — you have not altered any warranty already registered. - 2
Generate a warranty batch.
Same console, same credit, one choice different: what the batch is for. A warranty batch's genuine scan carries a registration form instead of a product page. - 3
The buyer registers in about forty seconds.
Phone number, an OTP over WhatsApp, a consent tick, then purchase date, shop name and shop pincode. The purchase date must be a real day that has already happened. One registration per label, enforced by the database and not by a check in the code — two phones racing the same label cannot both win. - 4
Your care desk gets a searchable book.
Search by serial, by shop, or by the last four digits of a phone number. Filter by “expiring within”. Export it, masked and audited, because a warranty book is a customer list.
Frozen at registration
What the buyer's scan locks in
- The unit — the registration is bound to that label's code, once.
- The purchase date, the shop and the shop pincode, as the buyer typed them.
- The expiry date, computed from the product's term on that day and stored.
What it does not
- Your warranty contract — we record what you already promise, not new cover.
- A future change of term, which applies only to registrations made after it.
- Ownership after a resale: transfer is not built.
What happens if no term is set
Nothing is invented. The purchase is still recorded, because that is what the care desk needs, and the buyer's card says no term set rather than claiming cover the brand never promised.
03 /What your team sees
Type the serial while the customer is on the line.
The whole value of this is a three-second answer. A customer calls, reads the code off the label, and the agent has the purchase date, the shop, the pincode and the expiry date in one row — before the customer has finished explaining what broke.
The warranty book — one example row
| Serial | Product | Phone | Bought | Expires | Shop |
|---|---|---|---|---|---|
| 7XK2M9PQ4R | The product's name | +91******3210 | 14 Sep 2026 | 14 Sep 2028 | The shop the buyer named · 411001 |
Search by serial, by shop, or by the last four digits of a phone number, and filter by “expiring within”. The phone is masked on every staff screen.
The export is a CSV, it masks phone numbers, and every export writes an audit row naming who took it. That is not a feature we are proud of so much as the minimum for a file that is a list of your customers.
04 /What the buyer sees
A phone number, three questions, and a message.
There is no app, no account, no password and no PDF. The confirmation arrives on WhatsApp. If the buyer wants to see their cover later — across every brand they have registered with, not just yours — it is at one page, signed in with the same phone number and an OTP.
One thing worth stating because it surprises people: one phone number is one AVRA identity across every brand on the platform. A buyer who registered a wire coil last year and a mixer grinder this year sees both, and does not verify their number twice. The consent notice says this in those words.
05 /Where it fails
What this does not do.
There is no claims workflow.
No RMA, no service-centre routing, no ticket, no status page for the buyer. A claim is still a phone call to the care number printed on the scan page. What changes is that the agent answering it can see the purchase in three seconds. Building the claims half is a real project and it is not this.
There is no PDF and no download, on purpose.
A card the buyer has to keep is the problem we started with. If your service process requires a document the customer presents, this does not fit it yet.
We do not read invoices.
The purchase date and the shop name are what the buyer types. No OCR, no bill upload, no verification against a dealer's sales record. For a brand that needs the invoice as proof, this records a claim of purchase, not a proof of purchase.
Registration is not transferable.
If the product is resold, the warranty record stays with the phone number that registered it. Ownership transfer is not built.
Every message costs money, including OTPs.
Registration sends at least two WhatsApp messages — the OTP and the confirmation. That is the real variable cost of this line, and it is why messages are billed as they are sent rather than folded into the label. See What it costs.
A buyer who never registers is not worse off.
They have whatever warranty you already give them. Registration is a record, not a condition — unless you choose to make it one, which is your policy decision and not something the platform enforces.
06 /Integration
One field on the product, one choice at the batch.
Set the term on each product. Choose warranty when the batch is generated. That is the whole configuration.
Two things need your team: a WhatsApp Business sender, because the OTP and the confirmation go over WhatsApp and the templates have to be approved under your number, and a decision about what the care desk does with the book. There is no ERP connector and no CRM sync; the export is a file.
07 /What it costs
The label, plus the messages that actually go out.
The label costs one credit, at the same rate as any other label. What warranty adds is messages, and messages are the one genuinely variable cost in this product: an OTP and a confirmation per registration.
They are billed at Meta's published India rate for WhatsApp, with no markup. An unregistered unit sends no message and costs nothing beyond its credit. From 1 October 2026 Meta also charges for utility messages sent inside an open 24-hour window, and the pass-through follows Meta's rate card.
08 /Questions
Questions.
Do I have to make registration compulsory to get the warranty?
That is your policy and the platform does not enforce it either way. Most brands should not: a warranty conditional on a form is a warranty argument waiting to happen, and the registration rate is high enough without it because the scan is already open in the buyer's hand.
What if the buyer registers on the wrong date, or names the wrong shop?
The date must be a real day in the past, and the pincode must be a real pincode shape, but beyond that it is what the buyer typed. Treat shop name and pincode as good distribution data and weak evidence. That is also why the expiry is computed from the purchase date and then frozen rather than recomputed.
Can two people register the same unit?
No. One registration per label, enforced by a unique index in the database rather than by a check that two simultaneous requests could both pass.
We changed our warranty term from 24 to 18 months. What happens to existing registrations?
Nothing. Every registration's expiry date was computed once and stored. Changing the term changes what future registrations get, and the test suite has a case that proves existing ones do not move.
Can the buyer download a warranty card?
No, and that is deliberate. The record is the point; a file to keep is the old problem with extra steps. If your process needs a document, tell us — it would be a real change, not a setting.
Does this stop fake warranty claims?
It makes them harder in one specific way: a claim on a unit whose code was never issued, or was never activated, or was already registered by someone else, is visible immediately. It does not stop a genuine unit being claimed on dishonestly, and it is not a fraud engine.
Which phone number is this tied to?
The buyer's, verified by OTP. One phone number is one identity across every brand on AVRA, so a buyer sees all their registrations in one place. A buyer who changes their number loses access to the old registrations; your book still has them, and your care desk can still find the unit by its serial.
Is this a separate label from my authenticity label?
It is a separate batch. A warranty batch and an authenticity batch are printed differently and answer differently, so it is decided when the run is generated, not afterwards. A product can have both, on different runs.
Print one batch and scan it yourself.
The fastest way to judge this is a sheet of real labels and a phone.
Trust, made visible.
connect@avrascan.com · +91 91737 47583 · Navacara Infotech, Ahmedabad, Gujarat, India