When an ingredient is suddenly unavailable: a substitution plan

How a shortage becomes an allergen incident

Shortages rarely announce themselves. In a short r/restaurantowners post, an owner asked whether there was a snow pea shortage, after struggling to get them from both an Asian specialty supplier and a cash-and-carry store. In another, an owner asked what others were paying for wings and where they bought them, comparing prices and fresh versus frozen options. Both records are search excerpts. They show that availability and price can move across channels at once. They don't confirm any market-wide shortage.

The kitchen's natural reaction is to grab whatever is close. Snow peas become sugar snaps or green beans. Fresh plain wings become a frozen product. Most of the time that's harmless. The risk is in the swaps nobody thinks about: a frozen wing that comes pre-breaded, a replacement sauce made with sesame oil, a different brand of bun with a different label. If the dish's allergen information stays the same while the recipe changes, servers will give guests wrong answers with confidence.

Build a shortage-prone items list from your own history

Don't try to plan for every ingredient. Make a list of 10 to 20 items using three filters. Which items have run short or spiked in price in the past year, according to your invoices and the outages your cooks remember? Which items come from a single supplier or a single manufacturer? Which are seasonal or weather-sensitive produce? Add any item a signature dish depends on, even if it has never run short.

For each item on the list, note who supplies it now, any second source, the usual lead time, and how many days of stock you normally keep. That last number tells you how much warning a shortage gives you before you're out.

Pre-approve substitutes and record what changes

For each listed item, choose one or two substitutes and test them in the actual dish. Record more than taste. Note any change in cooking time, yield or portion, cost, the ingredient label and allergens, and whether the dish can keep its menu name. The decision is made once, calmly, by the chef. On a busy Wednesday, the line follows the matrix rather than improvising.

The matrix below is an illustration of the format, not a recommendation for your menu. The allergen column must be filled in from the actual labels of the products you'd buy, not from general assumptions about what a product usually contains.

The allergen recheck, and what the model code says

Allergen rules for restaurants come from the food code your state or locality has adopted, plus any local allergen laws. The FDA Food Code is a model offered for adoption by jurisdictions. It isn't automatically local law. FDA's Food Code 2022 page lists a resource titled "Addition to the 2022 Food Code - Sesame added as a Major Food Allergen," and FDA's summary of changes for that edition notes added information on the federal Food Allergy Safety, Treatment, Education, and Research (FASTER) Act of 2021. FDA has since published a 2026 edition of the Food Code. Don't assume your jurisdiction has adopted either edition. Ask your local health department which edition and which allergen provisions apply to you. In the District of Columbia, that's DC Health.

Whatever your local rules require, the operational logic is the same. A substitute is approved only after someone compares its full ingredient label with the original's and updates every place the dish's allergen information lives: the recipe card, the allergen matrix, the server reference sheet, online menus, and delivery app listings. If a delivered product differs from the approved substitute, for example a different brand, it goes back through the same label check before use. Keep the labels on file.

• Compare the substitute's ingredient label with the original's, line by line, before first use.
• Update the recipe card, allergen matrix and server sheet the same day.
• Update online menus and delivery app listings if the allergen profile or description changes.
• Brief the shift at pre-shift: what changed, in which dishes, and what to tell guests.
• When the original returns, reverse every update and record the dates.

Worked example: a wing shortage with a breading trap (hypothetical)

Every number here is invented. A pub sells about 400 wing plates a week at $14.00, each using 1 lb of raw plain wings. Its supplier's price on fresh wings jumps from $2.40 to $3.30 a pound, and supply is unreliable. At $2.40, wings cost about 17.1 percent of the plate price ($2.40 ÷ $14.00). At $3.30, they cost about 23.6 percent ($3.30 ÷ $14.00). Absorbing the extra $0.90 a plate for a week costs about $0.90 × 400 = $360.

A cook finds a frozen wing product that's available and cheaper, and suggests switching. Its label lists a wheat-based breading and soy. Under the pre-approved matrix, it isn't an approved substitute. The approved substitute is frozen plain wings of a similar size. With that rule in place, the swap is caught before the first fryer basket, rather than after a guest who avoids wheat orders the "naked" wings they've eaten safely before.

On price, the pub's written rule says it holds the price for up to two weeks while cost stays within $1.00 a pound of baseline, then reviews. Here the $0.90 increase is inside that limit, so the price holds and the owner re-checks the following week. The rule is an internal choice, not a benchmark. The point is that it was decided before the shortage.

Telling guests honestly

Guests mostly accept a substitution they're told about, and resent one they discover. Use the lightest notice that's accurate. If the substitute is equivalent and the menu wording is still true, a server note is enough for guests who ask. If the menu names the missing ingredient, either change the text or have servers tell guests before they order. And if the allergen profile changes, update the written allergen information and make sure servers raise it with any guest who mentions an allergy.

Don't leave a claim on the menu that the substitute makes false. "Fresh wings" served from a frozen product, or "snow pea stir-fry" served with green beans, are small inaccuracies that can grow into a credibility problem. Online and delivery menus are easy to forget, so check them as part of the change.

Pricing during a shortage

Decide in advance which of three responses you'll use for each listed item. You can absorb the cost temporarily, within a dollar or percentage limit and a time limit. You can make a temporary price change or show the item at market price, clearly labeled. Or you can pull the item until supply returns. Absorbing works for short spikes on low-volume items. A temporary price change suits longer spikes on items guests will still buy. Pulling the item fits when the substitute doesn't meet your standard or the cost would make the dish unsellable.

Write down the threshold and the review date, and record which response you chose and when. Without a rule, the shortage is decided by whoever is ordering that day, and the menu ends up with a price that was raised during a spike and never brought back down.

Failure modes and records to keep

The failures are consistent: line cooks improvising substitutes under pressure, allergen information that stays the same while the recipe changes, delivery app menus forgotten, temporary prices that become permanent, and no record of when the original came back. Keep the matrix, the labels for each substitute, a dated log of each substitution and reversal, and notes on the pricing decision. Review the shortage-prone list every quarter.