Restaurant Recipe Cards US 2026: Complete Guide + Template

The short version. A restaurant recipe card is the document that tells you, for every dish: what goes in, how much it weighs, what it costs, and what allergens are present. Mandatory on the FDA allergen side (§3-603.11). Essential everywhere else to run your margins without guessing. The trap: a recipe card frozen in an 18-month-old spreadsheet is worth nothing. Here's how to make it a living tool.

What a recipe card is — and what it actually does for you

A restaurant recipe card is the kitchen's reference document. It records every dish, every base sauce, every shared side — with exact weights, cooking method, allergens present, and what it costs per portion at today's vendor prices. Without it, you cook on instinct. With a card frozen in old prices, you steer the restaurant on bad data. The difference is real dollars.

I've run kitchens in France and watched how US operators work. The pattern is consistent: everyone knows they need recipe cards, most have started them, and almost nobody keeps them updated. The cards exist. The prices are stale. The margin is a guess.

The 7 blocks of a complete US recipe card

A well-built recipe card fits on one page. The goal isn't to write a manual — it's to have an operational reference any BOH team member can read in 30 seconds.

Block 1 — Dish identification. Name, category (app, entrée, dessert, sides), number of portions per batch, expected yield, date created and last updated.

Block 2 — Ingredient list with US weights. Every ingredient with net weight in oz, lb, or fl oz (after trimming and breakdown). Gross weight separate — the difference is your yield loss, and ignoring it underestimates your actual cost per portion.

Block 3 — Current vendor price. Pulled from your active vendor price list. Not from six months ago. Today's price. If your broadliner just updated pricing, your cards need to reflect it.

Block 4 — Food cost per portion ($). Sum of all ingredients at net weight × current price per unit, divided by batch size. The number that runs your margin. Staying under 32% is the target for most casual dining dishes.

Block 5 — FDA 9 allergens. Milk, Eggs, Fish, Shellfish, Tree Nuts, Peanuts, Wheat, Soybeans, Sesame (added January 2023, FASTER Act). Every ingredient either carries an allergen or doesn't. The card documents what's present in the dish. This is the block health inspectors check under FDA Food Code §3-603.11.

Block 6 — Cooking method. Prep steps, cooking temperatures in °F, rest times. Essential for BOH consistency and for food safety traceability (cooking temps tie to FDA Food Code §3-401.11: poultry 165°F, ground beef 160°F, fish 145°F).

Block 7 — Selling price and food cost %. Menu price ex-tax, food cost as a percentage. If a dish is above 33-35%, you have a decision to make: reformulate, reprice, or remove.

How to build a recipe card in 5 steps

Building a card takes 20 to 45 minutes per dish from scratch. The challenge isn't creating them — it's keeping them current.

Step 1: Actually weigh ingredients. No estimating. No "about 6 oz of chicken." You weigh. You record net weight after breakdown. A 10 oz chicken breast with 15% trim loss actually costs you as if it were 11.8 oz. Across 80 portions a night, that math matters.

Step 2: Pull prices from your current vendor list. Each ingredient is tied to a vendor, a unit, and a current purchase price. This is where the card lives or dies. If you type a price by hand and don't update when Sysco or US Foods adjusts, your card lies.

Step 3: Calculate food cost per portion. Cost per portion = Σ (net weight in oz × price per oz) for all ingredients, divided by batch yield. Simple math, but it only works with current prices.

Step 4: Document the 9 FDA allergens. For each ingredient, identify which allergens are present. The card consolidates the allergens present in the finished dish. Changed sauce supplier? New dressing recipe? Allergens need to be reassessed. Full details on FDA allergen requirements.

Step 5: Set selling price and calculate food cost %. Food cost % = food cost per portion / net menu price × 100. Target: 28-32% for casual dining. Above 35%, you're working for your vendors.

Real case — La Verrerie, 2016

When I took over La Verrerie in 2015 — a hotel-restaurant in formal insolvency — I found 48 recipe cards in the office. Well-structured, complete, clean. Dated 2014.

I pulled every card. I went back through every ingredient with prices current as of early 2016. Result: 67% of ingredient prices were stale. On several dishes, the actual food cost was 18 to 24% higher than what the card showed. The restaurant had been pricing and serving these dishes at margins calculated against 18-month-old numbers.

