Every change we ship to Chefy, newest first. New features, improvements and fixes across costing, stocktake, procurement and Chefy Go.
4 releases
Per-entity email preferences for recipes, menu items and supplier products, plus one-click unsubscribe, so notifications match what you actually care about.
Charts are now built on the server instead of shipped to your browser as raw data, and what is on screen refreshes itself rather than going stale. One dashboard query went from 6.3 seconds to 0.06.
A ground-up rebuild for the floor: named Go instances per venue each with their own join code and devices, a prep board with priorities, due times and repeats, stocktake by location, and wastage capture.
Sales was the slowest screen in Chefy. Reworking how it loads took it from just over five seconds to a third of a second.
3 releases
Recipes and menu items now show their multi-level sub-recipe composition inline, so you can read the full build without clicking through each layer.
Mark an item as an organisation template and control which venues may use it. Venues fork their own version where they need to, and you see the blast radius before a policy change lands.
Record what gets thrown away, against a menu item, recipe output or supplier product, with a reason and a note, costed automatically. A venue history and a top-wasted-products view come with it.
1 release
A consumption view on any supplier product, recipe or standard product showing every downstream thing that depends on it, as a radial graph or a list, drillable per venue.
4 releases
Our AI provider retired the model we used for reading invoices. A catch-all turned that failure into a zero-confidence score, so uploads were not erroring, they were being politely rejected as unreadable. Every single one.
An overnight report on your dashboard: how yesterday went against a typical day, what stood out, and an outlook for today with expected sellers and a prep forecast.
Save the filters and sorting you use most as a named view. Set menus arrived as a costing object in their own right, alongside a loyalty and rewards program.
Approval stopped being all-or-nothing. Admins configure require-approval or auto-approve per plan, organisation and venue, with inheritance down the chain.
3 releases
A billing page showing metered usage over time and where the cost comes from, with spend alerts and a self-serve upgrade path.
A floating help button for asking questions in context, rather than going looking for documentation somewhere else.
Orders gained a real lifecycle: draft, awaiting delivery, overdue, awaiting invoice, invoiced, reconciliation needed, completed. Receiving handles partial deliveries, substitutions and things you never ordered.
1 release
Passkeys and multi-factor authentication arrived, so getting into Chefy can stop depending on a password someone wrote on a whiteboard.
1 release
Supplier pages gained spend over time, order frequency and top products, plus delivery days, lead times and closure periods so ordering respects when they actually deliver.