Many warranty cards are never posted back, and many registration websites ask for a serial number printed in tiny type on the back of an appliance. Connected packaging offers a simpler route: scan the code on the product, confirm a few details, done. Behind that convenience is one idea, unit-level product identity, and a few limits that brands should design around honestly.
From product number to unit identity
A GTIN identifies a product model, the same for every unit of that model. Warranties are about individual units: this water heater, installed on this date, at this address. So warranty registration needs a serial number per unit, combined with the GTIN to form a unit identity. We explain that pairing in GTIN + serial: how an individual product gets its identity.
Put that identity in a QR code, for example as a GS1 Digital Link with the serial in the web address, and the code on the product already knows which unit it is. The buyer no longer has to find and type the serial.
How registration by scan works
Consider Nordline, a fictional maker of electric water heaters. Each heater carries a serialized code on its rating plate, and the same code is printed on the carton.
- The buyer or installer scans. The code opens Nordline's registration page with the unit already identified: model, serial and production batch.
- The system checks the unit. Is this serial one Nordline actually made and shipped? Has it already been registered? Is it subject to a recall?
- The buyer adds details. Name and contact details, installation address if needed for service, purchase date and, ideally, a photo of the receipt.
- Nordline confirms. The buyer receives a confirmation tied to that serial, and the record is ready for any future service call.
In GS1 terms, a resolver can offer registration as one of several links for a product; the GS1 Web Vocabulary includes a gs1:registerProduct link type. Links set for the product model can apply to every serial of that model, so Nordline does not need to configure each heater individually.
What a scan proves, and what it does not
A scan of a serialized code shows that someone had access to that code. That is useful, but it is not the same as proof of purchase.
| Question | What the scan can tell you | What else you need |
|---|---|---|
| Which unit is this? | The exact model and serial | Nothing, if the code was correctly printed and checked at the factory |
| Is this a unit we made? | Whether the serial exists in your records | Physical inspection if counterfeits are a concern |
| When was it bought? | Only when it was scanned | A receipt, invoice or retailer sale record |
| Who owns it? | Who registered it | Proof of purchase if ownership is disputed |
| Was it sold in this market? | Where it was registered, compared with where it was shipped | Shipment records and a fair review process |
The last row links warranty to channel monitoring. A water heater registered in a country it was never shipped to may be a grey-market import, or simply a product a family took with them when they moved. How consumer scans can reveal channel and diversion signals explains how to treat such signals.
Registration also connects to authenticity. A serial that has never been made, or one registered twice in different places, deserves a closer look. But a registration check is at most a "known serial" level of assurance; see product verification vs authentication for what each level can and cannot show.
Service history: the long tail of unit identity
Registration is the start, not the end. Once a unit has an identity, every later event can attach to it:
- the installer who fitted it, and when;
- service visits and parts replaced;
- firmware or safety updates applied;
- recall notices that apply to its batch;
- a change of owner when the property is sold.
A technician scanning the rating plate years later sees the unit's history at once, without asking the homeowner for paperwork. A second owner can see that the heater was serviced. This only works if the code is on the product itself and keeps leading somewhere useful long after the launch campaign ends, which is why product identity should outlive the marketing campaign.
Consent and data
The code carries product identity, not personal data. Personal data enters at registration, and it should be handled carefully:
- Ask only for what the warranty needs. Marketing preferences should be a separate, optional choice.
- Explain the purpose before collecting details, and record consent.
- Do not make registration a condition of a warranty that the buyer is entitled to by law. Registration should make service easier, not take rights away.
- Plan for ownership changes. When a product is resold, the old owner's personal data should not pass to the new owner along with the service history.
- Precise location is optional. If an installation address is needed for service, ask for it directly rather than collecting location from the phone silently.