Food Cost Control for Restaurants in Nigeria

Food cost control is really margin control

Food cost control is often discussed as if it were a kitchen problem, but the commercial problem is margin. If a restaurant in Nigeria sells a plate, a bowl, or a combo meal at a price that no longer matches ingredient cost, prep waste, and production volume, the outlet is not really selling food at a profit. It is selling revenue and hoping the cost side stays quiet.

That is why prime cost discipline matters. Prime cost is the direct food cost plus labour cost that sits closest to the sale. If food cost is already too loose, labour usually follows because the kitchen needs more people, more hours, and more firefighting to keep the line moving. Operators who focus only on the selling price miss the real issue. The problem is not just what the guest pays. The problem is what it takes to produce the item at a controllable cost.

For a broader control framework, this article works best alongside recipe and BOM management for Nigerian restaurants and menu engineering for Nigerian restaurants. Those two pieces explain how the menu is costed and how the best items are priced. This article focuses on the operating discipline that keeps the numbers honest.

Prime cost discipline has to be visible every week

Prime cost discipline begins with a simple habit: measure food cost and labour cost together, not as separate excuses. A kitchen that is overspending on proteins, oil, garnish, and waste may not look alarming if labour is temporarily low. But once labour hours rise to cover the chaos, the outlet has a full prime cost problem. The business then pays for the same inefficiency twice.

The cleanest model is to build a weekly food cost view from actual purchases, opening stock, closing stock, transfers, wastage, and sales. This gives management a current picture instead of a delayed report. The same week should also show labour by department or shift, because the production team and the service team usually move together. If one side is broken, the other side will soon feel it.

The discipline should be easy enough for managers to use daily but strong enough for finance to trust. If the kitchen says a dish is under control and the stock count says otherwise, the system needs a third view: receiving, issuing, and production records. That is the only way to stop the same loss from being explained three different ways.

Recipe costing must use actual quantities and actual yield

Recipe costing is the base layer of food cost control. If the recipe is not scaled, measured, and recosted, every other control is built on guesswork. The recipe should list the exact raw quantity, yield loss, trimmed or cooked quantity, and cost per sellable portion. A vague recipe can still produce a tasty dish. It cannot produce a reliable margin.

In Nigerian kitchens, the biggest problems usually come from unit confusion and yield drift. A cook may buy tomatoes in baskets, issue them in crates, and serve the final base by spoon. A protein may be purchased whole, cut into portions, and plated in a way that changes the usable yield every week. Once the yield moves, the actual food cost changes even if the sales price stays the same.

Use the same logic for sauces, soups, rice, proteins, garnishes, and side items. A dish may look like it has one major cost, but the small components often carry the real leak. Oil, stock cubes, pepper, wraps, garnish, and delivery packaging can quietly change the economics of an item that management thought was stable.

For the control process around this, review recipe and BOM management. Recipe costing without BOM discipline is just a spreadsheet. It is not control.

Supplier variance is where inflation and leakage meet

Supplier variance is the gap between what the business expected to pay and what it actually paid. In Nigeria that gap can come from inflation, pack-size changes, grade differences, transport charges, substitutions, or a supplier quietly changing the quality of the item while keeping the product name the same. If the restaurant does not track that movement, the menu price will lag reality.

Variance should be tracked by item, not as one mixed number. The cost movement on tomatoes is not the same as the movement on rice. Imported cheese is not the same as local chicken. A kitchen that treats all supplier changes as one bucket loses the ability to answer the real commercial question: which ingredients are breaking the margin and why?

Variance control also improves procurement decisions. If two suppliers sell what looks like the same item, the better supplier is not the cheaper one on invoice. The better supplier is the one with the stable yield, reliable fill rate, and fewer hidden costs after delivery. That is the commercial test that matters.

Menu pricing should protect the target food cost, not follow hope

Once recipe cost is accurate, the menu price should follow a target food cost percentage or a target gross margin. The restaurant can choose the commercial rule, but it must choose one deliberately. Some operators use a target food cost percentage for each item class. Others use contribution margin by dish type. Both can work if they are applied consistently and reviewed often enough.

