Restaurant inventory management starts with three connected jobs: order what you need, check what arrived, and count what is left. Different people often do each job. A purchase order, receiving checklist, and physical count need to carry the same item and pack-size context across those handoffs. Recipes help estimate usage between counts, but they cannot establish what the delivery contained or what is actually on the shelf.
This guide is for an independent restaurant or small group establishing reliable stock records. It covers recipe estimates, ingredient targets, physical counts, supplier changes and receiving evidence. Use the restaurant purchasing hub for vendor setup and the broader buying process.
For a practical sequence to try with a shift team, use the order, receive and count walkthrough. It connects the purchasing record, delivery check and physical stock count before the next buyer orders.
Quick answer
Restaurant inventory management connects ordering, receiving, physical counts, waste records, and the next replenishment decision. Recipe mappings can translate POS sales into estimated ingredient usage. Receiving records actual deliveries; counts check actual stock. Treat those as separate inputs rather than assuming a recipe estimate or an invoice proves what is on hand.
Closed-loop procurement adds the missing supplier side: supplier replies, substitutions, price changes, receiving variance, and accounting handoff stay attached to the living PO instead of drifting into email, prep notes, and AP cleanup.
1. Recipes are the load-bearing object
Recipe mappings can estimate ingredient consumption from recorded menu sales. Validate them against actual portions, yields and counts; they do not observe every physical movement.
For each menu item, your recipe should specify:
- Every ingredient, including the small ones (salt, pepper, garnish)
- Ingredient quantity and usable yield, with an explicit conversion to the purchase and count units
- Substitutions if any are pre-approved
- The POS-side product ID so sales decrement the right ingredients
The yield matters more than people realize. If your turkey sandwich actually uses 110g of turkey but the recipe says 100g, actual use is 10% above the recipe estimate (the estimate understates actual use by about 9.1%). Over time that can mean more turkey demand than your forecasts ordered, which can create stockouts, rush orders, and margin compression. Spend time weighing actual servings; it pays back through better inputs.
For a package conversion, divide ingredient quantity by package size using the same unit. A 1.5 kg flour bag contains 1,500 g; a recipe using 23 g consumes 23 / 1500 ≈ 0.01533 bags, before any separately modeled loss. That package fraction is different from a usable-yield percentage. Do not apply the same loss twice.
2. Set PAR levels per ingredient, not per dish
For dishes prepared from ingredients, plan the ingredient requirements rather than treating each finished dish as a supplier item. Purchased finished goods can instead be tracked directly in their purchase units.
For each ingredient, compute the consumption rate by summing across all recipes that use it:
ingredient consumption rate = Σ (recipe sales rate × recipe yield for this ingredient)
Add any direct-use consumption (e.g. flour used to dust pans, separate from a specific recipe). Review recorded waste and any modeled decay allowance for perishables without counting the same loss twice. Neither a recipe estimate nor a decay model establishes food safety or extends an expiry date.
The PAR level then follows the standard formula:
PAR = base demand over cycle + statistical safety stock + manual buffer
Include the time until the next review and replenishment, then check storage capacity and the usable life of actual lots. See PAR level and the weekly café example for the planning assumptions.
When recipe estimates are incomplete
Variable specials, catering and frequently changing prep can make fixed recipe mappings less useful. Document another way to plan those ingredients, such as event requirements and usable counts. Avoid presenting a precise consumption estimate when its inputs are missing.
Clean purchasing records remain valuable: item, supplier, location, accepted quantity, price and receipt. Purchase spend is not automatically food consumed in the same period. Finance determines inventory valuation and COGS treatment using the relevant stock and transaction evidence. The food-cost guide explains the management calculation and its assumptions.
3. Daily counts vs weekly counts vs cycle counts
You don't need to count everything every day. The right cadence depends on the item. The following is an illustrative starting schedule, not a food-safety inspection schedule or an industry benchmark; adjust it to value, variance, criticality and local procedures.
| Reason to review count frequency | What to inspect |
|---|---|
| High value or repeated variance | Whether more frequent checks reveal a correctable issue |
| Critical ingredient with little coverage | Whether the next count occurs before the buying deadline |
| Perishable or short usable life | Actual lot condition and stock available for planned use |
| Frequent receipts and transfers | Whether movements are recorded correctly between counts |
| Stable stock with reliable records | Whether a less frequent cycle count still supports the required accuracy |
Agree the schedule with the responsible operator and finance team. Item category alone does not establish how often a count is sufficient, and an inventory count is separate from required safety checks.
Keep the count tied to a clear item list and location. In LineNow, filter the inventory, print a count checklist, and scan its QR code to open that same list on a phone. Enter quantities in packs or units, review them, and apply the counts to inventory. The checklist helps carry the physical check back into the stock record before the next order.
4. Supplier roster: build for redundancy
Consider a qualified backup for critical items where the continuity benefit justifies the additional minimums, qualification and relationship work.
Reasons:
- Single-supplier dependence can reduce negotiating options and increase disruption exposure.
- Stockouts on the supplier side become stockouts on your side. A backup helps only if it has suitable stock, capacity and delivery timing when needed.
- Different suppliers carry different specialty SKUs. Locking to one means missed opportunities.
For critical ingredients, retain current supplier packs, price references, ordering routes and available alternatives. Compare total cost, suitability, capacity and delivery timing before switching; use the dual-sourcing guide to evaluate the backup.
5. Recipe costing: the dynamic margin view
One useful menu metric is revenue remaining after ingredient and packaging costs. For each menu item:
Margin after ingredients and packaging = Net menu revenue − ingredient cost − packaging cost
This excludes other variable costs such as delivery commissions and payment fees, so it is not full contribution margin or net profit. The trick is that ingredient cost moves. Your last shipment of avocados came in 18% higher than the previous one. Your recipe still costs the old number unless you re-cost.
When ingredient prices change, review which price is proposed, accepted or actually recorded for the relevant stock. A latest quoted cost, replacement-cost estimate and accounting inventory cost can differ. Specify which basis the recipe calculation uses before interpreting the margin.
Ask the software vendor to demonstrate a changed price and its effect on the configured recipe-cost view. Do not assume every extracted supplier proposal should immediately become an accepted cost or an accounting posting.
6. How should an establishment handle ingredient substitution?
Record a supplier's proposed substitute against the original item and have the authorized kitchen or quality owner approve suitability before use. Pack size, yield, allergens, dietary claims, labeling and storage requirements can differ even when the supplier calls it equivalent.
For one-time substitutions, preserve the actual received item and its unit conversion. Do not assume a bag of one product equals a bag of another or silently pour the substitute into the original stock pool. Update the recipe or approved substitution mapping where needed, communicate the change to the kitchen and retain the cost difference.
For permanent switches (you're moving from one supplier or brand to another): update the recipe ingredient mapping. Keep both items in the system (you may switch back). Track the cost difference; sometimes a permanent switch was made for availability reasons but costs more, and that's margin you didn't budget.
A common reason operators get this wrong is that the substitution is communicated by the supplier in an email, then forgotten by the time the truck arrives. The substitution gets received as the original item, the inventory drift starts, and the margin difference gets buried. A closed-loop procurement platform can catch the substitution when the supplier's email arrives: supported message processing proposes an update, the buyer reviews the substitute, and the receiver can see the approved expectation and any unresolved issue before accepting the delivery.
7. Receiving: check the delivery against the order
Receiving is one place where stock records can diverge from physical quantities. The truck shows up, things get put away, the receiving sheet doesn't get checked. By Wednesday, your inventory says you have 4 cases of strawberries but you have 2 (or 6).
The discipline, using LineNow's receiving checklist:
- Print the checklist from the purchase order. It includes item and pack details, ordered quantities, and quantities already received or still due.
- Check what arrived. Mark full quantities or record the partial quantity rather than assuming the entire PO was delivered.
- For locations receiving through LineNow, scan the checklist's QR code to open phone receiving without a login. Attach the invoice, packing slip, or delivery photos to that order.
- Review the checked quantities and submit the receipt. A document upload alone is not confirmation that the physical goods arrived.
If your receiver is also your prep cook, make the handoff explicit: who checks the delivery, where they record differences, and who follows up on missing items. A later stock count answers what is left; it should not be the first indication that a delivery was short.
8. The waste log
Record waste by item, unit, quantity, time and reason. Keep spoilage or breakage distinct from intentional uses such as staff meals and complimentary dishes. Those uses still consume stock, but combining them all as waste obscures the operating cause.
Before applying a usage adjustment, check whether the event already depleted stock through the POS or another record. Otherwise the same consumption may be deducted twice. Review repeated losses alongside prep quantities, storage, portions and receiving evidence; do not assume a waste log automatically calibrates the software's decay settings.
9. Reconcile counts with recorded movements
Agree count timing and period-end requirements with finance. For the same item, unit, location and period, reconcile opening stock plus receipts, inbound transfers and returns, less recorded consumption, waste, outbound transfers and other adjustments. Avoid subtracting overlapping consumption records twice.
Compare that expected balance with the physical count. Unexplained variance is a reason to investigate missed movements, recipe errors, conversion errors or loss; it is not proof of theft. Use consistent denominators when comparing variance percentages across periods.
10. Test the connected stock cycle
Use one ingredient and follow it through a count, a reviewed order, a supplier change, a partial receipt and the next count. Have another shift explain what is on hand, what is expected and what remains unresolved. Then ask finance to trace the corresponding invoice or credit.
LineNow connects configured demand inputs, purchasing drafts, supported supplier messages and receiving context. Validate actual POS records, recipe mappings, units and update timing rather than assuming every workflow follows a daily or nightly schedule.
Agree record ownership, transfer timing, mappings and correction handling with finance. Preserve commitments, partial receipts and later credits rather than waiting for one final order state.
Review current pricing for the base subscription, required add-ons and trial scope. The result to test is whether the buyer, receiver and finance reviewer can use consistent evidence while retaining their own decisions.
Related
- Closed-loop procurement, in plain English
- Multi-Location Restaurant Procurement: Location-Level Planning
- Procurement Software for Florists — a related example of purchase-spend management with explicit accounting boundaries
- PAR Level — the formula
- Decay rate by category
- Why Your Invoice Never Matches Your PO
- What Is a Living Purchase Order?
- Three-Way Matching vs. Living POs
- LineNow vs MarketMan, vs MarginEdge, vs WISK AI
- PAR Level Calculator