01
Map missing DPP fields
Import or create product records, then separate manufacturer-owned data from supplier-held evidence requirements.
DPP workflow features
Features that move supplier evidence into audit-ready DPPs.
Redy is built around the work behind every credible Digital Product Passport: missing fields, supplier evidence, review decisions, provenance, versioned publication, and system outputs.
Evidence operating board
request -> review -> approve -> publish
Field gaps
tracked
Supplier requests
scoped
Claims
approved
DPP versions
published
Claim packageready for review
Source attached
Supplier grant
Audit trail
See it in the product
One workspace, the whole evidence workflow.
The DPP creation workflow's completeness review: a field checklist and completeness bar showing exactly what is present and what is still missing before publication.
Workflow backbone
The feature set follows the evidence path.
Redy is not a pile of disconnected modules. Each feature exists to move data from uncertainty to approved, explainable passport claims.
02
Request supplier evidence
Send suppliers focused requests with product context, field requirements, attachments, and due dates.
03
Extract and normalize responses
Use AI-assisted extraction for certificates, declarations, and LCA attachments while keeping reviewer control.
04
Approve publishable claims
Review values, source documents, confidence, supplier grants, and audit context before data enters a passport.
05
Publish versioned outputs
Move approved claims into DPP views, APIs, webhooks, exports, and resolver-ready records with provenance attached.
Capabilities
Product features for the teams that actually run DPP operations.
Readiness
DPP gap detection
Track required fields by product group, product record, supplier, and passport version so missing evidence is visible before publication.
Product field mapEvidence ownershipReadiness status
Requests
Supplier evidence workflow
Convert missing fields into scoped supplier requests instead of email threads and spreadsheet tabs.
Request templatesSupplier workspaceDue-date state
Evidence
Document and source intake
Collect declarations, certificates, audit letters, LCA extracts, and structured values with source context intact.
AttachmentsSource metadataReusable records
AI
Human-reviewed extraction
Use AI to accelerate evidence parsing while keeping confidence, source text, and reviewer decisions visible.
OCR and extractionConfidence signalsReviewer approval
Governance
Claim approval controls
Approve, reject, request changes, and preserve who made each decision before any value becomes passport data.
Decision logRole-aware reviewChange requests
Trust
Audit trail and provenance
Keep actor, timestamp, evidence, grant, version, and source context attached to every approved claim.
Actor attributionVersion historySource evidence
Publication
Versioned DPP publishing
Publish controlled passport versions and keep downstream surfaces aligned as records change.
Draft to publishedRevocation pathOutput sync
Platform
APIs, webhooks, and exports
Connect the evidence workflow to product systems, supplier portals, analytics, and resolver implementation paths.
REST APIsWebhooksCSV and JSON exports
Reuse
Supplier-controlled reuse
Let suppliers respond once and reuse approved evidence across requests with permission and context attached.
Free supplier responseGrant controlsCross-request reuse
Workspace fit
Different teams see the same evidence record from their own lane.
Manufacturers, suppliers, compliance reviewers, and IT teams should not fight over separate copies of the same DPP data. Redy keeps one workflow with role-aware surfaces.
Manufacturer
Owns readiness, review, approval, publication, revocation, and DPP issuer actions.
DPP field mapSupplier requestsClaim approvalVersioned publish
Supplier
Responds to scoped requests, attaches evidence, reviews extracted values, and controls reuse grants.
Request inboxEvidence uploadAI reviewReusable records
Compliance and audit
Reviews source evidence, decision state, actor attribution, version history, and published outputs.
Audit trailEvidence lineageApproval stateExportable records
IT and data
Connects Redy to product systems, supplier data sources, exports, webhooks, and resolver paths.
APIsWebhooksImportsAccess controls
AI controls
AI helps parse evidence. It does not replace approval.
DPP teams need speed, but they also need defensible decisions. Redy treats AI as an assistive layer inside a governed review workflow.
See AI detailsExtraction review
Recycled material percentage
41%
Extracted from supplier declaration, pending manufacturer approval.
Source documents remain attached to extracted values.
Confidence is visible before reviewer approval.
AI suggestions do not publish without human decision state.
Structured values keep evidence, actor, grant, and version context.
Integrations
Built to sit between source systems and DPP outputs.
Redy should not force a manufacturer to replace product systems. The feature set connects around those systems and keeps the DPP workflow explainable.
Inputs
ERPPLMPIMLCA dataSupplier documentsCertificate providers
Workflow
RequestsEvidenceAI extractionApprovalsAudit logVersions
Outputs
DPP viewsAPIsWebhooksExportsQR flowsResolver-ready records
Feature FAQ
Feature questions should reinforce the workflow story.
Are these consumer app features?
No. The consumer view is only one output. This page focuses on the operational features manufacturers and suppliers need before a passport can be trusted.
Can suppliers use Redy without paying?
Yes. Supplier response is free. Manufacturers pay for the governed workflow that controls readiness, approvals, publication, integrations, and reporting.
Does AI approve DPP claims automatically?
No. AI can extract and normalize evidence, but Redy keeps confidence, source context, and reviewer approval state visible before publication.
How does this support multiple DPP domains?
The evidence workflow is domain-flexible: request evidence, review claims, preserve provenance, and publish versioned outputs as official schemas mature.
Start with the evidence workflow, then choose the launch scope.
Supplier response stays free. Manufacturer workspaces control approval, publication, integrations, and audit-ready outputs.