Minting Overview

What Minting Does

Minting is the process of creating verifiable Digital Product Passport (DPP) tokens for your products. Each minted token is a permanent, tamper-evident identity tied to a product — individually serialised or grouped by lot. Once minted, tokens can be scanned via resolver URLs to access the product’s passport data, including any linked localised content.

Who It’s For

Brand owners and compliance approvers who need to issue Digital Product Passports for regulatory compliance, supply chain transparency, or consumer engagement.

Entry Points

How It Works

Prerequisites

Before a product can be minted it must meet the following conditions:

1. Mint readiness — all required DPP schema fields must be populated (the product shows a “Ready to mint” badge in the Product Library).
2. Active commercial status — the product must have a valid commercial status.
3. Passport configuration — the brand must have a published passport template governing content disclosure.
4. Production batch (optional) — a production batch may be associated for ERP-level quantity enforcement. If omitted, minting proceeds 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) — optionally link to an ERP-synced production run.
3. Mint Configuration — choose identity mode, activation mode, quantity, and optional lot details.
4. Review & Submit — the system validates eligibility and submits the request.

Supported Modes

Identity Mode

Activation Mode

Execution

After submission, minting executes asynchronously:

• Tokens are generated in high-throughput processing cycles (up to 20,000 units per cycle).
• Large jobs (e.g., 1,000,000 units) complete automatically in the background — no user action is required after submitting the request.
• In-progress jobs are automatically resumed to completion by the background worker, even if you navigate away.
• Failed jobs are retried up to 3 times before being marked as terminal failures.

Minting Dashboard

The dashboard at /mint is organised into four tabs:

Batches

Lists all 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 all minted tokens across batches. Each token shows its serial number (if applicable), status, resolver URL, and creation date. Clicking a token row opens a right-side preview panel with detailed token information and a scannable QR code encoding the token’s 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 / 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 (5-minute TTL).
• Pack size — each pack contains up to 10,000 units. Batches exceeding 10,000 units produce multiple sequential packs.
• Resume — if export is interrupted, re-clicking “Export / Download” resumes from where it left off.
• Concurrency — a 10-minute soft lock prevents parallel generation for the same batch.

Activity / Audit

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

Dashboard KPIs

Four summary cards at the top of the Minting Dashboard:

• Total Tokens Minted — aggregate count of all minted tokens.
• Active Tokens — tokens currently in active status.
• Batches Created — total number of mint batches.
• Exported / Printed — count of completed export jobs.

KPIs refresh automatically while batches are in progress.

Scan Resolution

Resolver URLs generated during minting are handled at the edge. When a token’s resolver URL is scanned:

• The resolver identifies the product and (if applicable) activates the token on first scan.
• The passport renders with the brand’s theme and any linked Market Pack content for the consumer’s market.
• Scan telemetry is captured with GDPR-safe metadata (truncated IP, coarse geolocation, user agent).
• Bot traffic is detected and served static responses without triggering telemetry.