Minting

Minting Overview

What does minting do?

Minting creates verifiable Digital Product Passport tokens for your products. Each token is a permanent, tamper evident identity tied to a product, either individually serialised or grouped by lot. Once minted, a token resolves through its scan URL to the product’s passport, including any linked localised content.

Who it is for

Brand owners and compliance approvers issuing Digital Product Passports for regulatory compliance, supply chain transparency or consumer engagement.

Entry points

ScreenPathPurpose
Minting Dashboard/mintView KPIs, batches, tokens, exports and activity
New Mint/mint/newLaunch a new minting request via the guided wizard

How it works

Prerequisites

1

Mint readiness

All required DPP schema fields are populated and the product shows a “Ready to mint” badge in the Product Library.

2

Active commercial status

The product carries a valid commercial status.
3

Passport configuration

The brand has a published passport template governing content disclosure.

4

Production batch (optional)

A production batch may be linked for ERP level quantity enforcement. Omit it to mint without ERP constraints.

Minting wizard

The wizard at /mint/new uses progressive disclosure:

  1. Select SKU. Search and select a product from your catalogue.
  2. Production run (optional). Link to an ERP synced production run.
  3. Mint configuration. Choose identity mode, activation mode, quantity and optional lot details.
  4. Review and submit. The platform validates eligibility and submits the request.

Identity mode

ModeDescription
SerialOne token per individual unit. Each unit receives a unique resolver URL and optional serial number.
LotMint lots with quantities. Individual unit tokens are created within each lot.

Activation mode

Activation is a deliberate control over when a passport becomes live. There are two modes.

ModeDescriptionWhen you would choose this
Activated at mintThe passport is live the moment the token is issued.Codes are applied to finished goods already cleared for sale, or you want passports live for QA and print checks.
Manual activationThe token is issued inactive and activated later by the brand.You want the passport to go live at packing, shipping or point of sale, so unsold stock stays dormant.

Execution

After submission, minting runs asynchronously:

  • Tokens are generated in high throughput processing cycles.
  • Large jobs complete automatically in the background, with no user action required after submission.
  • In progress jobs are resumed to completion by the background worker even if you navigate away.
  • Failed jobs are retried a limited number of times before being marked as terminal failures.

Minting dashboard

The dashboard at /mint is organised into four tabs.

Batches

Lists mint batches with status, quantity progress, identity mode and activation mode. Each batch links to a detail view at /mint/batch/:id showing metadata and, for serial mode batches, a paginated list of individual tokens.

Batch status progression: queued → processing → minted (or failed)

Tokens

A paginated list of minted tokens across batches. Each token shows its serial number where applicable, status, resolver URL and creation date. Selecting a token opens a preview panel with detailed token information and a scannable QR code encoding the resolver URL.

Token lifecycle: minted → active → revoked

For GS1 ready brands, tokens carry GTIN and serial identifiers. For non-GS1 brands, the token’s internal ID serves as the resolver identifier.

Exports and print jobs

Shows generated payload packs (CSV manifests) for completed batches. Each pack contains resolver URLs and token metadata for printing, labelling or integration with downstream systems.

  • Download. Each pack download uses a short lived signed URL.
  • Pack size. Large batches produce multiple sequential packs.
  • Resume. If an export is interrupted, selecting “Export / Download” again resumes where it stopped.
  • Concurrency. A soft lock prevents parallel generation for the same batch.

Activity and audit

A chronological event log for minting operations, filterable by entity type. It covers job creation, batch status transitions and unit level events.

Dashboard KPIs

  • Total tokens minted. Aggregate count of minted tokens.
  • Active tokens. Tokens currently in active status.
  • Batches created. Total number of mint batches.
  • Exported or printed. Count of completed export jobs.

KPIs refresh automatically while batches are in progress.

Scan resolution

When a token’s resolver URL is scanned:

  • The resolver identifies the product and returns the passport destination for the identifier.
  • The passport renders with the brand’s presentation and any linked Market Pack content for the consumer’s market.
  • Scan telemetry is captured with coarse geolocation and user agent metadata. Scanning requires no consumer account and builds no personal profile.
  • Bot traffic is detected and served static responses without triggering telemetry.