Public verification
A warranty should not disappear into a private spreadsheet after purchase. A product-passport style verification page gives buyers and service teams a controlled public record for status, reference numbers, seller context, and next steps while keeping private documents and account data protected.
Best for sellers, distributors, ecommerce teams, service desks, and buyers who need fast proof that a warranty exists and is current.
Public verification is separate from private warranty records.
Protected account routes redirect unauthenticated users.
API and MCP private actions require scoped tokens.
Decision point
The public layer should answer the operational question without exposing the private record. It should confirm whether the warranty is recognized, whether it is active or expired, and which safe next step the user should take.
Decision point
A verification page should not leak customer documents, private notes, account ownership, payment details, or internal approval evidence. Those belong behind authentication and tenant checks.
Use Warrantee to separate public verification from private warranty operations.
Not exactly. The product passport is the safe public surface. The private warranty record can include documents, ownership, claims, approvals, and account-specific history.