# QR codes for warranty registration

> Put the unit's serial number in the QR code's URL as a query parameter, so scanning opens a registration form with the product and serial already filled in. Registration friction comes almost entirely from typing; a prefilled form reduces the ask to name and email. Be transparent that registration is data collection.

Source: https://useqr.app/docs/ecommerce/qr-code-for-warranty-registration · Last reviewed 2026-08-21 · UseQR is free forever, no signup.

---

## Why registration cards fail

The traditional warranty card asks the customer to find a pen, copy a 14-character serial
number off a sticker on the underside of the product, and post the card or retype
everything into a website. Every step loses people. The product works, the box is in the
recycling, and the card goes with it.

A QR code fixes exactly the expensive part: **the typing**. The code on the product or the
quick-start insert carries the serial, so the landing form arrives already knowing which
unit it is:

```
https://example.com/register?sku=KT-200&sn=A1B2C3D4E5
```

What remains for the customer is name and email, one field each. That is the entire
mechanism, and it is worth doing properly because everything downstream (recalls, support,
proof of purchase disputes) depends on the registration actually happening.

## Generating per-unit codes

Because the serial is in the URL, every unit needs its own code. Three routes, by scale:

- **Dozens**: the [bulk generator](/bulk) with a pasted list, or
  [a spreadsheet workflow](/docs/how-to/how-to-make-qr-codes-from-a-spreadsheet).
- **Thousands**: `POST /api/v1/qr/batch`, **up to 1,000 codes per request**, no API key.
- **Production lines**: generate at labelling time from your MES; the
  [serialisation guide](/docs/ecommerce/qr-code-for-serialized-products) covers the data
  model, including why serials should be opaque rather than sequential.

Print the code **≥ 2 × 2 cm** on the quick-start insert or the product itself, not only
on the outer box, which is discarded first. Label it: "Scan to register your warranty".
A bare code registers nothing.

## What each side gets

Be clear-eyed about the exchange, because your customers increasingly are.

**The buyer gets**: a warranty that is on file without keeping the receipt, direct recall
and safety notifications, and faster support because the agent already knows the unit,
its manufacture date and its firmware.

**The brand gets**: a customer identity attached to a unit, which is to say, **warranty
registration is data collection**. Say so on the form, plainly: what you collect, what it
is used for, and a checkbox (unticked) for marketing that is separate from the
registration itself. A form that buries marketing consent inside the warranty flow
converts worse over time and, in many jurisdictions, is not lawful consent anyway.

Worth knowing: in most markets, statutory consumer rights and typically the manufacturer's
warranty itself apply **whether or not the product is registered**. Registration is
evidence and convenience, not a precondition, a form implying otherwise is the kind of
dark pattern that gets screenshotted.

## Placement and companions

The registration code competes with other calls to action, and
[insert cards work best with exactly one](/docs/ecommerce/qr-code-in-the-unboxing-experience).
If registration matters most (and for anything with a recall risk it does) give it the
card. For products sold on marketplaces, registration and support links are among the uses
that stay on the right side of
[Amazon's insert policies](/docs/ecommerce/qr-code-for-amazon-sellers), unlike review
solicitation.

Point the URL at a path you will maintain for the product's service life, per the
[packaging permanence rules](/docs/ecommerce/qr-codes-on-product-packaging), and
[verify a printed sample decodes](/validate) before the production run.

## FAQ

### How does a warranty registration QR code work?
The code carries a URL with the product model and serial number as query parameters. Scanning opens the registration form with those fields prefilled, so the customer only enters contact details. Each unit needs its own code, generated in bulk.

### Do customers have to register to keep their warranty?
In most markets, no. Statutory rights and typically the manufacturer's warranty apply regardless. Registration provides evidence, enables recall notifications and speeds up support, but forms should not imply the warranty is void without it.

### How do I generate a different QR code for every serial number?
From a spreadsheet of serials, use a bulk generator to produce one code per row, or call a batch API (UseQR's accepts up to 1,000 items per request without a key), and merge the images into your labelling workflow.

### Where should the registration QR code go?
On the quick-start insert or the product itself, at 2 × 2 cm or larger with a clear label. Avoid relying on the outer carton alone, because packaging is discarded before many owners think about registration.

## Try it

- https://useqr.app/url
- https://useqr.app/bulk
- https://useqr.app/validate