Connect recipe demand, physical counts, supplier orders, receiving and food-cost review while keeping perishability and safety controls distinct.
Jainul Vaghasia/Published /Updated /11 min read
For software buyers
Evaluate the workflow, not only the feature list.
LineNow is built for teams that need purchasing recommendations, purchase orders, supplier replies, receiving, and accounting handoff to stay connected.
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 covers the end-to-end loop: setting PAR levels for perishable ingredients, building recipes with accurate yield, doing daily and weekly counts, managing supplier relationships, and tracking COGS as ingredient prices move. It assumes you're running an independent or small-chain operation — the playbook is different for a 200-unit national.
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.
Read before ordering
A dense operator briefing for teams that need sharper buying, cleaner supplier follow-up, and fewer expensive surprises.
1. Recipes are the load-bearing object
A major leverage point in restaurant inventory is your recipe sheet. Get the recipes right and ingredient consumption can flow automatically. Get them wrong and every downstream number becomes suspect.
For each menu item, your recipe should specify:
Every ingredient, including the small ones (salt, pepper, garnish)
Yield per serving, in the same unit you order in (or with a clear conversion)
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 yield calculations, the LineNow rule of thumb: recipes per package = total package size / amount used per recipe. A 1.5 kg flour bag with 23g per recipe = 65.22 recipes. The yield stored in the system is 1/65.22 = 0.01533 bags per recipe. Decrement accordingly.
2. Set PAR levels per ingredient, not per dish
This is the most common mistake in early restaurant inventory: thinking in terms of finished dishes rather than ingredients. Your supplier doesn't deliver sandwiches. They deliver flour, turkey, and lettuce.
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.
2.5. When you intentionally do not track every perishable unit
Not every perishable business should pretend every input is worth tracking at the unit level.
One operator in a recent customer call described the floral version of this problem:
"Whatever we purchase in fresh flowers for the month is our cost of goods sold."
That customer describes an operating approach, not a general accounting rule. Purchase spend can be a useful management proxy when item-level usage is difficult to track. Finance still needs to determine the appropriate inventory and COGS treatment, including material beginning and ending stock. The quotation is not an independently audited financial result.
Restaurants can hit a similar edge case with highly variable specials, garnish-heavy menus, catering events, or prep programs where the recipe changes constantly. The team can distinguish two management views:
Recipe-tracked mode: ingredients decrement through fixed recipes, recipe margins update as supplier prices change, and PAR levels are computed from POS sales.
Procurement-spend mode: purchases are tracked cleanly by supplier, category, location, and time period, while COGS is trued up from actual spend and period-end counts or accounting policy.
The workflow still matters in procurement-spend mode. You still need to know what was ordered, what arrived, what the supplier changed, which location consumed the spend, and whether the bill matches the latest PO. The difference is that the system should not force fake precision where the operator has intentionally chosen a period-based COGS method.
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.
Item type
Counting cadence
Why
High-cost proteins (steak, fish)
Daily, end of shift
Theft and waste are concentrated here; high $/unit
Liquor (bar program)
Weekly minimum, daily for premium spirits
Over-pour and shrink are systemic
Fresh produce
Twice weekly (delivery days)
Decay-driven; counts at receipt and mid-cycle
Dairy, eggs
Twice weekly
Mid-perishable; sealed but cold-chain dependent
Dry goods (rice, beans, pasta)
Weekly
Stable, low-decay; weekly is enough
Cleaning supplies, paper goods
Bi-weekly
Slow-moving; risk is running out, not waste
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 each ingredient, store at minimum: primary supplier's price, secondary supplier's price, last-12-months pack-size and price history. When a primary increases price, compare current alternative availability, total cost and required approvals.
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.
The right system re-costs recipes when ingredient prices change, surfaces the new margin, and flags items that have crossed below your target. Without this, you may find out about margin erosion at the end of the month, after the cost has already moved.
LineNow can update recipe cost as new prices are captured from supplier emails and invoices. The margin column on your menu items can stay current to the latest supplier-confirmed and received state, not just the last manual update.
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: Layer 1 AI parses the reply, the living PO gets a reviewable update, the receiving record can be pre-loaded with the substitute, and the cost difference is captured before AP sees the bill.
7. Receiving: check the delivery against the order
The act of receiving inventory is when most counts get out of sync. 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
Track waste. All of it. Spoilage, breakage, comps, employee meals, mistakes. Tag each event with quantity, item, and reason. Over a quarter you'll see patterns: a particular protein spoils more, a specific shift has more breakage, certain dishes get comped disproportionately.
The waste log feeds the decay-rate estimate. With a clean log, decay rates can be derived directly rather than guessed. Without it, you're estimating from gap analysis (count discrepancies) which conflates waste with theft and counting error.
9. The end-of-month closeout
Every month, regardless of how clean your daily process is, do a full count. Compare against expected (starting + receipts − sales − comped − waste). The unexplained variance is a signal to investigate; it may include missed transfers, recipe errors, count errors or loss. It is not proof of theft.
Set a variance target using your own comparable count history, item value and process requirements. Record the numerator and denominator so percentages can be compared. If variance rises, investigate counting, receiving, recipes, transfers and waste before attributing a cause.
10. The end-to-end loop, summarized
POS connects to inventory; sales decrement ingredients via recipes
PAR levels per ingredient, recomputed daily from rolling consumption
Replenishment recommendations generated nightly; operator reviews in the morning
POs sent to suppliers through configured supported channels
Confirmations parsed into structured updates; status updated; price changes flagged
This is what restaurant inventory looks like when it works. Many steps can be automated or assisted, but the deciding and the touching still matter. The deciding gets a recommendation; the touching — counting, receiving, tasting, checking quality — is the operator's job.
LineNow is a closed-loop procurement platform for restaurants — meaning a system where the buying loop stays connected, including supplier-reply parsing that catches substitutions and price changes before they hit your invoice. Recipe builder with substitution and dynamic margin recomputation, decay-aware PAR for perishables, multi-vertical support if you also run retail or packaged goods, supported Toast / Square / Clover POS workflows, and configured QuickBooks/Xero handoff. Confirm the base subscription, required add-ons and trial coverage in current pricing.
For an independent restaurant or small group where supplier execution is the bottleneck, LineNow is a strong procurement system to evaluate.
