What should a kitchen do when a supplier changes pack size and quietly breaks every recipe cost?

Why One Pack Change Moves Costs You Never Touched

Most cost increases arrive with a number attached. A case goes up a dollar, you see it on the invoice, and you know something happened. A pack size change works differently. The distributor moves an item from a six-unit case to a four-unit case, or a bag drops from five pounds to a slightly smaller fill weight, and the extended line total on your invoice looks close enough to last week that nobody stops on it. The unit cost underneath, the number your recipes actually depend on, has changed by a meaningful amount. Nothing in the kitchen looks different. The cost per ounce you typed into a recipe card months ago is now simply wrong, and it stays wrong until someone goes looking.

The damage compounds because base ingredients are rarely used once. A cooking oil, a flour, a canned tomato, or a house stock feeds a sub-recipe, and that sub-recipe feeds a handful of finished dishes. One stale unit cost can sit under a dozen plates at the same time. Worse, your reports keep looking fine, because a costing report reads the recipe cost you stored, not the invoice you just received. Theoretical food cost stays flat while actual food cost climbs, and the gap gets blamed on waste or portioning. The real cause is a conversion factor that changed at the loading dock. Related: How do you cost a recipe accurately down to the true plate cost?

Keep reading: How do you cost a recipe accurately down to the true plate cost?, What is food cost percentage and why does it matter for a menu?, How should you price a menu using both plate cost and target margin?. See how PlateCostr helps you recipe food-cost and menu margin calculator.

The Conversions That Break First

Weight and volume are the usual culprits. A recipe that calls for eight ounces of an ingredient is ambiguous unless the record says whether that is eight ounces by weight or eight fluid ounces, and the two are only the same for water. Oils, syrups, creams, and reductions all carry a different density, so a costing sheet that treats fluid ounces as weight ounces will be off on every batch. The second common break is purchased weight versus usable weight. You buy a case at one price, but after trimming, peeling, or draining you are plating far less than you paid for, and only a yield factor stored on the ingredient keeps the plate cost honest when the pack changes. Related: How should you price a menu using both plate cost and target margin?

Then there are the items that never had a fixed pack to begin with. Catch weight proteins arrive at whatever the individual pieces weigh that day, so the case price and the pound price move independently. Produce cases vary in fill by season. Frozen seafood carries a glaze that is water you paid for by the pound. Canned goods list a total weight and a drained weight, and only one of them ends up on the plate. Any of these can shift without a price change at all, which is exactly why a costing system built on case prices rather than base unit costs slowly stops telling the truth.

Catch It on the Invoice, Not on the Monthly P and L

The habit worth building is small: when an invoice comes in, read the pack and size column before you read the money. Most distributor invoices print the pack description right next to the item, and a change there is easier to spot than a change buried in a per-case price. Three questions handle nearly every case. Did the pack description change from the last delivery of this item? Does the unit price track with the case price, or did only one of them move? Was anything substituted because the usual item was unavailable? A substitution is the most common quiet source of a new pack size, because it is a one-time swap that nobody records.

Receiving is where this gets caught or lost. If whoever signs at the back door only checks counts against the sheet, a different pack sails through because the count is right. Give receiving one extra instruction: note any item where the pack description does not match what was ordered, and pass that note to whoever owns costing. It takes seconds and it saves the archaeology later, when you are staring at a food cost that moved three points and trying to reconstruct which of forty invoices caused it. Keeping the last few weeks of invoices somewhere searchable makes that reconstruction survivable when you do need it.

Build Recipes So a Pack Change Is a One Line Fix

The structural fix is to stop storing dollars inside recipes. An ingredient should exist once, with a purchase price, a pack size, a base unit, and a yield percentage. Recipes then consume quantities of that ingredient, not amounts of money. When the pack changes, you edit the ingredient record once and every recipe, sub-recipe, and finished plate that touches it recalculates. Compare that with a spreadsheet where the cost per ounce was typed by hand into each recipe tab. In that setup a single pack change is a find and replace exercise across the whole book, which is why it usually does not happen at all. Related: How do you protect margins when ingredient prices keep rising fast?

Pair that structure with a re-cost pass you actually run. After a price file update or once a month, recalculate the whole menu and sort by percentage change in plate cost rather than by dollar amount. Small dollar moves on high volume items matter more than they look, and a large percentage jump almost always points at a pack or yield problem rather than a genuine market swing. Anything past a threshold you set, five percent is a reasonable starting line, gets opened and checked against the invoice. This is the loop we designed PlateCostr around, but the discipline matters more than the tool: one source of truth per ingredient, and a scheduled look at what moved. Related: What is food cost percentage and why does it matter for a menu?