Kooklin

The prompt to build it yourself

Build me a batch-based food traceability log, for my restaurant, to replace a HACCP subscription.

Stack: installable phone web app (PWA, mobile first), Node, Express, SQLite (better-sqlite3), hosted on my small server. No heavy front-end framework.

Core of the tool:
- Receiving: supplier, product, batch number, use-by date, quantity, temperature on receipt, photo of the label.
- Production: a dish or preparation records the batches used, quantity produced, use-by date set.
- Backward search: from a batch, show all the dishes concerned; from a dish, show all the batches.
- Alert when a batch nears its use-by date.
- Non-conformities and supplier recalls, with corrective action.

Common requirements (a reading only counts as evidence if it is reliable):
- Every record is timestamped by the server, with the user. A reading is never edited or erased: a correction creates a new line that points back to the old one (append-only log).
- Deviations (temperature out of range, cleaning not done) trigger a non-conformity to handle: cause, corrective action, closing date.
- Thresholds, zones (cold rooms, hot dishes) and checklists are set in a configuration file, without touching the code.
- PDF export per period, ready to show during a health inspection. Configurable data retention period.
- Several users (PIN code per employee), no email account. No telemetry.
- CSV and PDF export of traceability over a period.

Out of scope: managing several kitchens, purchasing integration, certification.

README: installation, database backup, and a reminder that this tool documents your food safety plan but does not replace it: have it reviewed by your inspection body or a hygiene consultant.