Proofdeck

After Checkout, Time Becomes the Interface

A shopping history answers what you bought. It rarely answers what needs attention next. Those are different questions, and a list ordered by transaction time is not always the best way to answer the second one.

The record gathers evidence and time in one place. A deadline filter can reduce attention spent on distant purchases, while the policy note prevents the interface from pretending every return follows the same rule. Calendar export hands the reminder to a tool the user already controls. That is a deliberately modest division of responsibility.

A control desk should help distinguish an approaching decision from a distant one. The seven-day filter makes that distinction concrete: it changes which purchase records deserve attention now. It does not rewrite a return policy or decide whether the item should go back. Proofdeck is useful precisely because it leaves that decision with the owner while making the supporting evidence easier to reach. A quieter queue can be a better outcome than a dashboard full of activity.

The sample kettle is deliberately ordinary. If a purchase desk cannot make an everyday return easier to understand, a more impressive demo would only hide the problem. No account is required to keep a record here. The trade is local responsibility: export what matters before changing devices or clearing browser storage.

Merchant policies are user-entered records, not guarantees. OCR is optional and requires its local runtime assets. No merchant integration or cloud reminder service.

Your calendar already has a job. Proofdeck hands it the dates instead of pretending to run a second reminder service. Fewer places to check is the feature.