dadaloop82/EverShelf

Summary Expose a documented public REST API and an outbound webhook system so EverShelf can be integrated with external automation platforms (n8n, IFTTT, Make, Home Assistant REST commands, etc.). Motivation Power users want to connect EverShelf to their broader home-automation stack — triggering automations when stock runs out, syncing with other apps, or building custom dashboards. The existing internal API is undocumented and protected by a settings token not designed for programmatic use. Proposed behaviour Public REST API New dedicated API key (API_KEY in .env, separate from SETTINGS_TOKEN) Authenticated via Authorization: Bearer <key> header Endpoints (read + write): GET /api/v1/inventory — list all items POST /api/v1/inventory — add item PATCH /api/v1/inventory/{id} — update quantity / fields GET /api/v1/shopping — current shopping list GET /api/v1/stats — dashboard stats OpenAPI 3.0 spec added to docs/openapi.yaml (extends existing file) Outbound webhooks Conf

Summary Add a native internal shopping list that works without any external account, so users who do not want to use Bring! still get the full shopping list experience. Motivation Bring! requires a separate account and app install. Many self-hosted users prefer a fully self-contained setup. The internal list would mirror all current Bring! features (auto-add on depletion, smart suggestions, price estimates) but store data locally. Proposed behaviour A new shopping_list SQLite table replaces Bring! as the data store when BRING_EMAIL is not configured All existing shopping list features remain identical: Smart suggestions (AI-powered) Price estimates Auto-add when stock hits 0 Auto-remove when a scanned product matches a list item Bring! catalog icon mapping reused for internal list icons Settings: toggle between *Bring-c bg-secondary /var/www/html/dispensa/index.html and Internal list mode Optional: one-way export of internal list to Bring! for users who later want to switch Accept

Summary Paste a recipe (plain text or URL) and EverShelf uses AI to extract the ingredient list, checks what is already in the pantry, and adds the missing items directly to the shopping list. Motivation Users frequently browse recipes online and then manually check their pantry and write a shopping list. This feature automates that entire flow. Proposed behaviour Input modes Paste text: user pastes raw recipe text into a textarea Paste URL: user pastes a recipe URL; server fetches the page HTML and extracts the recipe schema (schema.org Recipe or plain text fallback via AI) AI processing Gemini extracts ingredients with quantity and unit (e.g. "2 eggs", "200 g pasta") Each ingredient is matched against current inventory (name similarity + category) Items with sufficient stock are shown as ✅; items missing or low are shown as ➕ Actions Add all missing → bulk-adds to Bring! or internal shopping list Add selected → user picks which items to add Save as template → stores th

Summary Generate and download a PDF report summarising the current inventory, monthly consumption per category, and food waste metrics. Motivation Families and shared households want a printable or archivable overview — useful for budgeting, reviewing waste habits, or sharing with a partner. Proposed behaviour A Download Report button in Settings → Info tab or Dashboard Report contents: Cover: EverShelf logo, household name (from APP_NAME .env), report month/year Inventory snapshot: table of all items with quantity, location, and expiry date Consumption summary: top 10 most-used products + breakdown by category Waste summary: items thrown away during the month + estimated kg wasted Shopping cost estimate: total estimated value of current shopping list Generated server-side (PHP) using a lightweight HTML→PDF approach (e.g. Dompdf or a headless-browser-free library) No external service dependency Acceptance criteria PDF generates without error on a standard inventory All se

Summary A Telegram bot that sends proactive expiry notifications and lets users manage their pantry via simple chat commands — a lightweight alternative to PWA push notifications. Motivation Many users keep Telegram open all day but rarely check a web app. Receiving a morning message like "🥛 Milk expires tomorrow" or typing /add 2 eggs fridge is faster than opening the full UI. Proposed behaviour Notifications (server → user) Daily digest of items expiring in the next N days (configurable in Settings) Alert when a product hits quantity 0 and is auto-added to shopping list Commands (user → bot) Command Action /list Show current inventory summary /add [qty] [product] [location] Add product to inventory /use [qty] [product] Record usage /shopping Show current shopping list /help List available commands Configuration TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID in .env A cron job (or the existing cron_smart_shopping.php) sends daily digests Acceptance criteria B