How a PRUVILO deal is designed to work
A structured record carries the product from buyer expectations to seller declaration, evidence, receipt and, when authorized, return.
Illustrative only — deal workflows, categories, coverage, policies and payment providers are not live or approved yet.
From expectations to one shared record
Buyer sets the requirements
The buyer records the expected condition, identifiers, accessories, delivery and any accepted tolerances in structured fields.
Seller declares the actual item
The seller independently enters the item’s actual characteristics, known defects and anything unknown or unable to be verified. The declaration is not copied from the buyer’s requirements.
PRUVILO compares each characteristic
Matches, missing information and differences are shown side by side. Each party can see where the two records agree or differ.
Critical differences must be resolved
In the planned flow, an unresolved critical difference, critical missing detail or incomplete required verification would block the payment step.
Both approve one locked version
After any changes are accepted, the buyer and seller approve the same Product Passport, price, terms, evidence plan and policy versions. A later change would require a new version and both approvals.
Evidence follows the product
Planned evidence is linked to the characteristic it supports. At receipt—and during an authorized return—the item would be compared with the same locked Product Passport. Completion, release, disputes, returns and refunds would follow the policy published for that deal.
This page explains a planned process. It does not create a deal or state that any category or protection is currently available.
See the shared product record
Learn how Expected, Declared, Locked, Received and Returned records stay connected.