Venue Admins can now bulk import products at their venue, one + button on the product and recipe lists asks whether to import or add one by hand, two venues importing the same file keep separate imports, and a big upload tells you it is safe to leave and shows live progress.
New
Venue Admins can bulk import. The Import Products button and every step of the wizard used to need an Organisation Admin. A Venue Admin now runs the whole import for their own venue, from picking the file to committing the products. The keyboard shortcut and the command palette follow the same rule. Team Members still cannot import and see a plain message instead of a wizard whose steps fail.
Improved
One button that asks. In a user test nobody found the importer, because it sat on a second floating button above the +. The product list and the recipe book now have one + button. When you may import, it asks whether to import products from an invoice or price list, or add one by hand. On the recipe book it asks whether to import recipes from documents or photos, or add one by hand. On phones and small tablets the choice opens as a bottom drawer.
Big uploads tell you what is happening. Approving a few hundred rows used to leave you on a spinner for minutes. The upload now says it is safe to leave, estimates how long it will take, shows "N of M products saved" as it goes, and picks up where it was when you come back. Row errors name the product and its code, and a failure that needs fixing takes you to the fixing step instead of offering a retry that cannot work.
Fixed
Two venues in one organisation importing the same supplier file now each keep their own import. Before, the second venue's upload took over the first venue's session and mixed their rows and matches.
One access-level ladder everywhere: Chefy Admin, Organisation Admin, Venue Admin, Team Member, View Only, Chefy-Go Only. Every user card wears its role, pending invitations sit in the list with Resend and Revoke, the admin seat price shows before anyone is promoted, and sign-in survives a reload.
New
One name for a person's access. A Venue Admin could show up as "Venue Team Member" on the users list while the venue page called them something else. Every person now has one access level from one ladder: Chefy Admin, Organisation Admin, Venue Admin, Team Member, View Only, Chefy-Go Only. Someone with different levels at different venues reads "Varies by venue" with a row per venue. Inviting, the Permissions tab, adding to a venue and transferring ownership all use the same picker in the same order, and an admin can now add someone to a venue as Chefy-Go Only.
Invitations live in the list. A pending invitation shows as a user card pinned to the top of the Users list, with a Pending chip, when it was sent and when it expires, and Resend and Revoke right there. The separate panel above the list is gone.
Improved
The role on every card. Each card on the Users list leads with a labelled role chip instead of an icon you had to decode, and the details drawer spells the role out.
The seat price before you promote. Making someone an Organisation Admin adds a paid seat. The edit form and the invite form now show the same confirmation as the Permissions tab, with the estimated monthly cost, before anything is saved or sent. Moving an Organisation Admin down to a venue level asks which venue they keep and at what level, so nobody is left with no venue by mistake.
Fixed
Sign-in survives a reload. On Android, switching to your mail app to read the sign-in code could reload Chefy and send you back to the password step, which then sent a fresh code and invalidated the one you had. The page now reopens on the code step with "Enter the code we already sent to..." and the code in your inbox still works.
A tab left open after you signed out elsewhere now takes you to the sign-in form on its next action, with your page carried along, instead of a "Try again" error that could never succeed.
Before deleting a product, recipe, venue or organisation, Chefy checks what depends on it and tells you. A product names the recipes that use it, a recipe another recipe relies on is refused with a reason, and deleting a venue keeps the catalogue products other venues still use.
Improved
A product in use says who uses it. Deleting, deactivating or unsharing a product that a recipe uses as an ingredient now opens a confirmation that explains it is in use and lists the items that use it. Before, the product page showed a generic "Something went wrong". If usage cannot be checked, Delete stays disabled and the dialog says how to retry.
A recipe in use cannot be quietly discarded. Discarding a draft recipe whose outputs another recipe or dish still uses is refused, and the dialog stays open with the reason. Before, the discard went through and the other recipe silently lost that ingredient from its cost. Bulk discard, delete and deactivate check the whole selection first: if one recipe is in use, nothing changes and the dialog names it. Discarding a draft together with the drafts that use it still works in one go.
Deleting an organisation checks first. The confirmation shows a checking state and keeps Delete Forever disabled until the users and venues that go with it have been counted. If the check fails, the dialog says what to do.
Fixed
Deleting a venue keeps your products. Supermarket and free-catalogue products that other venues' recipes still use stay on the catalogue with their prices when a venue is deleted. Before, they turned into locked placeholders. "Placeholder" now means one thing: a TBC product you created mid-recipe.
AI insights and reports no longer drop a recipe that has a line pointing at a discarded recipe. The recipe shows without that line.
The orders list opens in a blink instead of spinning, stage chips filter on the server, bulk Submit all and Delete all tell you exactly which orders did not go through, and an order that was sent is never reported as failed because its preview image was slow.
New
Bulk actions name what did not change. Submit all and Delete all now try every selected order, even after one fails. If some fail, the dialog says which, by supplier, with the reason when the supplier gave one: "The Bidfood order was not submitted. Bidfood is closed today. The other 2 orders were submitted." Only the failed orders stay selected, so Confirm retries just those and never resends an order. A failed Merge says the orders were not merged instead of getting stuck.
Improved
The orders list opens at once. It used to load every matching order in full before showing a card, and on a busy venue that meant a long spin or no list at all. It now loads a page of light cards and fetches the next page as you scroll. On the demo venue the first cards went from about two seconds to well under one, and the download shrank from megabytes to kilobytes.
Stage chips count and filter on the server. Pick Awaiting Delivery and the list pages that stage like any other filter, while every chip keeps its true count across the whole result, not just the rows loaded so far.
Fixed
Submitted means submitted. An order that was sent and emailed to the supplier is no longer reported as failed because its purchase-order preview image took too long to draw. When a submission does fail, the Submit button stops spinning, the dialog shows the reason, and the list refreshes to show each order's current stage.
Delete all works on the organisation-wide orders list, and the success message reads "Successfully submitted 3 supplier orders" instead of naming an internal record type.
Cost and sales charts across the recipe book, the product lists and the recipe report get a proper value axis, a period label that stays out of the title's way, trends on every recipe revision, and only the metrics that apply to a recipe you do not sell.
Improved
The period label sits under the title. On the Supplier products, Standard products, Recipes, Menu items and Venues lists, the right-panel chart shows "Last 28 days" on its own line. A long title wraps between words instead of splitting one and running into the legend.
Only the metrics that apply. A recipe marked Not on menu offers Total Cost and Cost / Unit in the Recipe Graph. COGS and Sales stay for recipes you sell, so old sales figures no longer stand in for a recipe that is off the menu.
Fixed
A real value axis for flat lines. A cost that barely moved used to fill the whole plot, so every tick read the same cent and the line sat on the edge. Charts now pad the axis around the values, draw both axis lines, and give sales their own scale on the recipe report, so a steady $7.49 line sits mid-plot with ticks you can read.
Trends on every revision. A recipe revision in the recipe book showed a ready tile with no trend. Its card and detail sparks now show historical cost, sales and COGS. Compact spark charts let the costing band show through, and a single recorded reading shows as a dot.
A recipe made only of sub-recipes showed $0.00 and 0% COGS in the list until you opened it.
Not on Square? Export sales from your point of sale and upload the file. Chefy maps the columns with you, checks the dates, and feeds the result into the same dashboard, per-item analytics and AI insights a connected venue gets.
New
Sales from a spreadsheet. Until now the sales side of Chefy needed a Square connection. Any venue can now export a sales report from its point of sale and upload it as a CSV. Chefy helps you match the columns to menu items and quantities, previews wide files with sideways scrolling, and tells you what was imported and what needs fixing before anything counts.
Trading dates, read and checked. When the filename carries an unambiguous day-first date, Chefy uses it as the trading date. Ambiguous dates and date ranges are held for you to confirm, and the upload screen explains what it checked and where you can correct it.
The same numbers, whichever way they arrive. Uploaded sales feed the dashboard, cost of goods, margin and per-item trends exactly as connected sales do, so a venue on a spreadsheet gets the same picture as a venue on Square.
Improved
AI insights say what they know. A venue with the Sales module and no live point of sale used to get a daily insight telling it to "verify the POS integration". It now gets the operations report instead, covering cost movements, recipe edits, supplier activity and stocktake variances. The same applies to the on-demand insight behind the Sparkles button. A window with no sales reads as no sales, not missing data.
Fixed
Dashboard trend charts load reliably for organisations with a large sales history.
A month of fixes for the shared kitchen tablet. Cooks change their own PIN, a dish stays with the cook who started it, the cookbook shows each dish once, and the front door behaves when a section is empty, a device is removed, or the network drops.
New
Change your own PIN. Tap your name in the rail, choose Change my PIN, prove the one you have and set a new one. Until now a PIN could only be set once at the tablet or cleared by an admin.
A dish belongs to the cook who started it. Signing out or reloading no longer hands a half-cooked dish to the next person at the front door. The next cook sees "Sam is cooking this dish" with a one-tap Take over, and the In progress list names the cook on every card.
Improved
One card per dish in the cookbook. A dish that is both a recipe and a menu item showed twice, with Recipe and Menu badges and filter chips to tell them apart. It now shows once, opens a recorded cook, and the badges and chips are gone.
The front door. A venue with crew and no recipes yet shows the name grid at once instead of hanging. A tablet an admin removed lands on the link screen by itself. A tablet that cannot reach Chefy is offered a retry instead of being told it was unlinked. The keypad stops at four digits and Enter confirms.
Fixed
Discard is greyed out on a dish that is somebody else's, and a card leaves the cookbook the moment a dish is switched off, without waiting for a reload.
A standard product can hold a pool of approved alternative suppliers and switch between them in one click, a supplier product that recipes buy directly can be converted into a standard product in one gesture, and the standard product screen now matches the recipe and supplier product screens.
New
Approved alternatives on a standard product. Alongside its active supplier product, a standard product keeps a pool of approved alternatives priced side by side per the product's own unit. Recipes keep costing from the active one until a buyer clicks Make active, which switches in one click with no review. Adding or removing an alternative is a normal edit that goes through a change set. Allergens and tags are the union of the active product and every alternative, with chips saying which product contributed each allergen.
Convert to standard product. From a supplier product's row, card or status banner, create a standard product wrapped around it and move every recipe and menu item that bought it directly onto the new standard product. A preview shows how many recipes and lines will move and the cost before and after. Everything lands in one named change set, open for review, so nothing goes live until it is approved.
Improved
The standard product screen opens with the shared header card, the cost band and the cost spread across alternatives. The photo controls fold into the Details tab's Photo row, and a Visual or Grid toggle covers the Details and Target tabs, where the grid lists the active target and each alternative with Make active and Remove in the row menu.
Fixed
After an edit, Cost per unit kept its per-kilogram unit instead of falling back to per-gram until a reload.
The second round of change sets. Every new recipe, product and upload asks which change set it belongs to before anything is written, an invoice leaves behind its own applied change set, and the review screen became a proper workspace with tabbed lists, grouped blockers and an activity log you can read.
New
Adding a recipe, menu item, supplier product or standard product opens on one question: which change set does this go into? Pick an open one or start a new one. If you are already working inside a change set, the step is skipped. Product CSV uploads, invoice uploads and recipe imports ask the same question before a file is read.
Processing a supplier invoice creates an applied change set named for that invoice, listing every product it created and grouping every price it changed, so one invoice's whole effect sits in one place.
The change set screen has four tabs: Supplier products, Recipes, Standard products and Placeholders. Each is the ordinary list with search, filters and scrolling, locked to what this change set touched. The Placeholders tab lists the TBC products blocking submission, with Replace in each card, and the count on the tab.
Before review. The red alert is one line with a count and a "See what to fix" button. Placeholders are listed once each with the recipes that use them, and drafts outside the change set offer Move here.
Improved
The activity log is readable. Events sit under day headings with the venue's clock time, each kind has its own coloured mark, and a reviewer's comment or an edit's change is always visible under the row. The same log now draws the Activity tab on recipes and products.
Apply runs in the background, one record at a time, and the page follows it. A large change set no longer fails with a database error. If one record cannot be applied, the page names it and the reason, the records before it stay live, and the reviewer can apply again, return it or discard the rest.
A change set with dozens of items loads its first cards at once, and a recipe on the menu shows once with an "on the menu" mark instead of twice. The Impact panel counts Changes, Blockers and Needs a fix, and list filters can show what was created in, edited in, or untouched by the change set.
The recipe book can show only recipes, only menu items, or both, and the word for what goes into a recipe is now Ingredients everywhere, on screen, in exported workbooks and in the help guides.
New
A Show filter in the recipe book's filter drawer: recipes and menu items, recipes only, or menu items only. A held choice shows as a chip on the controls row and clears from there.
Improved
Inputs are called Ingredients everywhere you read the word: the recipe tab, the row count, the cost line, the drawer actions, breadcrumbs, page titles and the activity log. The drawer's view action now says where it goes, such as View Recipe or View Product.
An exported recipe workbook names its sheet Ingredients. Older files with an Inputs tab still import.
The help site and the marketing site's product walkthrough use the same word, so what you read matches what you see.
Fixed
The first change in the recipe filter drawer used to hide every recipe nothing uses yet. It no longer does.
Edits are now gathered into named change sets. A chef makes a batch of changes, gives it a name, submits it once, and a reviewer sees exactly the world that will land. Apply publishes all of it together. Several change sets can be open at the same time.
New
Named change sets replace approving items one by one. Every edit you make in Planning belongs to a change set. Submit it as a unit, and the reviewer sees the change set's own costs and margins, not a guess. Apply publishes every revision in it at once and cancels rival open edits on the same items, telling their owners. Statuses are Open, In review, Returned, Applied and Discarded.
The Changes screen. Every change set at a glance with its status, its count of changes, an Impact tab that costs the whole batch against live, and an Activity tab that records every step. The bar at the top of the app reads "Viewing <name>. These changes are not live yet."
Notes on a change set. Anyone who can see it can leave a note under the activity log, on any status, including after it is applied, so the reasoning stays with the change.
Return one item, not the whole set. A reviewer can send a single item back with a comment. Its siblings stay submitted, the author fixes it and resubmits, and Apply waits until every item is clean.
Email when your change set is returned. The person who created it gets the reviewer's name, their comment word for word, and a button that opens the change set. There is a notification toggle for it in My account.
Venue admins are told when head office changes something they use. Applying an organisation change set emails every admin of each affected venue with the records that venue uses.
Drop one recipe file or a dozen and walk away. Chefy groups the files into recipes, reads them, matches ingredients to your products, prices anything it has to invent, and hands back finished draft recipes with a log of every decision it made.
New
Automatic import is the default. The upload has a "Review before saving" switch, off by default. Off means finished draft recipes with no further input. On keeps the step-by-step review for anyone who wants to check each line first.
Several files in one drop. Chefy decides which files belong to the same recipe before reading them, so a two-page PDF and its photo become one recipe, not three.
Every decision is written to the recipe's activity log: how files were grouped, which product each line matched and how confident the match was, placeholders created and their estimated cost, unit and density assumptions, and anything it could not resolve. Each entry links to the source document. The first person to open an imported recipe sees a digest of all of it.
Improved
No detected ingredient is ever dropped. A line with an amount in a unit Chefy does not know is counted per item in that unit. A line with no amount gets one estimated from the recipe itself, with the estimate quoted in the log. Repeated mentions in the method fold into one line.
Chefy's own exported workbooks import cleanly, including the hidden sheet they carry.
The help widget's Messages tab is now a two-way conversation with Chefy support. Send a message from inside the app, get the reply in the same thread with an unread badge, and get it by email too with a link straight back to the conversation.
New
Support conversations. Open the help widget, write a message, and it starts a thread. Replies from Chefy support land in that thread, the widget shows an unread count, and each reply also goes out by email with a link that opens the conversation in the right organisation.
A draft you have not sent survives a failed send, so nothing typed is lost.
Improved
When the app hits an error, the crash screen opens a support conversation with the details attached, rather than asking you to describe it. If a conversation cannot be started, it falls back to the emailed report.
Recipes take cups, tablespoons and teaspoons as real units, every product knows what a cup of it weighs, and organisations in the United States get Chefy in ounces, pounds, fluid ounces and gallons for both display and entry. Underneath, everything is still stored in grams, so costing never changes.
New
Cup, tbsp and tsp on every product and sub-recipe. They appear in every unit picker, from recipe ingredients to stocktake, wastage, ordering and spreadsheet cells. A cup is 250 mL on an Australian market and 236.6 mL on a US one, with a tablespoon of 20 mL and 15 mL to match.
Tell Chefy what a cup weighs. A standing line under the product's unit ladder reads "1 cup = 250 g" with an Edit control. Entering the real weight sets the product's density, the tablespoon and teaspoon rows follow, and a corrected cup weight survives later price uploads.
US customary units. An organisation's measurement system defaults from its country and can be overridden in settings. Weights show and enter as oz and lb, volumes as fl oz and gal, across screens, PDFs, emails and spreadsheets. The AI assistant answers in the same units.
Improved
Recipe import reads "1 cup flour" as one cup and puts it on the product's cup row, rather than silently converting it, and only notes a density assumption where water was genuinely assumed.
Fixed
Stating a density re-weighs recipe lines written in volume units. One cup of flour stays one cup when you tell Chefy a cup of flour weighs 150 g; before, the line kept its grams and the count drifted to 1.67 cups.
A recipe's method is now real steps, not a block of text. Steps can carry photos, a section header, a photo check or a temperature check, and Chefy Go walks a cook through them one at a time. Any recipe prints as a card for the docket rail, with a QR code that opens the live version.
New
Cooking instructions replace the Method tab, with six parts: Method, Plating, Time to complete, Equipment, Storage and shelf life, and Notes. Steps come in three kinds and can be added, reordered and deleted. An instruction step takes a section header and its own images. The spreadsheet view and the Excel round-trip carry all of it.
Photo checks and temperature checks. A photo check holds the step in Chefy Go until the cook takes a picture of what they produced. A temperature check takes a reading against the recipe's target, flags one outside the range, and still records it after a confirmation, because a log that refuses a real reading is not a log. Whoever signed in at the tablet is stamped on the run and on every capture, and the record is there to audit later.
Print a recipe card. From any recipe tab, choose docket roll, A5 or A4, set a batch multiplier, and download or print. Amounts are already scaled. Every card carries when it was printed, a version stamp and a QR code that opens the live recipe on the scanning device, so paper always points back at the truth. Cards print the section headers, checks, active and total time, plating and storage notes, and the equipment list.
Chefy Go sections. One tablet can serve every section of a venue, and cooks pick their section at the front door.
Improved
Time to complete shows before a cook starts a dish, and tapping any recipe or step image opens it full screen on the shared iPad.
Print the allergen sheet from a dialog on the recipe screen, and the Allergens and dietary matrix has its own Print button with a masthead and legend on every page.
A venue's demand plan says what it expects to sell on each of the next fourteen days, lets a chef override any figure, and turns the answer into dated prep on the Chefy Go prep lists. The kitchen preps to a number with a reason behind it, not a guess.
New
The Demand plan screen. A two-week calendar on the left with a Plan and Pars toggle. Each item shows one large Producing number and a plain sentence saying where it came from, such as "Floor 12. Your standing Monday par sits above the 4 history expects." Under the date, a verdict for the day: "Producing 84 portions across 11 items, level with sales history."
Forecasts, pars and overrides in one place. The forecast is built from sales history. A standing weekly par sets the floor for each day of the week. A chef's override wins over both, and sales already committed for the day are counted in.
Production for this day. The right panel shows the prep the plan generates for the selected day, batch by batch, before you commit it. Generate prep writes it onto the Chefy Go prep lists as dated tasks.
Improved
The plan recomputes overnight, so each morning's numbers reflect yesterday's sales.
Chefy has a help site with written guides for every daily task, and new organisations get a short checklist in the help widget that ticks itself off as the real work lands. The old click-through tutorials are retired.
New
The Chefy help site. Guides are grouped into Getting started, Day to day, and Admin and account, with search and a print-friendly layout. Day to day covers updating a supplier's prices, reading a recipe's costing, doing a stocktake, raising a supplier order, recording wastage, connecting Square and bringing in your sales, and using insights and reports.
A getting-started checklist in the help widget. Four steps get an organisation up and running: upload your first invoice, add your first recipe, put a recipe on the menu, and invite your team. Each step ticks itself off from what the organisation actually holds, so nobody has to mark anything done, and the widget opens with the tick the moment a step completes.
Improved
The step-by-step tutorials are switched off. They had fallen behind the last month of screen changes and were sending new users the wrong way. The checklist and the help site take their place.
Chefy now keeps a live stock ledger for the venue. Every delivery opens a costed lot, every sale draws it down oldest first, and every stocktake anchors the figure back to what is on the shelf. You see what your stock is worth, how long it will last, and what shrinkage cost you, without a spreadsheet.
New
A per-venue stock ledger. Each receipt opens a lot at the price you paid, consumption drains lots first in, first out, and every sale carries its own cost of goods. The figure starts as provisional and firms up as costs settle, so a late invoice never silently rewrites last week.
Stocktakes price your shrinkage. A count anchors the ledger to reality and the gap between expected and counted comes out as a shrinkage cost, not a mystery. Opening stock has three ways in: the getting-started checklist, adding a product, or the first delivery.
The venue Stock screen shows stock cost against replacement cost with the difference, coverage in days, lots on hand, a forecast, and recent counts. Each product page gets a Stock tab with its lot bar, a pace-and-runway forecast with a runs-dry date that knows about open orders, and a consumption strip.
Live stock rolls out per venue. A venue runs Disabled, Shadow or Active. Shadow shows the figures with a clear note that they are not yet the costing source, so you can check them against your own numbers before switching on.
Fixed
Finalised stocktakes that failed to open, or took the whole stocktake list down with them, load again. Finalising a stocktake with a recipe output line prices the line instead of failing.
Dashboard stocktake figures read the finalised total, carry the last real count forward, and no longer show a placeholder zero as a chart value.
The recipe book, the standard product list and the supplier product list all open as a sheet as well as cards. Sort the whole list from a column header, pick how many rows you see, tick rows for a bulk action, and save the view so it opens that way next time.
New
Grid view on the recipe book and the standard product list, matching the supplier product grid. One row per record, one column per field, name pinned while the rest scrolls. Names and tags edit in place on recipes. The toggle sits beside the count and is remembered per user.
The ingredient picker inside a recipe has the same grid, so a chef choosing an input can scan photo, name, supplier, SKU, cost and cost per unit as a sheet and select from the row.
Rows per page. Choose 15, 30, 50 or 100 rows, with Previous and Next in the sheet's footer. Lists now default to 30.
Tick rows in the grid for a bulk action. A checkbox column stands first, the header box ticks the page, and a bar counts the ticks and offers only the actions every ticked row allows. The old Bulk Actions toggle on the card views is gone.
Saved views remember whether they were saved from cards or the grid, so a default view opens the list in that shape.
Improved
A column header sorts the whole list on the server, not just the rows on screen. The cost chart plots the rows you tick, six by default, each box coloured to match its line.
The right panel splits in two. The cost chart stays on top. Below it, an Overview tab shows sales, cost of goods and margin for the last 28 days plus what needs attention across the whole list, and a Changes tab lists the ten newest edits with who, when and what changed.
One switch replaces opening revisions by hand. Live shows what is approved and in use today. Planning shows the version you are working towards, with every cost and margin computed against your drafts.
New
Live mode shows only approved, current state and is read-only, so a chef on the line or a manager checking a price cannot land on a half-finished draft.
Planning mode is where you work. The first edit starts a draft on the spot, drafts render in place of the originals, and submission and approval happen there. The create-a-revision dialogs are gone.
Improved
Search, lists, the cost chart and every figure follow the mode you are in. Planning finds, sorts, filters and costs by the draft values, Live by the approved ones, so the two never mix on one screen.
Recipes and menu items are no longer two lists. A recipe is the one thing you build, and selling it is a setting on it: sale price, cost of goods, margin, availability and the POS link sit on the recipe itself.
New
Selling a recipe is part of the recipe. Add it to the menu and it carries its sale price, cost of goods, margin, portion, POS item and sales figures, with one Submit and one Approve that land the content and the commercial changes together.
Putting a recipe on the menu goes through the same review as any other change. It shows as pending until approved, and pending items never leak into what the kitchen and the POS see as live.
Improved
One revision per recipe. Menu settings are edited inside the same revision as the ingredients and method, so there is no longer a recipe revision and a separate menu item revision to keep in step.
"Where is this used" is one clean tree of the recipes that consume this one, with nothing counted twice.
A new grid mode gives power users who live in spreadsheets a familiar sheet to work in: rows and columns, editable in place, quick to move through. Every product and supplier screen edits where it is, and barcodes work everywhere a product can be added.
New
Grid mode for power users. If you have run your costing out of a spreadsheet, the supplier product list now works the way you are used to: one row per product, one column per field, click a cell and type. Tab across, arrow down, save as you go. It is built for people who want to get through a lot of products quickly and efficiently, and it is remembered per user so the sheet is there every time you come back.
Barcode scanning. Point the phone camera at a barcode, or use a keyboard-wedge scanner, when adding ingredients to a recipe, counting a stocktake, building an order or logging wastage. An unknown code offers to register it on the spot, and a code shared by more than one supplier lets you tap the one you mean. If the camera is blocked, "Take a photo instead" reads the code from a picture.
Chefy prints its own labels. Products without a supplier barcode get a Chefy QR or Code128 label as a printable PDF, and a barcode typed into search finds the product.
Improved
Name, tags and photo edit inline on recipe, menu item, standard product and supplier product headers. The supplier product Details tab edits supplier, SKU, pack cost, seasonal and tax code in place, and barcodes and allergens edit on the detail screen. The full-form pencil is gone.
Units and conversions open in one dialog that carries the whole ladder, and changing a pack weight keeps the pack price.
Supplier and venue screens are tabbed (Details, Tax settings, Delivery schedule and Stats for suppliers; Overview and Venue settings for venues) and edit in place. Changing a venue's approval mode no longer reverts, and the team picker works.
Upload a Word, Excel or PDF recipe, or a photo of a printed page or a plated dish, and Chefy reads it into a draft recipe you review line by line. Every recipe also opens as a spreadsheet you can export to Excel and bring back.
New
Recipe import. Upload recipe documents or photos in a batch and Chefy extracts the ingredients, quantities and method. A review screen links every ingredient line to one of your products or recipes before the draft is created, with placeholders priced by AI for anything you do not have yet.
Batch uploads show as queue cards in the recipe book, and you can leave and come back to a review where you left it. A photographed dish becomes the recipe's image.
Every recipe tab (Details, Ingredients, Method, Outputs) has a Visual or Grid toggle and an Export to Excel button. Exported sheets round-trip back into Chefy.
Improved
One recipe card across the detail screen, the action sheet and the recipe list, with a five-cell cost band: total cost with the mass split, wastage, by-product, yield and cost per unit. A revision shows its cost change against the original.
Fixed
The list and the detail screen used to print different rates for the same recipe. They now match.
Products, recipes and menu items without a photo get an illustration, and dietary claims sit next to allergens on every row image.
New
Any product, recipe or menu item created without a photo gets an AI illustration a few seconds later, in place. Your own photos are never replaced, and you can ask for a new image when you rename something. Organisations on a paid plan generate freely; free organisations get an allowance of 150 images, then the tile keeps its initials and a banner offers the upgrade.
Vegan, vegetarian and halal get their own icons, shown in green next to the amber allergen icons on row images and in the drawers, so a selling point never reads as a warning. Past four entries the strip collapses to an amber count and a green count.
Improved
The duplicated dietary chips on list rows and detail headers are gone. The Allergens tab groups dietary claims on their own and no longer counts them as allergens.
Fixed
Turning Allergens & Dietary off for a venue removes the badges and the Allergens tab everywhere, as the confirmation promised.
Order rows lead with the product and its supplier, the pantry reads like a ledger with the stepper inline, and you can submit an order from a phone again.
Improved
Each order row leads with a larger product photo, the supplier as a pill and a Details link, with cost per unit, order amount and order cost as a ruled footer. Product names no longer truncate.
The pantry reads as a ledger. Each row shows cost per unit, the amount on order and the running order cost, with the quantity stepper inline. The plus button adds an item, and stepping the last unit off asks before it removes the line.
One stepper treatment across order and pantry rows, and the barcode scan button lines up with the search, filter and sort controls.
Fixed
Submit Order works on a phone again. Below tablet width, tapping a supplier only applied a filter, so the panel with Discard Orders and Submit Order never opened. It now opens a bottom sheet with the purchase order, its items and both actions.
Opening product details from inside the Add Items sheet no longer leaves the sheet underneath fully lit. Stacked drawers layer correctly.
A "to be confirmed" product holds the place in a recipe or order so you can keep moving and fix the gaps at the end. Nothing that contains one can be submitted until it is replaced with the real thing.
New
TBC placeholder products. Drop one in when you do not have the real product yet and keep building; uploading a recipe is much quicker when you sort the missing products in one pass at the end.
Anything that still contains a placeholder is blocked from submission until it is replaced, so a TBC never reaches an order or a costed menu.
Water, ice and soda water come built in, and phone numbers work in any country's format.
New
Every organisation gets water, ice and soda water as free products under a built-in supplier, so nobody has to invent a fake supplier for zero-cost ingredients.
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.
Improved
Charts built on the server, not assembled in your browser
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.
New
Named Go instances per venue with their own join codes
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.
New
Organisation templates with per-venue versions
Control which venues may use an item
Preview the impact of a policy change before applying it
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.
New
Record wastage with a reason, costed automatically
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.
New
Consumption view showing every downstream consumer
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.
Improved
Provider failures surface as errors instead of silent rejections
Fixed
Invoice extraction working again after a provider model retirement
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.
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.
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.
