Find
See what is missing before the deadline becomes the project.
Map DPP fields by product group, identify what your internal systems already know, and expose the supplier-held evidence still required.
Manufacturer DPP operations
Publish audit-ready DPPs without chasing supplier evidence.
Redy gives manufacturers a governed operating layer for Digital Product Passports: find missing fields, request supplier evidence, approve claims, and publish versioned passport records.
Manufacturer operations board
gap -> request -> approval -> version -> output
DPP gaps
Visible
Required fields are tracked before publication so teams know which claims still need evidence.
Supplier requests
Scoped
Manufacturers ask for the exact evidence needed for a product, field set, and passport version.
Publication
Versioned
Approved values can become controlled DPP versions with provenance and audit context.
Authority
Org-gated
Issuer actions stay with manufacturer workspaces that are allowed to create and publish DPPs.
See it in the product
The manufacturer DPP console.
Where a passport lives after publication: the resolver link and QR shoppers scan, product details, version state, and an advisory compliance check — with supplier evidence requests one tab away.
The manufacturer console for a published passport: resolver URL, QR code, product details, version state, and the advisory compliance check.
Operating model
The manufacturer job is to turn incomplete product data into publishable claims.
Redy keeps that work visible and governed across teams, suppliers, systems, and passport versions.
Request
Turn missing fields into supplier asks.
Send targeted requests with product context, field requirements, source-document expectations, and response state instead of spreadsheet threads.
Approve
Review claims before they become passport data.
Accepted supplier values keep source context, decision state, and audit attribution so the published DPP can be explained later.
Publish
Move approved evidence through controlled outputs.
Use the same approved data in passport views, exports, webhooks, APIs, and resolver-ready implementation patterns.
Evidence workflow
A business workflow that auditors can inspect.
01Draft DPP
Create or import DPP draft
Start from product data, ERP/PLM/PIM inputs, imports, or API-created records.
02Evidence gaps
Detect supplier-held fields
Separate manufacturer-owned values from claims that require supplier declarations, certificates, or source evidence.
03Supplier requests
Request supplier evidence
Invite suppliers into scoped response workspaces where they can attach evidence and approve sharing grants.
04Approved field set
Review and approve claims
Manufacturer teams approve, reject, or request changes before claims become publishable passport data.
05DPP v1.0
Publish a versioned passport
Publication creates a controlled version with audit context, provenance, and downstream output paths.
Integrations
Keep product systems in place. Add the DPP operating layer around them.
Manufacturers should not have to replace ERP, PLM, PIM, LCA, or certification systems to start DPP operations. Redy connects the evidence workflow around those sources.
Product systems
ERPPLMPIMMDMSKU catalogs
Evidence systems
LCA and EPD dataCertification providersSupplier portalsDocument stores
Output systems
APIsWebhooksExportsQR and labeling workflowsPassport pages
Sandbox to live
Build in test mode now. Go live the moment certification lands.
Build your entire issuance pipeline and author your passports in test mode. When certification lands, your integration flips with one key change and your authored data -- including your GTIN -- carries straight into live issuance; only the seal is newly minted. No re-integration, no re-authoring.
This is a copy-forward, not an upgrade: a test passport never becomes certified in place. Promoting to live re-runs real GTIN validation, resolver-identity checks, and registry submission for the first time -- sandbox success does not guarantee live success.
What carries forward
- Your authored passport data and fields
- Your GTIN and product identifiers
- Supplier evidence and approvals already collected
- Your integration -- the same API calls, under a new live key
What's newly minted at go-live
- The qualified e-seal
- Live GTIN validation and resolver registration
- Timestamp and EU registry submission
Rollout checklist
Scope the program before picking the passport surface.
A credible DPP rollout starts with products, fields, suppliers, systems, approvals, and output requirements. Redy gives those decisions a workflow.
Product group and field map
Supplier segmentation
Evidence request templates
Integration surface list
Approval owners
Publishing and revocation rules
Security and procurement review
Launch pricing scope
Start with the manufacturer workflow, then invite suppliers into the missing fields.
Supplier response stays free. Manufacturer workspaces control request scope, approval decisions, publication, and integration outputs.
Business FAQ
The page should answer procurement, product, and operations questions.
Is this a DPP page generator?
No. Public passport pages are an output. The business value is the operating workflow that moves missing supplier evidence through request, response, approval, versioning, and publication.
Can suppliers participate without paying?
Yes. Suppliers can respond to DPP requests and share supplier-owned evidence for free. Manufacturers own the commercial publishing workflow.
How does Redy fit with ERP, PLM, or PIM?
Redy should sit beside product systems rather than replace them. Product records, source evidence, imports, APIs, exports, and webhooks keep the DPP workflow connected to existing systems.
Which domains should manufacturers start with?
Start with the product group under the clearest regulatory or customer pressure, then reuse the same evidence workflow across domains such as batteries, textiles, and future ESPR categories.