Veribl logo

Publishing passports

Publishing turns a product's passport data into a public page that anyone can open from the product's QR code. Each publish is saved as a numbered version. This article is for the people who prepare and release passports.

Before you publish

Open a product under Passports. The product page has tabs on the left:

  • Checklist — the rules that apply and every item as done or not done, plus the Public passport card where you publish
  • Materials & Substances, Environmental, Certifications, Circularity — the data shown in the passport
  • Battery passport and Batteries — only for products with the battery rule
  • EU registry, Batches, Languages

The only hard requirement to publish is a valid GTIN (the number under the barcode). The passport's public address is built from it. Enter it on the Checklist tab. If required items are still missing, Veribl warns you but lets you publish anyway. You can add them in a later version.

Publish a passport

  1. On the Checklist tab, find the Public passport card.
  2. Click Preview changes to see the passport before it goes live.
  3. Click Publish passport.
  4. Optionally describe What changed?, then click Publish.

The card shows Not published, Version N live, or Version N live · changes not published. After the first publish the button reads Publish changes and is only active when something changed.

Every version stays in the Version history with its date, who published it, and its readiness percentage. Click View to open an older version. The QR code always shows the latest one.

Where the passport lives

  • Public page: /01/{GTIN} on your product page domain, for example go.veribl.com/01/04006381333931. This is a GS1 Digital Link.
  • Machine-readable data: /api/dpp/{GTIN} returns the same passport as JSON-LD (schema.org and GS1). The Public passport card links to it as Machine-readable (JSON-LD).
  • Restricted data: some fields, such as detailed composition or test reports for batteries, only appear to people you gave access. See Passport access.

The GTIN locks after publishing

Printed QR codes open the passport through the GTIN, so once a passport is published the product's GTIN is shown as locked. If the GTIN is wrong, copy the product, give the copy the right GTIN and publish its passport.

Products stay online

Published passports are meant to outlive the product record:

  • If you delete a product that has a published passport, Veribl archives it instead. Its passport stays online.
  • Archiving a product, or changing your plan, does not take a published passport down.
  • Veribl's Terms of Service commit to keeping published versions at their public address for at least 10 years after the latest version was published, even if you move to the free plan, cancel or close your account. You can download a copy of all published passports at any time.
  • A battery with a public passport cannot be deleted.

Use Download backup on the Passports overview to keep your own JSON copy of every published version.

Batches

A batch can have its own QR code. Open the Batches tab, click Add a batch, and enter the batch number (up to 20 letters, digits, -, . or _). Optionally add a production date, a manufacturing site and a public note.

The batch opens at /01/{GTIN}/10/{batch number}: the published passport plus the batch's details. Batch details show as soon as you save them and are not part of a published version. Download the QR code as PNG or SVG. Batches need a published passport first.

Languages

The Languages tab shows which languages the public passport is available in and how much of its text is translated. The languages come from Settings › Languages.

  • Click Translate missing texts to translate automatically. Automatic translations are labelled as such on the passport.
  • Under Review translations, edit a translation and click Save to mark it as reviewed.

Changes show after you publish a new version. Until then visitors see the published text.

Signed versions

Each published version is signed by Veribl: its content is fingerprinted, linked to the version before it, and signed. This shows who published what and when, and that it has not changed since. It does not prove that the content is true; you remain responsible for what your passport says. A signed version shows Signed in the history.

Anyone can check a passport at veribl.com/verify by entering the product number (GTIN), and a serial number for a single battery. The Public passport card also links to Check the signatures.

Tip: Write a short note on each publish. It makes the version history useful when someone asks what changed.

More ways to get help

  • Support

    Can't find the answer? Send us your question and the product or page it's about.

    Contact support
  • Specialists

    Get hands-on help with setup, migrating manuals, or designing your product pages.

    Book a call
  • Enterprise

    Dedicated onboarding, custom integrations, and regulatory guidance for large teams.

    Contact enterprise