Receipt Scanner

Examine the image carefully. Czech grocery receipts typically contain:

• Store name at the top (Albert, Lidl, Tesco, Billa, Kaufland, Penny, Globus, Makro, etc.)
• Item lines — product name, quantity, unit price, total price
• Date and time of purchase
• Discounts, loyalty card savings
• VAT breakdown and total

Extract:

• Store name
• Purchase date (from the receipt, not today's date)
• Each item: name, quantity (default 1 if not listed), price in CZK

2. Normalize items to fridge-tracker categories

Map each receipt item to one of the fridge-tracker consumption categories:

Skip non-food items that don't fit any category (bags, batteries, magazines, etc.) unless they fall under cleaning/household.

3. Confirm with the user

Before updating the fridge state, present a summary for confirmation:

"I see a receipt from Albert (March 23, 2026):

• Milk 1.5% x2 — dairy
• Chicken breast 500g — fresh meat
• Bananas 1kg — fresh fruit
• Pasta 500g — pantry
• Toilet paper x4 — household

Should I add these to your fridge tracker?"

Keep the confirmation concise — group items by category, skip prices (the user already knows what they paid). If many items (10+), summarize by category counts instead of listing each item.

If the user says "just add it" or has previously indicated they don't need confirmation, skip this step in future interactions.

4. Update fridge-state.md

Read /workspace/group/grocery/fridge-state.md and add the extracted items.

For each item:

• Delivered date = the receipt date (not today's date, unless the receipt date is unreadable)
• Quantity = as shown on receipt
• Est. Remaining = 100% (freshly bought)
• Status = FULL

Place items in the correct section (Fresh, Pantry, Frozen) following the existing file format:

| Item | Qty | Delivered | Est. Remaining | Status |
|------|-----|-----------|---------------|--------|
| Chicken breast (Albert) | 1 | Mar 23 | ~100% | FULL |

Add the store name in parentheses after the item name so the user can distinguish Rohlik deliveries from other shops.

If an item already exists from a recent Rohlik delivery with OK/FULL status, don't duplicate it — the user likely bought extra. Instead, increase the estimated remaining percentage or note the additional quantity.

5. Update delivery-log.md

Append a compact entry to /workspace/group/grocery/delivery-log.md:

### Mar 23 — Albert (receipt scan)
Items: 5 | Total: ~320 CZK
Categories: dairy (2), meat (1), fruit (1), pantry (1), household (1)

Mark it as "receipt scan" to distinguish from Rohlik deliveries.

Edge Cases

• Blurry or partial receipt: Extract what you can, ask about items you're unsure of. "I couldn't read 2 items on the receipt — can you tell me what they were?"
• Non-Czech receipt: The category mapping still applies, just the product names will be in a different language. Adapt accordingly.
• Receipt without date: Use today's date and note the assumption.
• Multiple receipts in one image: Process each separately, ask which store if unclear.
• User sends a photo that isn't a receipt: Don't force receipt processing. If it's clearly not a receipt (a meal photo, a product photo), respond normally.

What NOT to Do

• Do NOT update staples.md or preferences.md from receipt data — those files track Rohlik ordering patterns specifically. Non-Rohlik purchases inform fridge state only.
• Do NOT try to find matching Rohlik product IDs for receipt items.
• Do NOT suggest reordering receipt items on Rohlik unless the user asks.
• Do NOT update spending.md with non-Rohlik purchases — that file tracks Rohlik spending only.