> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://tieback.io/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://tieback.io/docs/_mcp/server.

# Lesson 2: What a Passport Is Not

> Academy Foundations Module 1 Lesson 2: why a QR code, a product web page and a PDF are not Digital Product Passports, and what a carrier-only programme has actually built.

**Module 1, Lesson 2 of 4. About 8 minutes.**

## Orientation

There is a specific failure that recurs in early programmes, and it is expensive because it looks
like success. A team ships QR codes on packaging, the codes scan, they open a page, and the
programme is declared delivered. Nothing in that sequence is a passport, and the gap is only
discovered when someone asks for structured data by attribute.

This lesson is about recognising that failure before you fund it.

Identified, machine readable, and access controlled. If you reached for "digital" or "public", go
back to the Definition section of the canonical article before continuing.

## Learning Objectives

## Three Confusions Worth Naming

**A QR code is a carrier.** It encodes a string, usually a URL. It carries no product data itself,
it has no access control, and it is printed once. A passport is the data, the identifier, the
access rules and the service that delivers them. Confusing the two is not a semantic quibble: it
determines whether you scope a printing exercise or a data programme.

**A product web page is a rendering.** It is one presentation of information, aimed at one
audience, usually the buyer. A passport must serve several audiences with different entitlements
and must be consumable by systems, not only by readers.

**A PDF is a document.** It cannot be queried by attribute, it has no access tiering within one
artefact, and it has no reliable update path once distributed. Those are practical failures, not
formalities: a recycler needs one attribute, not forty pages.

Documents are not banned. They remain legitimate as attachments inside a passport, for example a
declaration or a repair manual. The rule is simply that they cannot be the passport.

#### [What is a Digital Product Passport?](/docs/knowledge-base/digital-product-passports/what-is-a-digital-product-passport)

Read these three sections. The first two carry comparison tables that are worth keeping open in
front of you the next time someone proposes a QR project. The third names the failure patterns
directly.

#### Diagnosing the Aurelia S2 pilot

The S2 team runs a pilot: a QR code is printed on the trimmer housing and resolves to the existing
marketing page, which shows the specification, a manual download and a sustainability statement.
The team reports the passport pilot as complete.

What actually exists: a carrier, and a rendering for one audience.

What does not exist: a persistent identifier distinct from the marketing URL, any structured
representation a system could consume, any separation between what a consumer sees and what a
market surveillance authority may request, any versioning of what was shown on a given date, and
any owner for the battery pack composition data, which sits with the cell supplier and has never
been requested.

The pilot was not worthless. It proved the printing and scanning path. It should be reported as
"carrier proven", which is honest and still useful.

#### Diagnose your own nearest equivalent

Find whatever your organisation currently points a customer to for product information: a page, a
sheet, a portal. Score it against five questions.

1. Is there a persistent identifier that will still resolve after the product is discontinued?
2. Can a system consume the data by attribute without scraping a layout?
3. Do different audiences receive different subsets?
4. Can you reconstruct what was shown on a date last year?
5. Is there a named owner for each attribute?

Count the yes answers. Most organisations score one or two, and that number is the honest starting
position for a plan.

## Knowledge Check

## Takeaways

* A QR code is a carrier: it encodes an address and carries no product data.
* A web page is one rendering for one audience, not an access controlled data set.
* A PDF cannot be queried by attribute, tiered by audience or reliably updated after distribution.
* Documents are legitimate attachments inside a passport.
* A carrier-only pilot should be reported as a carrier-only pilot.

**If you remember one thing:** the easiest component to build is the one people mistake for the
whole thing.

## Sources

[What is a Digital Product Passport?](/docs/knowledge-base/digital-product-passports/what-is-a-digital-product-passport),
sections Digital Product Passport vs QR Code, Digital Product Passport vs PDF, and Why
Organisations Get DPP Projects Wrong.

## Related Docs

* [Lesson 3: The Four Layers](/docs/academy/foundations/module-1/lesson-3)
* [Lesson 1: What a Passport Is in Law](/docs/academy/foundations/module-1/lesson-1)
* [What is a Digital Product Passport?](/docs/knowledge-base/digital-product-passports/what-is-a-digital-product-passport)
* [Glossary: Data Carrier](/docs/knowledge-base/glossary/data-carrier)