Less Twice

The Next Shopping List Begins in the Cupboard

A shopping list often begins with what someone remembers wanting. Less Twice begins one step earlier: what may already have come home? A receipt cannot answer every question about a cupboard, but it can provide a useful cue before another item enters the basket.

The word “may” matters. A repeat purchase does not establish a mistake. Food gets used, shared and replaced on schedules the software cannot observe. Treating the repeat window as a prompt rather than a verdict keeps the tool useful without asking a local ledger to judge a household it does not know.

Unit prices add a second kind of context. A package that looks familiar may contain less, while a larger pack may not offer the better unit cost. Comparing matching products and measures can make that change visible. The notebook keeps incompatible units and currencies apart instead of manufacturing an apparently complete answer from unlike inputs.

The final decision belongs in an editable list. People can add what they need, adjust quantities and check items off before exporting. Only the chosen list fields travel in that file; the receipt history does not need to follow them. A useful outcome might be one tin remembered before leaving home or one packet reconsidered at the shelf. Less Twice is built for that modest improvement, rather than a claim that every purchase can be optimized.

The working notebook accepts structured CSV receipts and pasted CSV text, not photographs. Matching rows can be compared by normalized units, with source lines available for inspection. The shopping list supports editing and export of item names, quantities and checked states. Data stays in browser storage; no hosted household account or automatic cloud backup is implied by the local interface.