The food and beverage business is a margin business. Revenue sounds good, but if your food cost is running at 38% when it should be 30%, the 8% gap is the difference between a profitable operation and one that's struggling despite busy tables.
Most F&B businesses know what their revenue is. Far fewer know their actual food cost percentage at the menu item level — and even fewer can tell you whether that number is improving or getting worse month to month.
ERP doesn't make a restaurant run better by itself. But it gives you the data to see exactly where your margins are going, and that visibility is the prerequisite for fixing the problems.
Recipe Costing: The Foundation
Recipe costing is the process of calculating exactly what it costs to produce each menu item. You list every ingredient, in the exact quantity used per portion, at the current purchase price. The sum is the theoretical food cost for that item.
Without a system, recipe costing is a spreadsheet that gets updated occasionally when someone remembers and usually doesn't reflect the most recent supplier price changes. In practice, it's often built once during the opening and then quietly abandoned.
With ERP, recipe costing is live. The standard recipe for your soto ayam specifies: chicken thigh 200g, lemongrass 10g, turmeric 5g, rice 150g, and ten other ingredients. Each ingredient is linked to your inventory with its current purchase cost. When the price of chicken increases — and in Indonesia, it does regularly — the recipe cost updates automatically. You don't need to rebuild the spreadsheet to know that your food cost just moved.
This is the data that drives pricing decisions. If the theoretical food cost for a dish is Rp 18,500 and you're selling it at Rp 45,000, your gross margin is 59%. If chicken prices rise and the cost becomes Rp 23,000, that margin drops to 49%. You need to know that in order to decide whether to adjust the price, find a substitute ingredient, or accept the margin reduction.
Ingredient Inventory with Expiry Tracking
Fresh ingredient inventory is fundamentally different from retail or manufacturing inventory. Items expire. A kg of chicken breast received on Monday may be unusable by Thursday. Vegetables have even shorter windows.
ERP inventory with expiry tracking assigns a use-by date to each received batch of perishables. The system surfaces items approaching expiry so they can be used before they're lost. This reduces spoilage from the most common cause: ingredients that were in the walk-in but nobody knew how old they were.
For businesses sourcing from multiple suppliers — which most larger F&B operations do — batch tracking also enables traceability. If a food safety issue arises with a specific ingredient, you need to know which batch was received from which supplier, when, and which menu items it was used in.
The Gap Between Theoretical and Actual Cost
This is where ERP delivers one of its most operationally important insights for F&B businesses: the variance between theoretical food cost and actual food cost. Tracking this gap is closely connected to broader ERP reporting and KPI tracking — cost variance is one of the metrics that belongs in a weekly operational review, not a monthly one.
Theoretical food cost is what you should have spent on ingredients based on the number of dishes sold and their standard recipes. Actual food cost is what you actually spent on ingredients based on purchasing and stock consumption.
The gap between these two numbers — the variance — tells you where your operation is losing margin.
A variance of 2-3% is generally acceptable, reflecting normal portion variation and minor waste. A variance of 8-10% is a serious problem. Possible causes: over-portioning (staff plating more than the standard recipe), waste from poor inventory management, theft, inaccurate recipes, or receiving errors where you paid for more than you got.
Without ERP, calculating this variance requires a manual stock count, a manual reconciliation of purchasing records against recipes, and a calculation that most F&B businesses do quarterly at best. With ERP, it's a weekly or even daily report.
Identifying a 6% variance and fixing it — by correcting portion control, reducing waste, or tightening receiving procedures — can add several points of margin without changing a single price on your menu.
Automatic Reorder for Consistent Supply
Running out of a key ingredient during service is one of the most damaging things that can happen in an F&B operation. An 86'd (unavailable) dish disappoints customers and loses revenue. Running out during a busy Lebaran weekend when suppliers may have limited availability is worse.
ERP reorder automation sets minimum stock levels for each ingredient. When kitchen stock of chicken breast drops below, say, 10 kg, the system generates a purchase alert or an automatic purchase order to the approved supplier. Your purchasing team doesn't need to manually check the walk-in — the system tells them what to order before you run out.
For ingredients with longer lead times — specialty imports, items that require advance ordering — the reorder point can be set higher to account for the delivery window.
Supplier Price Tracking
Ingredient prices in Indonesia fluctuate. Commodity prices for chicken, beef, and cooking oil move with market conditions. Seasonal vegetable prices vary significantly. Knowing that you paid Rp 32,000/kg for tomatoes in January and the same supplier is charging Rp 47,000/kg in February is information you need for both negotiation and recipe cost accuracy.
ERP maintains purchase price history by supplier and ingredient. When you raise a new purchase order, you can see the last price paid and the current quote. Price increases that would previously have silently eroded your margin are now visible at the point of purchase.
For businesses buying from multiple suppliers, comparing prices across them becomes straightforward. If Supplier A is consistently cheaper for certain ingredients and Supplier B for others, you can split purchasing accordingly — a level of optimization that's impractical without a system maintaining the price history.
Indonesian F&B Context
A few specific considerations for Indonesian F&B operations:
Halal ingredient tracking. For certified halal businesses, maintaining records of ingredient sourcing and halal certification status is a compliance requirement. ERP supplier management can track halal certification validity by supplier and flag when a certification is approaching expiry.
Lebaran demand planning. The annual demand surge around Eid al-Fitr creates an inventory planning challenge for F&B businesses. Historical sales data by period in ERP allows you to plan ingredient purchasing well in advance — buying before the pre-Lebaran price spikes that hit most commodity ingredients — rather than scrambling during the peak.
Multi-outlet recipe consistency. F&B groups with multiple outlets face a specific challenge: ensuring that the same menu item costs the same and tastes the same across all locations. Centralized recipe management in ERP ensures all outlets work from the same standard recipe and the same portion specifications.
The F&B businesses that control their costs well aren't necessarily the ones with the best recipes. They're the ones who measure what's happening, catch problems early, and adjust before the margin damage accumulates.
CERIS builds ERP systems for F&B businesses with recipe costing, ingredient inventory, and cost variance reporting designed for the operational realities of Indonesian food businesses. See what we build or get in touch to discuss what your operation needs.