How Pantry reads a faded, crumpled grocery receipt
A supermarket receipt is a terrible document. It is printed by heat on paper that fades in a warm car, crumpled before it leaves the trolley bay, and written in a shorthand no two supermarkets share — names chopped to fit a narrow roll, quantities in three different formats, and the occasional bare product code sitting where a tomato should be. It is also the single best record of what just entered your kitchen, which is why Pantry is built around reading it.
What a receipt knows that nothing else does
Everything Pantry does downstream — the countdowns, the digest, the use-it-tonight nudge — starts from two facts per item: what it is, and when it was bought. The receipt is the only artefact from a shop that carries both, for the whole basket at once, including the loose carrots and the deli ham that never had a barcode to scan. One photo and the entire trolley is accounted for, with the purchase date — the day every shelf-life clock starts from — printed right at the top.
The mess, item by item
Reading it is the hard part, and the reasons are worth being plain about.
- Abbreviation is the norm. Receipt printers work a narrow roll, so names arrive compressed and inconsistent, differing between chains and sometimes between stores of the same chain. Pantry reads the receipt itself rather than matching one supermarket’s template, which is what lets Coles, Woolworths, IGA, Aldi and the corner grocer all go through the same way.
- Thermal print fades. The receipt photographed on shopping day is a different document to the one found in a pocket a week later. Sooner is better, and shopping day is best.
- Not everything on a receipt is food. Dishwashing tablets do not have a use-by date worth tracking. The reader is built to filter non-food lines out on purpose — Pantry tracks grocery shelf life, not your whole shopping history.
Wrong lines, and what happens to them
Some lines come back wrong. This site has a standing policy of not quoting an accuracy number nobody can show the workings for, and it applies to Pantry first: receipts are messy, and a perfect read is not the promise. The promise is the recovery. You confirm the list after every scan, fixing a line takes two taps, and Pantry is built to remember the correction — so the item that scanned strangely this week is recognised the next time that receipt shorthand appears.
That confirm step is not an apology for the reader. It is the design. A list the household will trust for weeks has to be right, and thirty seconds of review on shopping day is what makes every date on it worth believing.
From paper to pantry
Once confirmed, each line becomes an item with a name, a purchase date, and an expiry estimate drawn from the same CSIRO-grounded shelf-life data behind the reference table on this site — a different window for the chicken than for the cheddar, because they do not age alike. The receipt goes back to being rubbish. The information on it becomes the list your household runs the week from — which, given what forgetting costs, is the best thing a terrible document ever turned into.