A practical food cost framework for Dubai restaurants

Why food cost percentage is still the best single metric

Most restaurant operators know their food cost percentage — or think they do. In practice, the number reported at month-end rarely reflects what actually happened in the kitchen. Purchases are logged late. Waste goes unrecorded. Staff meals are charged to the wrong cost centre. By the time the P&L lands, the number is already too old to act on.

Food cost percentage (FC%) remains the clearest lever an operator has. A restaurant running at 35% in a market where prime sites carry 28–32% targets is effectively leaking 3–7 margin points that compound every month. For a venue doing AED 500,000 monthly in food revenue, the difference between 30% and 35% is AED 25,000 — every single month.

The 28–32% target in Dubai context

Dubai's food service market has specific cost pressures: imported ingredient premiums, high-turnover staff affecting portion discipline, and a culture of generous portioning that guests have come to expect. The 28–32% range is not arbitrary — it is the band that, combined with typical Dubai lease and labour costs, allows a full-service restaurant to reach EBITDA margins that justify reinvestment.

Quick-service concepts can operate at the lower end or below. Fine dining may push above 32% intentionally when the average spend justifies it. For everything in between — casual dining, polished casual, upscale-casual — 28–32% is the target zone.

The four variance categories you need to track

Food cost variance is the gap between your theoretical cost (recipe cost × covers sold) and your actual cost (opening stock + purchases – closing stock). Most operators measure the gap but do not decompose it. Decomposition is where the money is.

1. Waste and spoilage

Fresh produce, proteins and dairy are the biggest offenders. Waste can be legitimate (trim loss, prep waste) or operational (over-ordering, poor rotation). Both should be logged separately. Legitimate waste is priced into your recipe cost; operational waste is a training and process failure.

2. Portion drift

Recipes exist on paper. What happens on the pass is different. A burger patty specified at 180g costing AED 8.50 served at 200g costs AED 9.44 — an 11% silent overrun on that line item. Multiplied across 300 covers per day, it adds up faster than most operators realise. Regular portion audits (weigh 10 random plates per service, three times per week) catch drift before it becomes habitual.

3. Recipe drift

Menus evolve, but the recipes in the system often do not. A sauce that used to call for 30g of a premium ingredient but now uses 45g in practice will never show as a problem unless your recipe is updated and your team re-trained. Recipe drift is insidious because it feels like improvement — "we make it better now" — while quietly destroying margin.

4. Theft and unrecorded consumption

It is uncomfortable to discuss, but shrinkage from theft — whether by staff or at the receiving dock — is real in every operation above a certain scale. The signal is consistent variance on specific high-value items (proteins, spirits, premium produce) that cannot be explained by waste or drift. Unexplained variance on these SKUs warrants a receiving audit.

Daily vs monthly review cadence

Monthly food cost reviews are better than nothing. They are not good enough.

A monthly review tells you something went wrong. A daily review tells you what went wrong and gives you enough time to correct it before the month is lost.

Daily: Compare yesterday's recipe-out (theoretical consumption by recipe) against the items that actually moved. Any item where actual > theoretical by more than 5% gets flagged. Takes five minutes with the right system.

Weekly: Variance by category (waste, portion, recipe). Review with kitchen leadership. Set targets for the coming week.

Monthly: Full period inventory reconciliation. Theoretical vs actual by item. Sign off on the number before the P&L is produced, not after.

The tools you actually need

You do not need complicated software to start. You need:

• A recipe costing model where every dish has a costed bill of materials, updated when supplier prices change.
• An invoice-first purchasing log so every delivery is recorded at actual cost, not estimated cost.
• A daily waste log — a simple form, ideally digital, that kitchen staff complete at end of service.
• A period inventory process where the same people count the same locations on the same day each period.

The operational discipline matters more than the software. Once the process is consistent, a system like EYP Ops can automate the variance calculation and push it to a dashboard — but the process must come first.

Starting point

If you are not tracking food cost daily, start with a weekly review of your top 10 cost items. Identify which three have the most variance. Fix those three. Then expand. Trying to fix everything at once fixes nothing.