Data Carrier Studio
Prepare QR carriers from a passport's stable resolver address, choose an explicit print profile and retain a record of what was generated. The digital symbol and the physical print each have their own checks.
For product, packaging and production teams preparing labels that need a traceable destination and a reproducible print profile.
Carrier generation starts with a published passport and its persistent identifier. The platform checks the resolver host before a production carrier is created, so a local development address does not become a product mark.
Choose the output format, width in millimetres, resolution and QR error-correction level. SVG and PDF support vector output, PNG provides a raster image, and ZPL supports a printer-oriented label workflow.
Generate a carrier in the context of a model, batch reference or individual serial number. An item serial receives a recorded identifier assignment; repeating that serial preserves its existing assignment.
Software decoding checks that the generated symbol resolves to the intended content. A separate human action can record physical verification evidence after printing. The carrier record keeps its profile, encoded address and checksum.
A generated symbol, a successful software decode and a recorded physical verification are separate statuses.
Carrier history keeps the chosen format and print parameters alongside the encoded destination.
Individual serial assignments are stable; their item references resolve to the parent product's published passport data.
A software decode checks the digital file. It cannot certify print quality, durability or suitability for a specific surface or category requirement. Item identifiers currently point to the parent passport; they do not provide independently versioned product data for each individual item.
FAQ
SVG, PNG, PDF and ZPL are available in the carrier workflow. Choose the format and print dimensions for the system that will produce or place the mark.
Carrier generation requires a published passport. This ensures the encoded destination is attached to a record that the public resolver can serve at generation time.
No. Software validation confirms the generated digital symbol decodes correctly. Evidence about the actual printed mark must be recorded separately after a physical check.
A passport connects accepted product information to a stable public address. Passvanta keeps the published revision, the evidence behind it and the publication decision traceable.
Digital Product Passports →Bring requirements, source documents and review decisions into one product workspace. Every missing value or unresolved evidence requirement has a place in the preparation workflow.
Compliance Engine →Use Passvanta's versioned REST API to connect product operations with your existing systems. Organisation scopes, review requirements and publication gates remain part of the integration.
Product Passport API →Open the carrier workspace, choose the passport and specify the print format your production process needs.