The cards weren't badly built. They were frozen. Nobody updated them because it's a massive job to do manually — for each card, you have to find every ingredient, find the current price, recalculate. With 48 cards and a team running services, it doesn't happen.

That discovery planted the seed for Onrush. The tool had to do what nobody does manually: recalculate every card the moment a price changes.

The live cascade — why it changes everything

When your vendor raises chicken breast from $3.40/lb to $3.95/lb, two things happen. With a frozen card: nothing changes on paper, your displayed food cost is now wrong, and you find out at month-end when margins have eroded.

With a live price cascade: every recipe card that contains chicken breast recalculates instantly. You see which dishes are now above your food cost target. You decide immediately — absorb the price increase, reformulate, or raise the menu price. Same day. Before you run 400 covers at the wrong cost.

The cascade isn't a luxury feature. Once you have 20+ recipe cards and a vendor who adjusts prices every quarter (which every Sysco and US Foods account does), manual updates become structurally unmanageable.

US portion weight reference

US kitchens work in oz, lb, and fl oz. Here's a quick reference to keep recipe costs consistent:

Always use net weight — after trim, bone-out, peeling — not the gross weight you receive from the vendor. The difference is your yield percentage, and it directly affects your real food cost per portion.

How many recipe cards do you need?

Field rule: 1 card per finished dish + 1 card per base sauce + 1 card per base side.

A 25-dish menu typically needs 50 to 65 recipe cards. Your house ranch dressing used on 6 dishes? One card. When buttermilk prices change, you update one card and the 6 dishes recalculate. That's the cascade logic.

Recipe card: by hand, Excel, or software?

The workflow with software: scan your vendor invoice, OCR updates the prices in your vendor list, every recipe card containing those ingredients recalculates automatically. 5 minutes of invoice processing. Zero minutes of manual card updates. The inverse of the spreadsheet model.

Common mistakes US operators make on recipe cards

Mistake 1 — Ignoring yield loss. You receive 10 lb of trimmed beef. After butchering into portion-ready cuts, you have 8.5 lb. Your real cost is not $X/lb received — it's $X/lb divided by 0.85 yield. This calculation changes your food cost by 15-20% on protein-heavy dishes.

Mistake 2 — Building cards and never reviewing them. La Verrerie's mistake. A card built in 2023 with 2023 prices is wrong in 2026. With the price volatility US operators have seen since 2021, a card older than 6 months is suspect.

Mistake 3 — Making cards for main dishes only. Desserts, appetizers, shared sauces, and in-house condiments are often left out. A house burger sauce running at 40% food cost because nobody costed it — that drags your overall margin down silently.

Mistake 4 — Not linking recipe cards to purchasing. If your burger card says 5 oz ground beef net per portion and you're running 120 covers per service, you can calculate your weekly beef order within 5 minutes. That's the downstream value of recipe cards — they make your purchasing data-driven, not gut-feel.

Mistake 5 — Treating allergens as a checkbox. The FDA allergen on your recipe card needs to be tied to the ingredient — not hand-jotted at the bottom of the table. Switch sesame oil suppliers and the new product contains no sesame? That updates on the card. Miss that update and your allergen documentation is wrong even though it's "filled in."

Conclusion

Three takeaways from this guide.

1. A recipe card is a live tool or it's worth nothing. A card frozen for 18 months in a spreadsheet gives you the illusion of running things. In reality, you're making pricing decisions on stale data. I lived it at La Verrerie — 67% of prices stale. Dishes sold at wrong margins for a year and a half.

2. FDA allergens are not optional. 9 major allergens in 2026, including sesame since January 2023. Your recipe card is where allergen traceability is documented at source. If an ingredient changes supplier, the allergen information updates there — not on a table jotted in by hand afterward.

3. The Excel → software move isn't a luxury once you hit 15+ dishes. That's the threshold where manual upkeep becomes unmanageable. 5 minutes per card per vendor price change × 50 cards = 4 hours wasted. With a tool, it's 0 minutes.

Last updated May 2026. Written by Cyril Quesnel, founder of Onrush — 20 years on the line in France, two restaurant turnarounds, building food safety and food cost tools for US indie restaurants.