01Missing field
Manufacturer sees the DPP gap
Required product data is identified inside the DPP workflow, with ownership, domain, and status visible before a passport is published.
DPP portal, completeness checks, gap states
Architecture proof
Supplier evidence becomes passport data through one controlled operating layer.
Redy is not a static DPP page generator. It connects manufacturer requests, supplier evidence, approvals, version snapshots, APIs, and passport outputs so teams can show how a field became publishable.
DPP evidence flow
manufacturer -> supplier -> Redy trust layer -> passport
Missing field
Manufacturer sees the DPP gap
DPP portal, completeness checks, gap states
Request
Redy creates a scoped supplier request
Supplier request records, role-scoped links
Evidence
Supplier submits reusable records
Supplier workspace, records, certifications
Approval
Claims are reviewed before publication
Review states, field provenance, audit log
Output
Versioned, audit-ready DPP data that can move through portals, APIs, exports, webhooks, and passport views.
The flow, end to end
From missing field to published passport.
01Detected
Missing
A required passport field has no trusted value yet.
02Manufacturer
Requested
The gap becomes a scoped supplier evidence request.
03Supplier
Submitted
The supplier attaches source documents and values.
04Reviewer
Approved
A reviewer commits the value from the evidence.
05System
Versioned
The approved claim becomes an immutable record.
06Output
Published
Feeds passport views, APIs, exports, and resolvers.
Operating loop
The core loop is simple enough to inspect and strict enough to audit.
02Request
Redy creates a scoped supplier request
The manufacturer asks for exactly the missing evidence, not another spreadsheet thread or open-ended email chase.
Supplier request records, role-scoped links
03Evidence
Supplier submits reusable records
Suppliers respond in a focused workspace, attach source documents, and build an evidence library they can reuse across requests.
Supplier workspace, records, certifications
04Approval
Claims are reviewed before publication
Manufacturers approve or reject evidence. Accepted fields keep provenance, source context, and audit attribution.
Review states, field provenance, audit log
05Version
Redy snapshots the passport state
Published changes create version history so teams can explain what changed, when, and why.
Version rows, CAS writes, signed records
06Publish
Outputs move through APIs and passport views
The same approved data can feed passport views, exports, webhooks, and resolver-ready patterns.
B2B APIs, exports, webhooks, passport pages
System layers
A workflow architecture, not a single passport page.
Each layer has a job. People use portals, evidence is governed, trust state is recorded, and integrations move the approved data outward.
Workspace layer
Where people do the work
- Manufacturer DPP portal
- Supplier response workspace
- Consumer passport view
Evidence layer
Where supplier data becomes reusable
- Data requests
- Supplier records
- Certifications and component evidence
- Supplier-controlled grants
Trust layer
Where claims become defensible
- Role-based access
- Review and approval states
- Version snapshots
- Audit trail and signing posture
Integration layer
Where Redy connects outward
- B2B API keys and scopes
- Supplier-platform API
- Imports, exports, and webhooks
- Resolver-ready output patterns
Built proof
The page can point to real product surfaces.
This is the credibility page for buyers who want to know what exists behind the pitch. It separates shipped surfaces from standards posture and future route depth.
Manufacturer portal
Self-service DPP creation, draft updates, publishing, revocation, batch import, export, and team controls.
Supplier evidence workflow
Supplier requests, responses, reusable records, certification evidence, and free supplier participation.
Versioned passport records
Published updates create snapshots with concurrency guards, audit records, and provenance-safe field views.
Controlled API surfaces
DPP and supplier-platform APIs use scoped keys, lane separation, idempotency, throttling, and org capability checks.
Agent-ready controls
Assistant workflows are routed through scoped consent, preview, confirmation, and revocable access patterns.
Standards-aligned output
Redy is designed around ESPR-aware DPP records, domain-specific regulation workflows, GS1 Digital Link patterns, and W3C VC signing posture.
Interfaces
Different users, same governed data model.
Portal
Human workflow
- Request missing fields
- Approve supplier evidence
- Publish versioned DPPs
API
System workflow
- Create and update DPPs
- Export supplier-platform data
- Receive webhooks
Agent
Assistant workflow
- Parse source documents
- Preview proposed records
- Commit with scoped consent
Passport
Downstream workflow
- View published data
- Show provenance-safe fields
- Support scan and claim experiences
Use the homepage for the story. Use architecture for proof.
The next depth pages branch from here: the detailed evidence chain, trust and security, domain readiness, supplier evidence APIs, and agent-assisted evidence work.