What teams ask before they start.
DPP work touches compliance, supplier operations, product data, and IT. These are the first concerns to settle.
Is Redy only for batteries?
No. Battery passports are an early high-urgency use case, but Redy is built as a schema-flexible evidence workflow for many DPP domains.
Is this just a DPP page generator?
No. Public passport pages are an output. Redy coordinates supplier requests, evidence, approvals, provenance, versions, and API/resolver-ready records.
Do suppliers pay to respond?
No. Suppliers can answer evidence requests for free. Manufacturers control the request scope, review, approval, and publication workflow.
How does supplier evidence reuse work?
Suppliers can submit a record once, attach source documents, and grant reuse across customer requests while keeping permissions and audit context attached.
How are claims verified?
Manufacturer reviewers approve values before publication. Each approved claim keeps source evidence, actor, timestamp, version, and grant metadata.
What standards does Redy align with?
Redy is designed around ESPR-aware schemas, GS1 Digital Link patterns, verifiable-credential/signing posture, APIs, webhooks, and resolver-ready outputs.
Can Redy connect to existing systems?
The workflow is intended to sit beside ERP, PLM, PIM, LCA, supplier portals, and document stores through imports, APIs, and webhooks.
Is this production copy or a preview?
The workflow direction is intentional and reflects how Redy operates. Final legal, standards, SEO, and launch details are still being finalized.