Life/Personal admin & shopping

Make a receipts and returns tracker

Extract purchase dates and stated return deadlines while flagging missing policy information.

Make it mine

WHAT YOU’LL MAKEPurchase tracking table
WHAT TO BRINGReceipts · Provided policies
A LITTLE INSPIRATION

Here’s what it could look like.

An illustrative example to show the direction. Your details will make it different.

THE BRIEF

Desk lamp purchased 2026-09-01: sample policy says 30 calendar days after purchase, excluding the purchase date. Travel bag delivered 2026-09-05: sample policy says 14 calendar days after delivery, excluding delivery day. Headphones purchased 2026-09-03: no policy supplied.

THE POSSIBILITIES
Desk lamp — purchase 2026-09-01; deadline 2026-10-01; rule: purchase date + 30 calendar days.
Travel bag — delivery 2026-09-05; deadline 2026-09-19; rule: delivery date + 14 calendar days.
Headphones — purchase 2026-09-03; deadline unknown; obtain policy.

REVIEW BEFORE RELYING
Condition requirements, shipping-versus-receipt deadline, final-sale exclusions, and local cutoff time are not supplied.

SUGGESTED COLUMNS
Item, store, order reference, policy start date, deadline, rule, status, next action, source.
FROM IDEA TO SOMETHING REAL

A good way to get there.

  1. 01

    Provide receipt dates and the exact relevant return-policy wording.

  2. 02

    Extract one purchase per row and distinguish order date, delivery date, and the date the policy uses.

  3. 03

    Calculate deadlines only for unambiguous rules; retain the rule beside the calculation.

  4. 04

    Check the extracted dates and save the result in a tracker. Add reminders only as a separate confirmed action.

The prompt behind this idea

Replace the bracketed details or make it yours using the form.

Build a purchases-and-returns tracker from [Add receipts] and [Add policies]. Scope: [Add scope]. Columns: [Add columns]. Extract facts with their source. Distinguish purchase, shipment, and delivery dates. Calculate a return deadline only when the supplied policy specifies the starting date and counting rule. Mark missing or ambiguous deadlines as needs review. Use ISO dates and show the calculation rule. Do not invent a store policy or claim a return is eligible when exclusions remain unresolved.
MAKE A GOOD RESULT BETTER

Give it a second look.

  • Every deadline uses the correct start event.
  • Missing policies do not become guessed deadlines.
  • Date arithmetic is independently checked.
A FOLLOW-UP WORTH TRYING

“Add a needs-action view that includes unknown deadlines. Do not drop records merely because they lack enough information to calculate a date.”

A calculated date does not confirm return eligibility; use the actual retailer's terms.

The capability to look for

An assistant with file analysis or code execution for tables, calculations, and charts.

Find a tool for the job

How these ideas and prompts are made

Did you get a result you could use?