In the Nigerian market, the biggest pricing mistake is to update one or two visible items while leaving the rest of the menu on old numbers. Guests quickly notice the gaps. More importantly, the back office still has an old cost base. That means the restaurant has only adjusted part of the problem. The rest keeps leaking through volume.

Menu pricing should also reflect operating reality. A dish that drives a lot of prep, waste, or staff handling should not be priced as if it were simple. If the business wants to stay competitive, it can use bundles, smaller portions, or controlled specials, but those decisions must be modelled from actual cost first. This is where menu engineering for Nigerian restaurants becomes useful because it shows which items deserve protection and which items need redesign.

For commercial visibility, compare your operating assumptions with Staycore pricing so the business thinks about margin as a system, not as an afterthought.

Stock movement has to match the recipe and the sale

Stock movement is where food cost control either holds or falls apart. A restaurant can have excellent recipes and still leak if receiving, issuing, transfers, wastage, and returns are not recorded properly. Every item that enters the store should be able to move through the system with a visible reason attached to it. If stock can disappear from receiving to production without a trail, the business has already lost control.

In practical terms, food cost control means the store issues stock to the kitchen only against an approved need. The kitchen should then record prep usage, leftovers, and waste. Any transfer to another outlet or event should be signed off. Any return to the store should be captured as a return, not left to memory. These steps sound administrative only until the first variance review shows a pattern.

• Separate receiving, issue, waste, and transfer records.
• Use the same unit of measure in the store, kitchen, and POS report.
• Review the highest-value items every day or every shift.
• Reconcile production output against sales before the next service period.

This is also where broader controls matter. Pair the process with restaurant inventory management in Nigeria and inventory and assets so the outlet, the store, and finance are looking at the same movement story.

Production planning is how the kitchen stops overproducing

Many Nigerian restaurants lose money not because they underprice, but because they overproduce. Prep happens before demand is visible, batches are too large, and the kitchen cooks to a fear of shortage rather than to a real sales forecast. That creates leftover food, accelerated spoilage, and hidden labour cost on items that never sell.

Production planning should begin with sales patterns by day, daypart, and outlet. A lunch-heavy location should not prep the same way as a dinner-led venue. A weekday service should not use the same batch size as a Friday or Sunday rush. The production sheet should show the item, forecast quantity, batch size, par level, and the person responsible for approval.

Good production planning also reduces staff stress. If the team knows what to prep, when to prep it, and how much to hold, service becomes faster and waste falls. The kitchen is then less likely to “just cook extra” because the plan already exists. The right amount of production is not a guess. It is a controlled response to predictable demand.

For a service-side companion to this process, use the logic in the daily closing checklist for restaurant managers so the day ends with a clear handover, not a memory exercise.

How to implement food cost control without slowing service

Start with the items that carry the most volume or the most margin risk. In most Nigerian restaurants, that means rice dishes, protein-led mains, soups, oils, popular sides, and any item that is frequently discounted or bundled. Do not try to rebuild the entire menu on day one. Pick the top-selling items and the biggest variance items first.

Build a weekly review pack that shows sales, recipe cost, supplier variance, stock movement, waste, and production output. Make one manager accountable for the pack and one finance owner accountable for the numbers. If no one owns the review, the control process will drift into the background after the first busy week.

1. Recost the top-selling recipes from current supplier prices.
2. Check landed cost and yield for every core ingredient.
3. Set menu prices from target food cost or contribution margin.
4. Track issues, waste, returns, and transfers daily.
5. Plan production from forecast covers, not from habit.

The goal is not to create a heavy process. The goal is to make the kitchen easier to manage and the margin easier to defend. When the store, kitchen, finance, and POS data all line up, food cost stops being a surprise and becomes a decision. If you want to operationalise that control layer, talk to Staycore or review the inventory and assets module for the system side of the workflow.