Serial number and QR traceability for UK manufacturers

Short answer: Give every unit a unique serial number linked to its product model and production batch, print it in a QR code (ideally using the GS1 Digital Link format), and record each event in its life: manufacture, shipment, sale, warranty start and every service visit. This lets you handle warranty claims and recalls quickly, spot counterfeits, and connect each unit to the technical documentation you must keep for UKCA or CE-marked products. If you record end-customer details, UK GDPR applies.

Last reviewed: 3 November 2026

Why serial-level traceability matters

Batch-level records tell you which production run a product came from. Serial-level records tell you exactly which unit went where. That difference drives four practical benefits:

• Warranty claims. You can confirm the exact build date, shipment date and warranty start for a unit, rather than relying on the customer's receipt.
• Recalls and corrective actions. GOV.UK guidance says that if a manufacturer finds a product is a safety risk, it "must contact all the consumers it knows are affected" [2]. Knowing which serials are affected, and where they went, narrows the scope and speeds up contact. GOV.UK also points businesses to PAS 7100:2022, the code of practice on product recall and other corrective actions [3].
• Counterfeit and grey-market detection. A serial that has already been registered, or that was shipped to a different market, is a warning sign.
• Service history. Engineers can scan a unit and see previous faults, parts replaced and firmware versions before they start work.

GOV.UK also states that businesses must keep records of their suppliers "to allow their origins to be traced", and manufacturers and importers must keep technical documentation demonstrating compliance [2].

A practical data model

Keep the model simple. Most manufacturers need these entities:

Two design rules save trouble later:

1. Serials are never reused. Not after scrap, not after rework.
2. Events are appended, not overwritten. Keep a timestamped history rather than a single "current status" field.

QR codes and GS1 Digital Link

A plain QR code can hold any text, including just a serial number. The GS1 Digital Link standard goes further: it represents GS1 identification keys within a web address, so one code can be both a product identifier and a link to information [4][5].

A GS1 Digital Link URI with a product number (GTIN, application identifier 01), batch or lot (10) and serial number (21) looks like this [5]:

https://example.com/01/09520123456788/10/ABC123/21/12345

Points to note from the URI Syntax standard [5]:

• The URI "can be constructed in any domain name", so you can use your own website domain.
• The GTIN comes first, followed by qualifiers in a fixed order: batch/lot must come before serial.
• The current URI Syntax standard is Release 1.7.0, dated August 2026.

GS1 is a network of local not-for-profit member organisations that maintains barcode standards, including the GTIN [6]. The UK member organisation is GS1 UK; check its current guidance on GTINs and GS1 Digital Link QR codes before printing codes at scale.

Practical tips:

• Print quality: test codes on the actual label material and surface finish, at the scanning distance your users will have.
• Placement: put the code where it survives use and is visible after installation.
• Landing page: the link can route differently for a customer (manual, registration), an engineer (service history, after login) and your warehouse (scan-to-ship).
• Human-readable fallback: print the serial in text near the code.

UKCA, CE and record-keeping

Rules have changed several times since 2021, so check GOV.UK before relying on any summary. As of the guidance last updated on 21 August 2026 [1]:

• CE marking continues to be recognised for placing many products on the Great Britain market, alongside or instead of UKCA, under the Product Safety and Metrology (Amendment) Regulations 2024. The page covers more than 20 product types; check the sector regulations for your product.
• UKCA marking may be placed on a label or accompanying document until 31 December 2027, as well as on the product itself.
• Northern Ireland has separate rules, covered in a separate guide.
• Technical documentation must be prepared and is typically kept for 10 years after each individual product is placed on the Great Britain market, unless the sector regulations specify a different period.
• Manufacturer and importer details (name, trade name or mark, postal address) must be shown on the product, or on packaging or an accompanying document where that is not possible.

Serial-level traceability does not replace the technical file, but it helps you answer questions such as: which version of the Declaration of Conformity applied to this unit? Which component lot and test results go with it? When was it placed on the market, and so how long must its records be kept? Link each serial to the design revision and the technical file version in force at build.

Privacy: UK GDPR

Product and batch data is not personal data. Customer names, email addresses, phone numbers and installation addresses of individuals are. If you capture them through warranty registration or service visits:

• Collect only what you need for warranty and safety contact.
• Tell customers what you collect and why, at the point of registration.
• Decide how long you keep it; product records may need to outlast customer contact details.
• Restrict access by role (for example, distributors see their own customers only).
• Consider whether a data protection impact assessment is needed. Under Article 35 UK GDPR, one is required where processing is likely to result in a high risk to individuals [7]. Large-scale location or behaviour tracking through connected products deserves particular care.

Implementation steps

1. Define scope. Which product lines, from which date, and which events matter (build, test, ship, sell, register, service, return).
2. Agree identifiers. Serial format, whether you use GTINs, and how batches link to component lots.
3. Capture at source. Generate serials and print labels at the production line; scan at test and dispatch so data is not keyed in later.
4. Integrate. Connect order, production and shipping data from your ERP or spreadsheets so each shipment lists its serials.
5. Set warranty rules. Define the start trigger and term per product, and how registrations override ship dates.
6. Give access. Service engineers, distributors and customers each need a different view.
7. Test a recall. Pick a component lot and see how quickly you can list every affected serial and its owner. PAS 7100 recommends preparing for incidents in advance [3].
8. Review. Check data completeness monthly at first (scans missed, serials without shipment records).

Readiness checklist

• Unique serial per unit, never reused
• Serial linked to batch, component lots and design revision
• Scan at dispatch recorded against shipment
• Warranty start rule documented
• Customer data collection covered by privacy notice
• Technical file version linked to each build period
• Recall exercise completed and timed

Build or buy?

Whichever route you choose, insist on being able to export all serial and event data in a standard format.

Platforms for traceability

TechLinkAI's Product Lifecycle Platform is designed to follow every product from factory to customer: shipments, warranty and service in one dashboard. According to the product page, it tracks each physical product by serial number and QR code from manufacture and links orders, shipments, warranty and service records [8].

FAQ

Do we need GS1 barcodes, or can we use our own QR codes? You can encode your own serials in a plain QR code. GS1 Digital Link uses a standard structure that combines a GTIN, batch and serial in a web address [5], which helps if retailers or partners already use GS1 identifiers.

Is CE marking still accepted in Great Britain? For many product types, yes. GOV.UK guidance states the UK continues to recognise CE marking alongside UKCA [1]. Check the sector regulations for your product, and Northern Ireland rules separately.

How long should we keep product records? Technical documentation is typically kept for 10 years after each product is placed on the GB market, unless sector rules differ [1]. Keeping serial records for at least as long is sensible.

Is a serial number personal data? Not on its own. It can become personal data when linked to an identifiable individual, such as through warranty registration.

When should warranty start? Common triggers are ship date, sale date or registration date. Choose one, state it in your terms, and record it per serial.

Can we trace units already in the field? Partly. Use shipment and invoice records to back-fill where possible, and capture serials during service visits.

Sources

1. GOV.UK, Placing UKCA or CE marked products on the market in Great Britain
2. GOV.UK, Product safety advice for businesses
3. GOV.UK, Product recalls and alerts
4. GS1, GS1 Digital Link standards
5. GS1, GS1 Digital Link Standard: URI Syntax, Release 1.7.0
6. Wikipedia, GS1
7. UK GDPR, Article 35: Data protection impact assessment (legislation.gov.uk)
8. TechLinkAI, Product Lifecycle Platform