Discovering at end-of-month stock count that actual food cost is 4 points above target -- but having no way to identify whether the variance came from waste, over-portioning, theft, or supplier price increases?
Supplier invoices entered manually into a spreadsheet because the inventory system doesn't connect to purchasing -- so cost of goods is always a lagging estimate, not a current number?
Restaurant Inventory Management Software
Food cost is the most controllable cost line in a restaurant -- and most operators discover their food cost variance at the end of the month, too late to act on it, because inventory and recipe costing aren't connected to their POS in real time.
We build inventory systems where stock depletion is calculated from POS sales using actual recipe data, supplier prices update recipe costs automatically, and food cost variance is visible daily rather than after the month-end count.
Real-time stock depletion calculated from POS sales using recipe data
Recipe costing updated automatically when supplier prices change
Automated supplier ordering from reorder points or count results
Waste and variance reporting with reason codes and daily food cost visibility
RaftLabs builds custom restaurant inventory management software for independent restaurants, restaurant groups, and multi-site operators. Custom inventory software is the right choice when your food cost variance is discovered at month-end rather than daily, when recipe costing isn't connected to actual supplier prices, or when stock counts and purchase orders live in separate spreadsheets. Most restaurant inventory projects ship in 12 to 14 weeks at a fixed cost with full source code ownership and integration with your existing POS.
Real-timeStock depletion
·RecipeCost accuracy
·FixedCost delivery
·12-14Week delivery cycles
Restaurant inventory software built to close the gap between theoretical and actual food cost
Food cost variance is a profitability problem, and most restaurants manage it too slowly. A monthly stock count tells you the variance but not the cause. By the time the count is done, invoices reconciled, and the number calculated, four weeks of the problem have already been paid for. The operators who control food cost most tightly are the ones who see variance daily and can ask the right question -- was it waste, over-portioning, a supplier price change, or a theft pattern -- before it compounds.
The change that makes daily food cost visibility possible is connecting three data sources that most restaurants hold separately: POS sales data, recipe costing data, and supplier pricing data. When those three are integrated, the system can calculate what the kitchen should have used based on what the POS recorded selling, compare it against the physical count, and produce a variance report at the end of each service. The gap between theoretical and actual food cost becomes a daily management number rather than a monthly surprise.
What we build
Stock management and counts
Ingredient-level stock tracking with unit of measure management covering kilograms, litres, each, and portion units. Scheduled stock count workflow with variance flag comparing the counted quantity against the expected on-hand quantity calculated from opening stock, deliveries received, and POS depletion. Spot count capability for high-value or high-theft items between full counts, without running a complete count across all lines. Storage location tracking across walk-in, dry store, freezer, and bar so count teams work one location at a time. Stock transfer between locations for multi-site operations with transfer confirmation at both ends so stock in transit is recorded correctly.
Recipe costing and menu engineering
Recipe-level cost calculation using actual supplier prices, with cost per portion and gross margin per menu item updated automatically when a supplier invoice price changes. Recipe yield factors for prep loss -- trimming, cooking loss, reduction -- so the theoretical cost reflects what is actually used rather than the raw ingredient weight. Sub-recipe support for prep items used across multiple dishes, where the cost of a base sauce or a marinated protein flows into every dish that uses it. Menu engineering view showing contribution margin and volume by item to identify the high-profit, high-volume combinations worth promoting and the low-margin, low-volume items worth removing or repricing.
POS-integrated real-time depletion
Ingredient depletion calculated from POS sales in real time using recipe data, so each item sold reduces the theoretical on-hand quantity for every ingredient in that recipe. Theoretical usage compared against the physical count at the end of each service or day to produce a variance report without waiting for a manual count. High-variance ingredients flagged for investigation, with variance expressed in quantity and value so the team knows which variances are worth chasing. Depletion by meal period -- breakfast, lunch, dinner -- to identify when in the day the variance is occurring rather than only the daily total. Integration approach confirmed during scoping based on your existing POS system and its API capabilities.
Supplier purchasing and ordering
Supplier catalogue with contracted prices and order multiples per ingredient so purchase orders reflect the units your supplier delivers in. Purchase order generation from reorder points set per ingredient or from the results of a manual count, with one-click order creation rather than spreadsheet assembly. Supplier order delivery by email or EDI depending on the supplier's preferred method. Delivery receipt confirmation with price and quantity variance capture at the point of receiving -- if a supplier delivers short or invoices above the contracted price, the system records it immediately. Supplier invoice matching against purchase orders for accounts payable reconciliation. Price change alert when an invoice price differs from the contracted price so you know when costs have moved.
Waste and transfer logging
Waste log with reason code per entry -- spoilage, prep error, quality rejection, overproduction, staff meal -- so waste value can be analysed by cause rather than as a single number. Staff meal and internal transfer logging to exclude these from food cost calculations without removing them from the stock movement record. Waste value by reason code reported daily and weekly so managers can see whether waste is concentrated in one category, one time of day, or one team. High-waste items and high-waste days identified in the reporting view so the investigation starts in the right place. Waste reduction trend tracking against a baseline period after a process change is made.
Food cost reporting and analytics
Daily and weekly actual food cost percentage against the theoretical cost calculated from POS sales and recipe data. Variance breakdown by ingredient and by recipe so the food cost number is explained rather than just reported. Supplier cost trend analysis with price inflation tracking across your main ingredient categories, showing which cost increases are driving margin compression. Period-on-period comparison by site for multi-location operators so the operations manager can see which locations are managing food cost well and which need attention. Food cost reporting integrated with sales data from the POS for an accurate gross profit view per service period, not only a cost percentage.
Frequently asked questions
When a menu item is sold through the POS, the system looks up the recipe for that item and deducts each ingredient quantity from the theoretical on-hand stock level. For a dish that uses 200g of beef fillet, 50g of butter, and a portion of a prep sauce, all three are depleted at the point of sale. This happens continuously through the service. At any point during or after service, the theoretical on-hand quantity for every ingredient can be compared against the physical count to produce a variance number. The quality of the depletion depends on recipe accuracy -- portion weights and yield factors need to be set correctly in the recipe database for the theoretical usage to match reality. We build the recipe setup process into the onboarding workflow so the data foundation is correct before go-live.
In most cases, yes. Cloud-based POS systems with open APIs -- Square, Lightspeed, Toast, and others -- can be integrated directly so sales data flows to the inventory system without manual export. Accounting integration with Xero or QuickBooks is a standard component: purchase orders, delivery receipts, and invoice data post to the accounts payable workflow without re-entry. Legacy or proprietary POS systems may require a middleware layer depending on what data they export. We confirm the integration approach during project scoping. If you are considering a POS replacement alongside the inventory project, we can scope both together so the systems are designed to work as a unit from the start.
Most dishes have a standard recipe with fixed quantities per portion, and the system uses these as the basis for depletion and costing. For dishes where quantity varies by cover -- a shared board, a build-your-own dish with multiple modifier paths -- we model the recipe with the average portion weight or build separate recipe variants per modifier combination, depending on which produces a more accurate cost. The key constraint is that theoretical depletion is only as accurate as the recipe data. We discuss the variable-quantity dishes in your menu during scoping and agree on the modelling approach before build starts. Most menus have a small number of genuinely variable dishes and a majority of fixed-portion items.
A restaurant inventory system covering stock management and counts, recipe costing, POS-integrated depletion, supplier ordering, waste logging, and food cost reporting typically falls in a fixed-cost range confirmed after a scoping session. The main variables are the number of locations, the complexity of the recipe database, the number of POS and supplier integrations, and whether accounting integration is required. We provide a fixed cost and delivery timeline after a single discovery session where we understand your current stock control process, your POS system, your supplier relationships, and where your food cost variance is coming from. Most restaurant inventory projects deliver in 12 to 14 weeks.
Talk to us about your restaurant inventory project.
Tell us your current stock control process, your POS system, and where your food cost variance is coming from. We will scope a system built around your operation.
