Suppliers respond without friction.
Free supplier participation makes it easier for manufacturers to get data from the companies that actually hold the evidence.
Suppliers should not need a paid account to answer a DPP request. Redy charges the manufacturer workflow that requests evidence, approves claims, and publishes versioned passports.
Suppliers can respond to DPP requests, share evidence, and reuse approved records without paying Redy.
Manufacturers pay for the operating layer that turns approved evidence into versioned, audit-ready DPPs.
Document parsing and AI-assisted evidence work should be scoped as credits when teams use it at scale.
OAuth and MCP assistant access follows the same supplier and manufacturer workspace authority model as the portal and API.
Production programs can include security review, integration support, volume commitments, and SLA terms.
The commercial model should reinforce the product wedge: suppliers participate freely, while manufacturers pay for the governed DPP operating layer they need to publish.
Free supplier participation makes it easier for manufacturers to get data from the companies that actually hold the evidence.
The paid value is evidence orchestration, approval controls, integrations, versioning, audit trail, and passport publication.
For suppliers answering manufacturer DPP requests and building reusable evidence records.
For teams mapping product groups, collecting first supplier evidence, and publishing initial DPPs.
For manufacturers expanding across suppliers, SKUs, product families, and DPP domains.
For regulated organizations that need diligence, security review, contractual terms, and rollout support.
Supplier workspaces are designed for contribution and reuse. Manufacturer workspaces control issuer actions and publication.
Responding to DPP requests, sharing supplier evidence, and reusing supplier-owned evidence records are free. That promise is about supplier participation in the evidence workflow, not every future paid supplier add-on.
The manufacturer or brand operating the DPP publishing workflow is the commercial buyer. They pay for the workflow, approvals, integrations, governance, and published passport operations.
DPP programs vary by product group, supplier count, integration scope, security review, and published-passport volume. Until packaged self-serve billing is live, Redy should use launch-pricing and contact-sales language.
AI-assisted parsing and OCR can accelerate evidence intake, but production usage should be scoped as credits or an add-on so high-volume document processing is commercially clear.
Assistant access follows the same lane as the workspace: supplier-scoped assistants can work with supplier records and requests, while manufacturer-scoped assistants can work with manufacturer DPP workflows. High-assurance write actions require the same governed consent and step-up controls described on the AI page.
Published passport continuity should match the active product and billing contract. Redy should avoid promising indefinite free hosting unless that behavior is guaranteed by the product and commercial terms.
Bring the product group, supplier count, evidence categories, and integration systems. Redy can map the commercial plan to the rollout.