Publish structured product facts.
Model, GTIN, manufacturer, country, composition, material origins, recycled content, substances of concern, certifications, technical performance, durability and environmental footprint.
Create a maintained digital passport for each model, issue serialized QR identities in production-scale batches, and update product, service, warranty and end-of-life information without relabeling inventory.
Care · Repair · Warranty · Recycling
A QR is the doorway. QRalto manages the changing product record, serialized identity and operational signals behind it.
Model, GTIN, manufacturer, country, composition, material origins, recycled content, substances of concern, certifications, technical performance, durability and environmental footprint.
Queue up to 100,000 unit identities per batch. Resumable 1,000-unit chunks protect the web request and support horizontal workers.
Each saved content update creates a numbered snapshot, changed-field summary and hash link to the prior revision. The printed QR continues to open the current record and its visible history.
Record distribution, sale, warranty activation, service, repair, recall, recycling and retirement events—with public and internal visibility.
Separate hourly and daily time-series buckets keep identity reporting fast without mixing product scans into campaign analytics.
Model records use revision fingerprints for HTTP revalidation. Serialized scans use no-store responses so current identity state and scan results are always requested.
Digital Product Passport obligations are product- and market-specific. QRalto separates operational capabilities from standards and assurance work that still requires formal validation.
Model, batch and unit identities; machine-readable API data; current-record updates; public revision history; lifecycle events; access-aware event visibility; scan signals and scalable projections.
Material composition and origins, recycled content, substances of concern, care, repair, durability, warranty, recycling, documentation and environmental information.
Select a compliance profile and economic operator, review required information by section, and retain immutable versions and internal operator mandates. Publishing and registry registration remain separate.
Submit a specific passport version for simulated registration and track its status, request history and mock receipt. This does not register a passport with the European Commission.
Product-category delegated-act fields, GS1/ISO interoperability profiles, external registries, conformity evidence and retention duties must be selected and validated for the applicable market.
Field-level stakeholder access, expiring account grants and revision-bound signatures from configured trusted issuers are available. External proof anchoring and physical anti-cloning guarantees are outside this release.
Enter factual product, origin and lifecycle information. The model-level Dynamic QR is created automatically and stays paused in draft.
Publish after required facts are complete, then queue a serialized batch with your batch code, prefix, starting number and quantity.
Download each completed batch as a bounded packaging CSV, or download individual SVG/PNG codes for label and print systems. Tokens are separate from normal campaign QR limits.
Update identity state, warranty and service history while scan events flow through the mediator, outbox and RabbitMQ transport.
QRalto confirms the state of a QRalto-issued digital token and highlights simple velocity or location anomalies. It does not independently certify manufacturer claims or guarantee that the physical label has not been copied or transferred.
The revision chain makes publisher changes visible and internally tamper-evident, but a database operator could rewrite stored history. It is not a manufacturer digital signature, immutable ledger or third-party attestation.
Regulatory requirements vary by product category and market. QRalto provides product-information and lifecycle infrastructure but does not claim completed EU Digital Product Passport compliance.
These visible answers are the same content supplied to the page's FAQ structured data.
A digital product passport is a maintained product information page reached through a physical data carrier such as a QR code. It can present origin, materials, care, repair, warranty, recycling and documentation without replacing the printed carrier.
Yes. Eligible QRalto plans can queue serialized batches of up to 100,000 units. Each unit receives a stable serial number and a non-sequential public token for packaging and label workflows.
The same model and unit QR codes resolve to the latest published product record. QRalto creates numbered, hash-linked snapshots and exposes published revision history, affected fields and before/after previews on the scan page.
Yes, but model passport responses use revision-based ETags and require revalidation so an unchanged record is efficient while a new revision is returned after an update. Serialized unit scan pages are not cached because identity state and scan results must remain current.
No. QRalto can confirm that a digital token exists, report its state and history, and flag simple scan anomalies. A QR label can still be copied or moved, so brands should combine digital identity with suitable physical security and investigation processes.
Select a compliance profile and economic operator to see required information, optional improvements and readiness by section. QRalto keeps immutable versions and internal operator mandates alongside the existing publication and audit history.
No. TEST / MOCK registry registration is a simulation. It records a version-specific submission and mock receipt for testing registration and updates. It does not contact the European Commission or establish regulatory compliance.
No. QRalto provides lifecycle-oriented product information and serialized data-carrier infrastructure. Formal regulatory applicability, required data fields, standards, evidence and operating controls must be assessed for each product category and market.
Create the model, review the public view, then test a small serialized batch.