Food Trades Lite — Recipes, Allergens, Production and Waste (free) (Odoo Online)

Food Trades — Recipes, Allergens & Production (DYONYSOS)

Food craft businesses (butchers and delicatessens, bakers, pastry chefs…) plan their daily production by hand, lose track of unsold items and waste at the end of the day, and display allergens on paper that becomes outdated as soon as a recipe changes. This application addresses all three problems on a deliberately simple foundation: product, stock, account — no dependency on mrp, no cash register, no Enterprise module.

Important — what the app does, and what it does not do. It is not a full HACCP system (no temperature logs, no cleaning plan, no upstream supplier traceability lot by lot), not an industrial-style material cost calculation (see Odoo Manufacturing if you need more advanced features), not a cash register (pair it with Point of Sale if needed), and it does not manage use-by dates per lot with expiry alerts: the module tracks actual waste, not forecast expiry.

Also searched as: INCO regulation allergens Odoo, bakery allergen labels, unsold waste management for butchers and delicatessens, artisan daily production schedule, birthday cake takeaway order Odoo.

• Recipe sheet (dyo.bouche.recette): ingredients with quantities, linked to a finished product (product.template). Allergens are never checked by hand on the finished product: they propagate automatically from the allergens declared on each ingredient — including when an ingredient is itself the finished product of another recipe in the module (pastry cream used in a layered dessert, for example).

• Reference list of the 14 major allergens (dyo.bouche.allergene) from EU Regulation No 1169/2011 (INCO), shipped with the module (functional data, not demo data): gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, tree nuts, celery, mustard, sesame seeds, sulphites, lupin, molluscs.

• Labels never silently outdated (main risk identified): each recipe carries a “label up to date” indicator calculated by comparing the validated set of allergens with the current set of allergens (recalculated whenever an ingredient changes, even indirectly, through a sub-recipe). The slightest difference switches the indicator to “to review” — on the recipe form, in lists, and on the product — until a manager explicitly validates it.

• Cross-cutting search: “which products contain tree nuts?” is a simple search on the product's Allergens field — it works just as well for a finished product with a recipe as for a purchased raw material whose allergens are declared manually.

• Daily production (dyo.bouche.production_jour): plan by product and by day, with a suggested quantity calculated from the invoiced sales history (account.move) of the previous 28 days — averaged only over days with a sale, so that closing days do not dilute the average. A starting point, never an imposed quantity.

• Waste and unsold goods (dyo.bouche.perte): quantity, configurable reason, recording that delegates to stock.scrap (the standard stock move logic is never rewritten); waste rate per product over a period, relative to planned production.

• Customer takeaway orders (dyo.bouche.commande_client): birthdays, events, with pickup date and product lines; automatic numbering; alert when an order approaches its pickup date without having been sent to production.

• Dashboard: pivot/graph views of production and losses, groupable by product family (category).

Demo data: a baker-pastry chef with three recipes (including one sub-recipe used in another, to illustrate cascading propagation), a production plan over several days, recorded losses, and a customer order.