# Stockcount: Full Content > Stockcount is an AI-powered inventory management and food cost tracking tool for restaurants, cafes, and small food operations. It uses voice-powered counting, automatic receipt matching, and real-time COGS calculation to replace spreadsheets and manual data entry. > This is the extended version of [llms.txt](https://stockcount.io/llms.txt) with full blog post content. ## Product Overview Stockcount is built for solo restaurant owners and small teams who manage inventory without dedicated back-office staff. The core workflow: count inventory by voice, snap photos of receipts to log purchases, and the system calculates your actual food costs automatically. Key capabilities: - Voice-powered inventory counting: speak counts hands-free while walking the walk-in - AI receipt processing: photograph vendor invoices, the system extracts line items and matches them to your ingredients - Real-time COGS tracking: Beginning Inventory + Purchases - Ending Inventory, calculated after every count - Plate cost and contribution margin: define recipes, get per-plate costs and menu profitability - Smart cycle-counting: ABC classification prioritizes what to count each day - POS integration (Square, Toast): in development; will import menu items and support theoretical-vs-actual variance - Flat unit conversions: purchase units convert to counting units without nested packaging hierarchies Pricing: - Subscription required. No free tier. An active plan is needed to use Stockcount. - Starter: $19/month. The full single-location toolkit: voice counting, AI chat agent, invoice scanning, recipes, plate costs, shopping lists, variance + food-cost analytics, Square POS integration, team members, and 500 AI credits/month - Pro: $49/month. Everything in Starter plus multi-location dashboard, cross-location reporting, and 1,500 AI credits/month - Business: $149/month. Everything in Pro plus 5,000 AI credits/month, priority support, volume discounts on credit top-ups, and dedicated onboarding - Credit top-ups available à la carte; purchased credits never expire; auto-refill keeps you running uninterrupted; cancel anytime Website: https://stockcount.io ## Blog Posts ### Restaurant Prime Cost Formula & Benchmarks URL: https://stockcount.io/blog/restaurant-prime-cost Published: 2026-03-20 Keywords: restaurant prime cost, prime cost formula restaurant, restaurant prime cost benchmark, how to calculate prime cost restaurant, prime cost percentage restaurant, restaurant prime cost control, prime cost restaurant Most restaurant operators have a rough sense of whether they are making money. Prime cost replaces that feeling with a number, and it is the only number you need to check every week. ## The Formula Prime cost is your two largest controllable expenses combined: **Prime Cost = Cost of Goods Sold (COGS) + Total Labor Cost** As a percentage: **Prime Cost % = (COGS + Total Labor) / Total Revenue x 100** Our free [restaurant labor cost calculator](/tools/restaurant-labor-cost-calculator) runs this for you — enter labor cost, food cost, and revenue to get your prime cost percentage and a health check against the benchmarks below. COGS covers every ingredient and beverage that goes into what you sell. Total labor covers every dollar you spend on people: wages, salaries, payroll taxes, benefits, workers' comp, overtime. Together, these two categories typically account for 55-70% of a restaurant's revenue. Everything else (rent, utilities, insurance, marketing) is either fixed or much harder to change in the short term. Prime cost is where you have leverage. ### A Quick Example A casual restaurant does $25,000 in revenue last week: | Category | Amount | % of Revenue | | ---------------------- | ----------- | ------------ | | COGS (food + beverage) | $7,500 | 30.0% | | Total labor | $7,750 | 31.0% | | **Prime cost** | **$15,250** | **61.0%** | That 61% means 39 cents of every dollar is left to cover rent, utilities, insurance, equipment, marketing, loan payments, and profit. ### What Goes Into COGS [COGS](/blog/what-is-cogs-restaurant) is calculated from inventory counts, not invoices: **COGS = Beginning Inventory + Purchases - Ending Inventory** It captures what you actually consumed, not what you bought. This is why physical inventory counts matter. Without them, you are guessing. For a deeper breakdown, see [What Is COGS in a Restaurant?](/blog/what-is-cogs-restaurant) ### What Goes Into Total Labor Total labor is more than hourly wages. Include gross wages for all staff, salaried management, payroll taxes (FICA, FUTA, state unemployment), benefits (health insurance, 401k match, PTO), workers' comp, overtime, and any bonuses or tips paid by the house. A common mistake is using only the wages line from your payroll report. If your gross wages are $6,000/week, your actual labor cost is not $6,000. Payroll taxes, benefits, and workers' comp add a multiplier called your labor burden rate. At a typical 1.20x, that $6,000 becomes $7,200. Using the wrong number understates your prime cost by 3-5 points. How much the burden rate adds depends on what you offer. A QSR with no benefits might run 1.10-1.15x. A full-service restaurant with health insurance, PTO, and 401k match could be 1.25-1.35x. If you do not know yours, ask your payroll provider or accountant for the exact number. ## Industry Benchmarks These ranges are rough composites drawn from NRA reports, restaurant accounting platforms (Restaurant365, Toast, 7shifts), and operator surveys. Different sources disagree by a few points, so treat these as guideposts, not hard lines. The targets have held relatively steady for years, even as hitting them has gotten harder. | Restaurant Type | COGS Range | Labor Range | Prime Cost Range | | --------------------------- | ---------- | ----------- | ---------------- | | Quick-service / Fast casual | 25-30% | 25-30% | 55-60% | | Casual dining | 28-32% | 30-35% | 60-65% | | Fine dining | 30-35% | 30-38% | 62-68% | | Cafes and coffee shops | 25-35% | 28-35% | 55-65% | | Bars (beverage-focused) | 20-25% | 22-30% | 48-55% | **The general rule: prime cost should not exceed 65% for full-service, 60% for quick-service.** The honest context: according to the NRA's 2025 operations data, the median full-service restaurant spent [36.5% of sales on labor in 2024](https://restaurant.org/research-and-media/research/restaurant-economic-insights/analysis-commentary/elevated-labor-costs-had-a-significant-impact-on-restaurant-profitability-in-2024/), and operators reporting losses ran as high as 42.9%. Food costs remain [well above pre-pandemic levels](https://restaurant.org/research-and-media/media/press-releases/persistent-cost-increases-and-enduring-demand-will-shape-the-restaurant-industry-in-2026/). Many operators are running above these targets right now. If your prime cost is 67%, you are not failing. But you need to know the number and be working it down. ### What Different Levels Mean in Dollars For a restaurant doing $1.2M in annual revenue: | Prime Cost % | Prime Cost $ | Left for Overhead + Profit | Realistic Outcome | | ------------ | ------------ | -------------------------- | ------------------------------------------ | | 55% | $660,000 | $540,000 | Healthy margin. Room to invest. | | 60% | $720,000 | $480,000 | Solid. Typical for well-run casual. | | 65% | $780,000 | $420,000 | Tight but workable if rent is low. | | 70% | $840,000 | $360,000 | Barely breaking even. One bad month hurts. | | 75% | $900,000 | $300,000 | Losing money after overhead in most cases. | The difference between 60% and 70% on $1.2M revenue is **$120,000 per year**. ## The Split Matters More Than the Total A prime cost of 62% tells you whether you are profitable, but not where the money is going. Two restaurants can both run 62% with completely different problems: | | Restaurant A | Restaurant B | | -------------- | ------------ | ------------ | | COGS | 26% | 35% | | Labor | 36% | 27% | | **Prime cost** | **62%** | **62%** | Restaurant A has tight food cost but heavy labor: a scratch kitchen with a large prep team. Restaurant B has high food cost but lean labor: a premium-ingredient concept with counter service. If prime cost creeps up, Restaurant A investigates scheduling and overtime. Restaurant B investigates vendor prices and waste. This is also why [food cost percentage](/blog/how-to-calculate-food-cost-percentage) alone is misleading. A restaurant can have great food cost (28%) but terrible prime cost (72%) if labor is out of control. Switching from pre-made to scratch cooking might drop food cost by 3 points but add 5 points of labor. Food cost went down, prime cost went up, and you lost money. Always track the split. ## How to Calculate Prime Cost Weekly Monthly prime cost is an autopsy. By the time your accountant tells you last month was 68%, you have already lost four weeks of margin. Weekly tracking catches problems in days. **Step 1: Calculate COGS.** Count inventory on a consistent day (Sunday night or Monday morning). Pull your purchase invoices for the week. COGS = Beginning Inventory + Purchases - Ending Inventory. This week's ending inventory becomes next week's beginning inventory. (See [How to Calculate Food Cost Percentage](/blog/how-to-calculate-food-cost-percentage) for a detailed walkthrough.) **Step 2: Pull total labor.** Get your payroll summary for the week. Include gross wages, employer payroll taxes, benefits (prorate monthly premiums), and overtime. If you cannot get exact weekly numbers, multiply gross wages by your labor burden rate (typically 1.15-1.25x). **Step 3: Calculate.** Prime Cost % = (COGS + Total Labor) / Revenue x 100. Compare to last week. After four weeks you will have a trend. That is where the value lives. ## Two Weeks of Prime Cost: A Real Example A cafe doing about $12,000/week: **Week 1:** | | Amount | | ------------------- | ---------- | | Beginning inventory | $4,200 | | Purchases | $3,800 | | Ending inventory | $4,000 | | **COGS** | **$4,000** | | Total labor | $3,600 | | **Prime cost** | **$7,600** | | Revenue | $12,200 | | **Prime cost %** | **62.3%** | **Week 2:** | | Amount | | ------------------- | ---------- | | Beginning inventory | $4,000 | | Purchases | $4,500 | | Ending inventory | $3,800 | | **COGS** | **$4,700** | | Total labor | $3,650 | | **Prime cost** | **$8,350** | | Revenue | $12,400 | | **Prime cost %** | **67.3%** | Prime cost jumped 5 points. Revenue was flat, labor was stable. COGS spiked by $700. Because you track the split, you know exactly which side moved. Why did COGS jump? Possible causes: over-ordering for an event, vendor price increases you missed, a waste or portioning problem, a receiving error. Each has a different fix, but none gets diagnosed without the weekly number. That $700/week leak is $33,600/year. ## Common Mistakes **Using purchases instead of COGS.** Your invoices show what you bought, not what you used. Invoice totals alone do not give you food cost. You need [inventory counts](/blog/restaurant-inventory-counting-guide) to calculate actual COGS. **Ignoring seasonality.** A slow January might push prime cost to 68% even if your costs are unchanged, because fixed labor stays the same while revenue drops. Compare to the same period last year, not just last week. Expect prime cost to rise in your slow season. If it rises during peak season, something is wrong. **Cutting labor without watching revenue.** A kitchen that is understaffed during a rush does not save money. It costs you the customers who do not come back. You want the lowest prime cost that does not hurt revenue. ## When Prime Cost Is Too High: Levers You Can Pull Knowing your number is step one. Here is what to actually do about it, depending on which side is the problem. **If COGS is high:** - **Re-quote your top 5 items by spend.** Get competing bids from two other vendors. Protein and dairy alone often account for 40-50% of food cost. A 5% price reduction on your top five items moves the needle more than renegotiating everything. - **Track waste for one week.** Put a sheet and a bus tub next to the trash. Write down what gets thrown away and why. Most operators are surprised by what they find. Common culprits: over-prepped items that do not sell, produce that spoils before use, and proteins trimmed too aggressively. - **Check portioning.** Weigh ten random plates against your spec. Portion creep is invisible until you measure it. A burger that gains an extra ounce of protein over time costs you 6-8% more per plate, and nobody noticed. - **Audit receiving.** Verify that what shows up matches what the invoice says. Short deliveries, wrong items, and substitutions at higher prices are common and easy to miss if nobody checks. - **Compare what you sold to what you used.** Pull your POS product mix report for the week. Multiply each item sold by its recipe cost. That is your theoretical COGS. Compare it to your actual COGS. If actual is 3-5% higher than theoretical, the gap is waste, theft, or portioning errors. If it is 8%+, something specific is broken and you can usually find it by looking at your highest-volume items first. **If labor is high:** - **Cross-train staff.** A prep cook who can cover the line during a slow shift means you can cut one person without reducing capacity. Cross-training is a slower fix but the most durable one. - **Stagger shift starts.** If you open at 11 and the rush does not hit until 12, you do not need the full crew at 11. Shift your schedule in 30-minute increments to match actual demand. - **Review overtime.** Overtime is 1.5x labor cost and often avoidable with better scheduling. One employee working 48 hours costs more than two employees working 24 each, and you get more coverage. - **Compare labor to revenue by day.** Most restaurants over-staff on their slowest day and under-staff on their busiest. Plot labor cost against revenue for each day of the week. Rebalance toward the days that generate the most sales per labor dollar. - **Check your prep-to-sales ratio.** If you are prepping the same volume on a Tuesday as a Saturday, you are either throwing food away or overstaffing prep. Pull your sales by day of week and scale your prep pars to match. This also reduces waste on the COGS side. Over-prepping is where labor and food cost problems overlap. You do not need new software or a consultant for any of this. You need your prime cost number, which side is off, and one action this week. ## Making Weekly Tracking Stick Labor numbers come from payroll software automatically. COGS is where the habit breaks because it requires a physical count and invoice reconciliation. The pattern is predictable: you commit to weekly tracking, it works for three or four weeks, then a busy week hits and you skip one count. Now your beginning inventory for the next week is wrong too, so your COGS numbers are off for two weeks. At that point most people stop. The operators who actually sustain it do one of two things. Either they count a short list (just the top 20 items by cost, which typically cover 80% of COGS) or they make it someone's specific job on a specific day. A vague task like "count inventory" gets skipped. "Carlos counts the walk-in Sunday at 9pm" actually happens. Twenty minutes of counting once a week gives you the most important number in your business. Everything else in this article depends on it. --- ## Further Reading **Components of prime cost:** - [What Is COGS in a Restaurant?](/blog/what-is-cogs-restaurant). The COGS formula, with actual vs. theoretical variance - [How to Calculate Food Cost Percentage](/blog/how-to-calculate-food-cost-percentage). Step-by-step food cost calculation and weekly tracking - [How to Calculate Plate Cost](/blog/plate-cost-guide-restaurants). Per-dish cost analysis with menu engineering (Stars, Plowhorses, Puzzles, Dogs) - [Restaurant Inventory Counting: A Practical Guide](/blog/restaurant-inventory-counting-guide). The counting process that makes accurate COGS possible **Broader cost management:** - [Staying on Top of Your Restaurant Costs](/blog/staying-on-top-of-your-costs). Overhead, break-even, and margin management beyond prime cost - [Restaurant Food Cost Tracking with AI](/blog/restaurant-food-cost-tracking-ai). How AI removes the data-entry busywork from weekly cost tracking **External resources:** - National Restaurant Association, [_2026 State of the Restaurant Industry_](https://restaurant.org/research-and-media/media/press-releases/persistent-cost-increases-and-enduring-demand-will-shape-the-restaurant-industry-in-2026/). Annual cost trends and profitability data - NRA, ["Elevated labor costs had a significant impact on restaurant profitability in 2024"](https://restaurant.org/research-and-media/research/restaurant-economic-insights/analysis-commentary/elevated-labor-costs-had-a-significant-impact-on-restaurant-profitability-in-2024/). Source for the 36.5% labor cost figure - Restaurant365, ["How to Calculate Prime Cost in a Restaurant"](https://www.restaurant365.com/blog/how-to-calculate-prime-cost-in-a-restaurant/). Benchmarks from their platform data - 7shifts, ["Restaurant Prime Cost Guide"](https://www.7shifts.com/blog/restaurant-prime-cost-guide/). Labor-focused perspective on prime cost --- ## Sources - National Restaurant Association, [_2026 State of the Restaurant Industry_](https://restaurant.org/research-and-media/media/press-releases/persistent-cost-increases-and-enduring-demand-will-shape-the-restaurant-industry-in-2026/): food cost increases, operator profitability - NRA, ["Elevated labor costs had a significant impact on restaurant profitability in 2024"](https://restaurant.org/research-and-media/research/restaurant-economic-insights/analysis-commentary/elevated-labor-costs-had-a-significant-impact-on-restaurant-profitability-in-2024/): labor cost benchmarks (36.5% median for full-service, 42.9% for operators reporting losses) - Restaurant365, ["How to Calculate Prime Cost in a Restaurant"](https://www.restaurant365.com/blog/how-to-calculate-prime-cost-in-a-restaurant/): prime cost formula and benchmarks - Toast, ["Restaurant Prime Cost"](https://pos.toasttab.com/blog/on-the-line/restaurant-prime-cost): prime cost calculation and industry context - 7shifts, ["Restaurant Prime Cost Guide"](https://www.7shifts.com/blog/restaurant-prime-cost-guide/): prime cost benchmarks by restaurant type - NetSuite, ["11 Key Restaurant Benchmarks"](https://www.netsuite.com/portal/resource/articles/erp/restaurant-benchmarks.shtml): COGS and labor benchmarks by segment --- ### Stop Overcomplicating Unit Conversions URL: https://stockcount.io/blog/stop-overcomplicating-inventory-unit-conversions Published: 2026-03-19 Keywords: inventory unit conversion, restaurant inventory management, packaging conversions, inventory counting units, restaurant inventory system, food inventory tracking You buy a case of olive oil. The case has 6 bottles. Each bottle is 500ml. Your inventory tracks liters. Quick: how much olive oil did you just receive? If you had to pause on that, you've experienced the problem every restaurant inventory system creates for itself. And most of them make it worse, not better. ## The nesting trap Traditional inventory systems try to model the physical nesting of containers. A case contains 6 bottles. A bottle contains 500ml. So the system stores two conversions: - 1 case = 6 bottles - 1 bottle = 500 ml And then chains them together: 1 case = 6 x 500ml = 3,000ml = 3 liters. This feels thorough. It mirrors how the packaging actually works. But it creates problems. First, it's fragile. If your vendor starts shipping 4-packs instead of 6-packs, you need to update the case-to-bottle conversion, and every calculation downstream changes. If someone updates the wrong level, the math silently breaks. Second, it's unnecessary complexity. Your inventory doesn't care about bottles. You're counting liters of olive oil on the shelf. The only conversion that matters is: **1 case = 3 liters.** That's it. One number. No intermediate layers. ## The flat model The conversion you actually need is always the same shape: "what I bought" on the left, "what I count" on the right. | What I bought | What I count | | -------------------- | ------------ | | 1 case of olive oil | 3 liters | | 1 bag of avocados | 5 each | | 1 can of black beans | 425 grams | | 1 case of oat milk | 6 cartons | No tree structure. No intermediate entities. Just a single conversion factor per product-packaging combination. This is simpler to set up (one number instead of a chain), simpler to maintain (one number to update when packaging changes), and simpler to verify (does "1 case = 3 liters" look right? You can answer that without doing math). It also maps directly to how kitchen staff actually think. Nobody in a kitchen says "we received 6 units of 500ml." They say "we got 3 liters of olive oil." The flat model matches the mental model. ## Two types of purchases Once you flatten conversions, a more fundamental distinction becomes obvious: not all purchases even need a conversion. ### Fixed-packaging items A can of black beans is always 425 grams. A case of oat milk is always 6 cartons. A bag of sugar is always 2 kg. The conversion factor is stable. You learn it once, store it, and reuse it on every receipt. These are the easy case. First time you buy a product, you tell the system the conversion. Every subsequent purchase uses it automatically. ### Variable-weight items Bulk coffee beans weigh 1.32 lbs this week and 1.13 lbs next week. A piece of fresh salmon is 2.4 lbs one delivery and 1.9 lbs the next. A bag of limes from the farmers market has a different count every time. These items don't have a stable conversion factor. There is no "1 bag = X lbs" you can store and reuse. If you try, one of two things happens: 1. **The system pre-fills the wrong weight.** You bought coffee last week and the bag was 1.32 lbs, so the system assumes this week's bag is also 1.32 lbs. It's actually 1.13 lbs. Your inventory is now off by 14%. 2. **The system asks you to enter the weight every time.** Which means you're manually entering data that's already printed on the receipt. Both outcomes are worse than just reading the weight from the receipt and using it directly. The receipt says "1.32 Lbs @ $10.99/lb." The 1.32 lbs IS the inventory quantity. No conversion needed. No packaging card. No user input. The system should recognize that this is a variable-weight purchase and handle it on a different path. ## How to tell the difference The receipt itself usually tells you which type you're dealing with: - **"3 @ $5.99"** — Fixed packaging. 3 units at a per-unit price. Stable conversion. - **"1.32 Lbs @ $10.99/lb"** — Variable weight. A measured quantity at a per-unit-of-measure price. Use as-is. - **"12 CT"** or **"6 PK"** — Fixed packaging. A count is baked into the product. Stable conversion. - **"$14.47"** with no quantity breakdown — Ambiguous. Needs clarification the first time, but once the system learns the product, it knows. An inventory system that can make this distinction automatically saves you from the most common source of conversion errors: applying a fixed conversion to something that changes every time. ## Why this matters for accuracy Inventory accuracy lives and dies in the conversions. You can have perfect OCR, perfect product matching, and perfect receipt capture. If the conversion from "what I bought" to "what I count" is wrong, your inventory data is wrong. The nested model multiplies opportunities for error. Each layer in the chain is a place where a number can be wrong. And when a number IS wrong, it's hard to find because you have to trace through multiple levels. The flat model has exactly one place to be wrong. And it's easy to verify: does "1 case = 3 liters" look right? If it does, the conversion is right. If it doesn't, you change one number. ## The bottom line If you're building or choosing an inventory system, look at how it handles conversions. If it asks you to define packaging hierarchies (cases contain cartons contain units), it's over-engineering the problem. What you need: - One flat conversion per product-packaging combination - Automatic detection of variable-weight purchases - The ability to update a conversion when packaging changes That's it. The simpler the conversion model, the more accurate your inventory will be, because there are fewer places for errors to hide. --- ### From Receipt Chaos to Inventory Accuracy URL: https://stockcount.io/blog/receipt-chaos-to-inventory-accuracy Published: 2026-03-17 Keywords: receipt matching, inventory management AI, vendor product aliases, receipt OCR, restaurant inventory, food cost tracking, stockcount receipt processing Every time you shop at the same store, you make slightly different decisions. This week you grab a bag of five avocados. Next week you pick up three loose ones. Same ingredient, same store, but your receipt says two completely different things. "HEB BAG AVOCADOS 5CT" one week. "SMALL HASS AVOCADOS" the next. For inventory software that processes receipts, this is a deceptively hard problem. The strings look nothing alike. The units are different. The price-per-item math is different. But they're the same thing sitting on the same shelf, and your stock count shouldn't care how they arrived. Here's how we solved it. ## The Problem: One Ingredient, Many Faces Receipt text is chaotic. Stores abbreviate however they want, mix packaging details into product names, and change formats without warning. A single ingredient in your kitchen might show up on receipts as any of these: - HEB BAG AVOCADOS 5CT - SMALL HASS AVOCADOS - AVOCADO HASS EA - ORG AVOCADOS 4CT BAG A human glances at these and immediately thinks "avocados." Software has to work a lot harder. The naive approach is to match on keywords: if it says "avocado" somewhere, it's probably avocados. But that falls apart fast. "HEB ST AVOCADO OIL F" also contains "avocado," and it's a completely different product. Keyword matching creates false positives that silently corrupt your inventory data. The enterprise approach is to maintain a massive product catalog and map every possible receipt string to it upfront. That's what companies like Instacart and UberEats do with their Universal Catalog, a central database of canonical products with store-specific variants mapped by a combination of software and human review teams. It works, but it requires enormous upfront investment that doesn't make sense for a tool built for individual kitchens and small operations. We needed something that starts with zero knowledge and gets smarter with every receipt. ## The Architecture: A Learning Pipeline Stockcount uses a four-layer matching system that processes each receipt line item through progressively more expensive checks, stopping as soon as it finds a confident match. ### Layer 1: Exact Alias Match The first check is the fastest. We maintain a table of "aliases": every receipt string we've ever successfully matched to an ingredient. When "HEB BAG AVOCADOS 5CT" appears on a receipt and we've seen that exact string before, we know instantly that it's avocados, it came in a 5-count bag, and each avocado costs roughly what it cost last time. This is a simple database lookup. No AI involved. It resolves in milliseconds and handles the most common case: you buy the same things from the same store repeatedly. ### Layer 1.5: Fuzzy Alias Match Sometimes receipt strings change slightly between visits. A store might print "HEB BAG AVOCADOS 5CT" one week and "HEB BAG AVOCADO 5CT" the next, singular instead of plural. An exact match misses this. We generate a vector embedding for every alias when it's created. When an exact match fails, we run a similarity search against all known aliases for that vendor. A high threshold (0.92, tighter than general semantic search) catches trivial variations like pluralization, spacing, and abbreviation differences without false-matching across genuinely different products. This layer fires only when Layer 1 misses, and it's still fast: a single embedding generation plus a pgvector query scoped to one vendor's aliases. ### Layer 2: Ingredient Embedding Search If no alias matches (exact or fuzzy), the item is genuinely new to this vendor. We fall back to semantic search across all ingredients in your database. The receipt text "SMALL HASS AVOCADOS" gets embedded and compared against your ingredient catalog. Your existing "Avocados" ingredient scores high on similarity, and the system proposes it as a match. This is where the human enters the loop. The system presents the proposed match and asks you to confirm. If you confirm, a new alias is created, and "SMALL HASS AVOCADOS" is now permanently linked to your "Avocados" ingredient. Next time, Layer 1 handles it silently. ### Layer 3: Word Overlap Validation A safety net for Layer 2. When semantic search proposes a match, we validate that the receipt text and ingredient name share meaningful words. This catches cases where embeddings are misleadingly similar. Two strings might be close in vector space but refer to different things. ## The Key Insight: Aliases Carry Conversion Data Matching the receipt string to the right ingredient is only half the problem. "HEB BAG AVOCADOS 5CT" means 1 bag = 5 avocados. "SMALL HASS AVOCADOS" at $0.55 each means 6 individual avocados. The conversion from receipt units to your inventory's base unit (each, grams, milliliters) is different for each packaging format. In our system, each alias stores its own conversion data. When you first confirm "HEB BAG AVOCADOS 5CT" as avocados, the system asks: "What's inside the bag?" You say: 5 each. That conversion, `1 bag → 5 each`, is stored on the alias, not on a global conversion table. This matters because conversions are properties of specific packaging formats, not of ingredients in general. A bag of avocados contains 5. A bag of limes might contain 6. If you store "1 bag = 5" globally, it eventually applies to the wrong product. Scoping the conversion to the alias eliminates that class of bug entirely. The second time "HEB BAG AVOCADOS 5CT" appears on a receipt, the system knows the ingredient (Layer 1 match), knows the conversion (5 each per bag), and knows the approximate cost (from the previous receipt). It processes the line item with zero interaction. ## The Lifecycle: Self-Managing Aliases Aliases aren't static. They evolve based on how you interact with the system. **Confidence builds over time.** Every successful auto-match increments a counter on the alias. An alias that has matched 15 times without being overridden is rock-solid. One that was just created is less certain. This implicit confidence tracking means the system can make smarter decisions as it accumulates history. **Mistakes are correctable in the normal flow.** If the system auto-matches a receipt string to the wrong ingredient, you override it during receipt review, the same screen you're already looking at. The old alias is deactivated (never deleted; we keep the history), and a new alias for the correct ingredient is created. No admin panel, no settings page. The correction happens where the problem is visible. **Re-confirmation reactivates.** If an alias was deactivated by mistake and the same receipt string appears again, the normal confirmation flow creates a new alias (or reactivates the old one if the mapping is the same). The system is self-healing. ## Naming the Ingredient, Not the Package One lesson we learned the hard way: if the canonical ingredient name includes packaging details, the matching system works against you. Early on, processing "HEB BAG AVOCADOS 5CT" produced an ingredient called "Avocados, Bagged 5ct." That name made sense for one receipt. But when "SMALL HASS AVOCADOS" came in the next week, the system saw "Avocados, Bagged 5ct" in the database and reasonably concluded this was a _different_ product. Small hass avocados aren't "bagged 5ct" avocados. So it got flagged as new, creating a duplicate. The fix was a naming convention enforced in the AI's system prompt: name the product, not the packaging. "Avocados" is an ingredient. "Bagged 5ct" is a property of how HEB sells them, which is exactly what the alias captures. The ingredient name is what you see when counting stock or building a recipe. "Avocados" on a shelf tells you what to count. "Avocados, Bagged 5ct" tells you something about a receipt you processed last month, which isn't useful when you're standing in front of a shelf with a clipboard. Qualifiers earn their place in the ingredient name only when they affect how you count or cook. "Black Beans, Dried" vs. "Black Beans, Canned". Those are different items on different shelves with different uses in recipes. "Chicken Breast, Boneless Skinless" tells a cook something important. "Chicken Breast, 3-Pack" does not. This convention maps to how the best restaurant inventory tools work. MarginEdge, the industry leader for restaurant back-of-house software, uses the same separation: "Vendor Items" are the raw invoice strings (unique per vendor), and "Products" are the generic, countable items you track in inventory and use in recipes. One Product can have many Vendor Items across different vendors and packaging formats. They explicitly recommend using the product's full, generic name, not a shorthand, and not packaging details. ## Cost Intelligence Per Format A side benefit of the alias architecture: cost tracking per packaging format comes almost for free. Since each alias records a cost entry every time it matches a receipt, we can show you that bagged avocados from HEB cost $0.60 per avocado while loose ones cost $0.80 each. Over time, this builds a rolling price history per format. Not just "what did avocados cost" but "what did avocados cost _in each way I buy them_." On the ingredient detail page, this looks like: > **Avocados** (base unit: each) > > HEB BAG AVOCADOS 5CT | 1 bag → 5 each | $0.60/each (last: Mar 10) > > SMALL HASS AVOCADOS | individual | $0.80/each (last: Mar 17) You can see at a glance whether the bag is actually a better deal, how prices trend over time per format, and whether switching vendors or packaging saves money. This is purchasing intelligence that most inventory tools, consumer or professional, don't offer at this level of granularity. ## The Data Model For those interested in the technical structure, here's how the entities relate: **Ingredient** is the canonical item: "Avocados." It has a base unit (each, grams, or milliliters), a category (Produce), and this is what appears in your stock list, recipes, and reports. One ingredient can be purchased from multiple vendors in multiple formats. **IngredientVendor** represents the relationship between an ingredient and a vendor: "HEB sells Avocados." It stores the canonical cost and vendor-specific metadata like brand and preferred status. **VendorProductAlias** is the receipt string: "HEB BAG AVOCADOS 5CT." Each alias belongs to one IngredientVendor and stores its own conversion data (1 bag → 5 each), a vector embedding for fuzzy matching, lifecycle data (match count, active status, last matched date), and the latest cost. **AliasCostEntry** is the price history: one entry per receipt encounter, recording the unit cost, receipt quantity, converted quantity, and line total. This powers the per-format cost trends. The key relationship: one Ingredient → many IngredientVendors → many VendorProductAliases → many AliasCostEntries. Each layer adds specificity without complicating the one above it. ## The Flywheel The most important property of this system is that it gets better with use. Every receipt you process adds aliases. Every confirmation teaches the system a new mapping. Every override corrects a mistake. The 5th receipt you process requires a lot of interaction. Most items are new, most aliases haven't been created yet. The 50th requires much less. The 200th is nearly silent. That's the trajectory we designed for: an app that feels like work the first week and feels like magic by the third month. --- _Stockcount is an AI-powered inventory management tool that processes receipts through a conversational interface. It's designed for kitchens and small food operations that want professional-grade cost tracking without enterprise complexity._ --- ### How Smart Cycle-Counting Works URL: https://stockcount.io/blog/stockcount-smart-counting Published: 2026-03-12 | Updated: 2026-03-17 Keywords: smart inventory counting, cycle counting restaurant, ABC inventory classification, restaurant inventory app, stockcount smart counting Most independent restaurants and small-to-medium operations today still use clipboards or static spreadsheets as a checklist when doing physical inventory counts. Count everything, every week. That's a big waste of labor. This leads to overcounting certain items that don't really need to be counted as often. The best way to decide what needs to be counted on any given day during physical inventory counts is to use a structured cycle counting approach. Cycle counting keeps operations running smoothly while maintaining (or improving) accuracy. Most businesses who are serious about tracking inventory rely on **_ABC analysis_** (based on the Pareto Principle, a.k.a. 80/20 rule) as the primary method to prioritize and schedule daily counts. A lot of businesses use inventory apps, like Stockcount, to handle the technical details of managing a cycle count automatically. But, in a restaurant (especially a small-to-medium sized cafe, independent spot, or full service place without fancy software), a structured cycle counting approach using just clipboards, printed sheets, and basic organization is completely doable. And, many places still run this way successfully. It won't be as "smart" or automatic as the Stockcount app, but it can achieve **_very high accuracy_** if done consistently. The Stockcount app handles all these details automatically, so if you don't care so much about this, and just want an easy interface that continually updates your list for you, then I recommend you give the app a try. But, for those of us who are curious about how things work, or just want to implement this the old-fashioned way, this article is for you. First, let's talk about how to implement a structured cycle counting system using just clipboards: ## Step 1: Do a One-Time ABC Classification (Paper or Simple Spreadsheet) This is the foundation. Do this once every 3 to 6 months. - **A items** – High impact (~10-20% of your items, but ~70-80% of your total food cost). These are expensive proteins, premium liquor, high-volume perishables, coffee beans, or dairy in a busy cafe. - **B items** – Medium impact (~20–30% of items, ~15–20% of cost). Think cheese, ground beef, onions, pasta, mid-range produce. - **C items** — Low impact (50%+ of items, ~5% or less of cost). Salt, sugar, spices, bulk flour, napkins (if you track them at all). ### Build Your ABC List Manually Gather your last 3-6 months of supplier invoices (or POS sales reports if you have them). You don't need perfect data, just good enough to rank your items. 1. **_Make a master list on Paper/Google Sheet/Excel_**. List all ~50–150 regular SKUs with these columns: | Item Name | Unit | Approx. Monthly Usage | Unit Cost | Total Monthly Value | ABC Class | | -------------- | ---- | --------------------- | --------- | ------------------- | --------- | | Chicken Breast | case | 20 | $52 | $1,040 | A | | Whole Milk | gal | 40 | $4.50 | $180 | B | | Toothpicks | box | 2 | $3 | $6 | C | 2. **_Estimate Approx. Monthly Usage_** (the tricky but doable part): - **From invoices** (best method): Add up total units purchased over 3–6 months, then divide by the number of months. Example: 12 cases × 40 lbs/case = 480 lbs over 4 months → 120 lbs/month. - **From menu knowledge** (quick alternative): Estimate based on top-selling dishes. Example: Sell 80 burgers/day × ⅓ lb patty = ~27 lbs ground beef/day → ~810 lbs/month. Ask your chef: "How many cases of lemons do we typically go through in a week?" - **Shortcut if records are messy**: List high-cost items (steaks, seafood, premium booze) and high-volume staples (milk, bread, eggs). Anything you worry about for cost, theft, or spoilage goes in A. The rest sorts itself. 3. **_Sort the list by Total Monthly Value_** descending (highest $ impact on top). - On paper: Re-write or highlight in order. - In Sheets/Excel: Sort the Total column → calculate running total/cumulative % if you want precision. - Draw lines: Top ~80% cumulative value = A items; next ~15% = B; rest = C. (Common restaurant split: 80/15/5 or 70/20/10—adjust to fit your menu.) 4. **_Write A/B/C next to each item._** Make three clean lists (one page each for A, B, C) and laminate or sheet-protect them for reuse. Re-do this every 3–6 months as menus, prices, or seasons change. ## Step 2: Set a Simple Counting Calendar Print a monthly wall calendar or add it to your clipboard cover. Assign frequencies based on class. - **A items**: Count **daily** or **every other day** (many spots do proteins/seafood/booze every close to catch issues fast). - **B items**: Count **2–3 times per week** or **weekly**. - **C items**: Count **weekly** or **bi-weekly** (or save for monthly full sweeps). If you have task checklists for your staff, modify them to include conditional counting rules. Here are some practical examples: - **Daily quick A-count + rotating zones** (most popular for busy kitchens): - Every day: All A items (10–20 items, 10–25 min). - Rotate zones: Mon = walk-in proteins/dairy; Tue = produce; Wed = dry storage; Thu = freezer; Fri = bar/liquor. - **Weekly ABC rotation** (simpler for smaller spots): - Week 1: All A + half B. - Week 2: All A + other B + some C. - **Tiny cafe version**: Daily top 5–10 proteins/produce/booze; Sunday full everything else. Post the schedule visibly so the team knows the plan. ## Step 3: Create Reusable Count Sheets Print/laminate sheets for your clipboard - Header: Date / Day / Counter Name - Columns: Item Name | Physical Count | Variance/Notes (e.g., "spoiled 2 lbs", "found extra case") Color-code: Red for A, yellow B, green C. ## Step 4: Daily Execution Routine 1. Assign counter (manager, chef, closing lead—rotate to share load). 2. Low-activity time: Post-close or pre-open. 3. Count physically: Weigh bulk, count cases + partials, estimate pans (e.g., ¾ full mashed potatoes ≈ 15 lbs). 4. Record, quick variance check, note reasons. 5. Adjust orders/pars based on real counts. 6. File sheets in a monthly binder; log variances in a notebook for patterns. ## Step 5: Monthly Review + Full-ish Count - One slow day/month: Count A + B + problem C items fully. - Review variances: Fix root causes (over-portioning? Theft? Waste?). - Celebrate wins: Lower food cost creep = more profit. ## Bonus: Train Your Team for Consistency - Train counters on accurate methods (weigh bulk, use visual guides for partial pans, double-check high-value). - Rotate who counts to spread knowledge and reduce theft risk. - Set a goal: Aim for <2–3% variance on A items. - Review sheets weekly in a quick team huddle. And there it is, a clipboard system that organizes and prioritizes your inventory management efforts. But, if this feels like too much manual work (re-classifying quarterly, estimating usage, rotating schedules), Stockcount automates it all: rolling ABC from your sales/purchases, daily prioritized lists with perishability and variance boosts, and mobile voice counting. --- ### Staying on Top of Your Restaurant Costs URL: https://stockcount.io/blog/staying-on-top-of-your-costs Published: 2026-03-11 | Updated: 2026-03-19 Keywords: restaurant cost management, independent restaurant costs, food cost control, restaurant financial management, how to manage restaurant costs **TL;DR:** Wholesale food costs are up over 35% from pre-pandemic levels ([NRA 2026 State of the Industry](https://restaurant.org/research-and-media/media/press-releases/persistent-cost-increases-and-enduring-demand-will-shape-the-restaurant-industry-in-2026/)). Customers are cutting back. You can't fix the economy, tariffs, or minimum wage hikes. You **can** fix your own numbers. Track prime cost weekly. It's the single biggest lever you have. Stay lean inside your four walls or get buried. ## Part 1: The Operators Who Know Their Numbers Are the Ones Still Standing ### Who this guide is for Not for chains with controllers and Excel wizards. This is for you: the owner who's also line cook, GM, HR, and midnight invoice wrangler. No bookkeeper, no team. You're grinding solo. ### The numbers Wholesale food costs are up more than 35% since pre-pandemic ([NRA 2026 / BLS Producer Price Index](https://restaurant.org/research-and-media/media/press-releases/persistent-cost-increases-and-enduring-demand-will-shape-the-restaurant-industry-in-2026/)). Labor has seen similar increases. Utilities and occupancy are up double digits ([NRA/BLS data via Barmetrix](https://www.barmetrix.com/blog/restaurant-inflation)). 42% of operators reported their restaurant was not profitable in 2025 ([NRA 2026](https://restaurant.org/research-and-media/media/press-releases/persistent-cost-increases-and-enduring-demand-will-shape-the-restaurant-industry-in-2026/)). Meanwhile, 37% of diners are eating out less, with 69% citing rising prices ([YouGov 2025](https://yougov.com/en-us/reports/53193-us-dining-out-report-2025)). You already feel this. The question is whether you can _see_ it in your numbers, fast enough to act. ### What we'll cover - **What "knowing your numbers" actually means**: Key metrics, especially COGS where most independents bleed quietly - **Why tracking this stuff is painful and kills most operators** - **How to make it sustainable solo** with low-friction tools Goal: Chain-level visibility without hiring or dying on spreadsheets. --- ## Part 2: What Knowing Your Numbers Actually Means ### Prime Cost: The One Number That Tells You Everything Forget the full P&L. Obsess over **_prime cost_** weekly. Knowing your prime cost is more important than your P&L for feeling confident you're actually making money day-to-day. Prime cost = **COGS** (food & beverage cost) + **total labor** (wages, taxes, benefits, and all other payroll overhead). - **Target:** ≤60–65% of sales. Quick-service: aim 55–60%. Full-service: 60–65% max. These are standard benchmarks used across the industry by restaurant consultants and operations platforms ([Restaurant365](https://www.restaurant365.com/blog/how-to-calculate-prime-cost-in-a-restaurant/), [Toast](https://pos.toasttab.com/blog/on-the-line/restaurant-prime-cost), [7shifts](https://www.7shifts.com/blog/restaurant-prime-cost-guide/)). - Above 65%? It's very hard to be profitable after overhead. - Above 70%? Almost impossible unless your rent is near-zero. Prime is your biggest controllable chunk. Rent, utilities, marketing are secondary. Fix prime first. ### The Two Big Levers (COGS Gets the Spotlight) **1) Food & Beverage Cost (COGS)** - **Target:** 28–35% of sales. Quick-service often 25–30%, full-service 28–32%, fine dining 30–35% ([NetSuite](https://www.netsuite.com/portal/resource/articles/erp/restaurant-benchmarks.shtml), [Restaurant365](https://www.restaurant365.com/blog/closing-the-gap-between-actual-and-theoretical-food-costs/)). - Formula: (Cost of food/bev used ÷ Sales) × 100 - How you actually get the real number: Physical inventory counts + invoice pulls. No guessing. The money dies here quietly. Track **actual vs. theoretical** food cost. The gap is your variance. - **Theoretical** = the ideal. The expected cost of your dishes under **_perfect_** conditions. Assuming no waste, spoilage, shrinkage, or inefficiencies. - _How to get this number? Documented recipes + Ingredient Costs_ - **Actual** = What you really spent (waste, theft, portion mistakes included). - _How to get this number? Physical inventory counts_ - **Variance** = Actual − Theoretical. Industry practitioners generally consider 1–2% variance acceptable, while anything above 3% is a red flag worth investigating ([CrunchTime](https://www.crunchtime.com/blog/blog/explaining-actual-vs-theoretical-food-cost-variance), [Backbar](https://academy.getbackbar.com/how-to-calculate-bar-inventory-variance-guide)). Many independents operate well above 3% without realizing it, because they're not measuring. **Here's what that looks like in dollars:** Say you do $1.2M in annual sales. A 3% variance = **$36,000/year** gone. At typical independent net margins of 3–5%, that's half your profit or more. Chains catch this weekly. Most independents don't catch it at all. #### Quick example: Finding a $600/month leak Imagine you run a burger-focused restaurant doing $25K/week in sales. Your theoretical food cost (based on your recipes and current ingredient prices) is 30%. That means you _should_ be spending $7,500/week on food. But after counting inventory this Sunday, you calculate actual food cost at 33%. That's $8,250/week, a $750/week gap, or roughly **$3,000/month**. Where's it going? You check the biggest-dollar items first: - Ground beef: You spec 6 oz patties. You weigh a few from the line and they're coming out 7.5 oz. That's 25% more beef per burger. On 400 burgers/week, that's ~$200/week in extra beef alone. - Chicken wings: You ordered 10 cases this week but only received 9 (check the invoice against the delivery receipt). There's another $80. - Produce waste: Prep cook cut lettuce Monday for the week. By Thursday half of it is brown and gets tossed. That's avoidable with smaller, more frequent prep. Three items, one week of looking. You tighten portions, verify deliveries, and adjust prep schedules. Variance drops to 1.5%. That's real money back. #### Another example: Coffee shop bleeding on milk You run a small coffee shop doing $8K/week. Your theoretical food cost is 25% ($2,000/week). After counting, actual comes in at 29%, or $2,320/week. That's a $320/week gap, or **$1,280/month**. You dig in: - Oat milk: Baristas free-pour for lattes instead of using the measured pitcher. You're averaging 14 oz of milk per 12 oz latte instead of 10 oz. On 300 lattes/week, that's ~$90/week in extra milk. - Pastries: You order 5 dozen muffins Monday, sell 4 dozen by close Wednesday, toss the rest Thursday morning. That's 12 muffins/week in waste, about $30. - Beans: Your espresso grinder drifted. Shots are pulling heavy at 21g instead of 18g. Across 500 shots/week, that's an extra 1.5 kg of coffee, roughly $40/week. Recalibrate the grinder, train baristas on measured pours, and switch to smaller pastry orders twice a week. Variance drops to 1.5%. Same playbook, different operation. #### Where variance hides (the quiet assassins) - **Portion drift**: Recipe says 6 oz burger. Line cooks eyeball 7–8 oz. That's 15–30% extra cost on that item. - **Yield mistakes**: Braise assumes 55% yield. Team gets 40%. Cost per usable pound skyrockets. - **Supplier shorting**: Order 50 cases, get 49. If nobody's counting deliveries, you'll never know. - **Waste/spoilage**: Dropped plates, expired product, prep mistakes, all unlogged during rush. - **Theft**: Employee grazing, over-pours for tips, POS voids, walking out with product. Industry sources have widely cited that employee theft accounts for a large share of restaurant inventory shrinkage, with some estimates as high as 75%, with an impact of roughly 4% of sales ([NRA data, compiled by KROST CPAs](https://www.krostcpas.com/restaurant-news/restaurant-employee-theft)). The exact numbers are hard to verify, but the pattern is real: small, repeated losses add up fast when nobody's tracking. None of this is one big theft ring. It adds up through a thousand small cuts, and it persists because there's no visibility. **2) Labor Cost** (Just a quick view. We'll publish a deep dive later) - **Target:** 25–35% of sales (QSR lower ~25–30%, full-service 30–36%). Worth noting: the NRA's own data shows that full-service median labor cost hit [36.5% of sales in 2024](https://restaurant.org/research-and-media/research/restaurant-economic-insights/analysis-commentary/elevated-labor-costs-had-a-significant-impact-on-restaurant-profitability-in-2024/), which means many operators are already above the traditional target range. - Formula: Total labor ÷ Sales × 100 - Killers: Overstaffing dead shifts, overtime, turnover (training eats money), keeping dead weight. - Reality checks: - Sales per labor hour: Higher = better. - Schedule to forecast, not "last week's ghost schedule." - Cut fat, not muscle. A skeleton crew ticks off guests and tanks tips/repeat business. **Bottom Line:** Prime ≤60–65% + tight COGS variance = you're probably making real money after overhead. If COGS variance is above 3% and prime is creeping, fix **food first**. That's where independents lose the most without noticing. --- ## Part 3: Why Staying on Top of Your Data Is So Hard ### The Spreadsheet: Works Until It Doesn't Let's be honest: spreadsheets _can_ work. Some operators run tight ships with a Google Sheet they've maintained for years. If that's you and your numbers are solid, don't fix what isn't broken. But for most solo operators, the pattern looks like this: You go hard for a few weeks (Sunday count, invoice cross-check, Google Sheet math). Then a brutal week hits, the process slips, and the spreadsheet goes stale. Not laziness. Life. Typical grind for operators tracking everything from scratch: 5–7 hours/week handwriting, typing, fixing errors. (If you've got a streamlined sheet, yours may be lower, but still fragile.) Multi-tab files where one bad entry cascades. Prices outdated. Waste unlogged. By midweek you're analyzing last week's data, too late to act on it. Your time at $20–25/hr = $5K+/year just counting. The real cost is higher: hours stolen from training, vendor negotiations, and being on the floor. Burnout cycle: Trust no one to count right → do it yourself → run out of gas → numbers go dark → month-end surprise. **If you can make a spreadsheet work consistently, that's great.** The key word is _consistently_. The information in Part 2 applies no matter what tool you use. The hard part is sustaining the habit week after week. ### Enterprise Software: Powerful but Heavy Platforms like MarketMan ($130–$430/month), Restaurant365 ($250–$500/month), and xtraCHEF by Toast (custom pricing, typically $150+/month) are powerful for multi-unit operations with IT support. ([MarketMan pricing](https://www.marketman.com/pricing-for-restaurant-inventory-management-system), [Restaurant365 pricing](https://www.restaurant365.com/pricing/)) For a solo operator: setup often takes 20–40 hours (vendor mapping, recipe entry, par levels). You're paying for features you'll never use. And when your freezer Wi-Fi drops mid-count, you're back to pen and paper. These are good products. They're just designed for a different scale of operation. ### The Real Problem: Friction Whether it's a spreadsheet or expensive software, the failure mode is the same: too much friction. A busy week hits, the process breaks, and variance creeps back unchecked. Whatever system you use, it needs to be fast enough that you'll actually do it every single week. If it takes more than an hour, most solo operators won't sustain it. --- ## Part 4: Making It Sustainable ### The Leverage: Reducing Data Entry Time The biggest barrier to consistent cost tracking is data entry. Counting inventory by hand and keying invoices manually is slow, boring, and error-prone. Newer tools, including AI-assisted ones, are changing this: - **Voice counting**: Walk the cooler with your phone, call out what you see. The app logs items and matches them to your inventory. Operators who switch from clipboard counting typically report cutting their count time by half or more. - **Invoice capture**: Photograph an invoice, and software extracts items, prices, and quantities, then flags price changes or shorted deliveries. A few minutes vs. 20 minutes of manual entry per invoice. These aren't magic. You still need to verify the data, catch errors, and make decisions. But cutting weekly inventory from 5–7 hours to under an hour changes whether the process survives a busy week. _Full disclosure: we build a voice-first inventory tool (that's [Stockcount](https://stockcount.io)). But the advice in this article applies regardless of what tool you use. A spreadsheet you actually maintain beats expensive software you abandon._ ### What This Looks Like in Practice 1. **Get numbers fast**: Use whatever system keeps data entry under an hour: voice counting, a streamlined spreadsheet, a lightweight app. The tool matters less than the habit. 2. **Sustain it**: If your weekly process takes more than an hour, simplify it until it doesn't. A process that dies after three weeks tells you nothing. 3. **Use it**: The point of knowing your actual COGS is to _act_ on it. Reprice menu items. Negotiate with vendors armed with data. Cut items that don't earn their place. Tighten portions where drift is costing you. Operators who do this weekly, not perfectly, just consistently, find margin. The ones who don't, blame inflation for problems they could have caught. --- ## Do This Sunday (15 Minutes, No Setup) Don't wait until you have a perfect system. This weekend, do these five things: 1. **Pick your 5 highest-dollar ingredients.** The items you spend the most on each week (protein, dairy, produce, whatever moves the most money). 2. **Count just those 5 items.** Walk your cooler and dry storage. Write down what you have on hand right now. 3. **Pull this week's invoices for those items.** Check what you ordered vs. what you received. Any short deliveries? Any price jumps you didn't notice? 4. **Weigh one portioned item on the line.** Pick whatever your kitchen uses the most of (burgers, chicken breasts, grain bowls). Are portions matching your recipe spec, or are they drifting? 5. **Write down what you find.** A notes app is fine. You're not building a system yet. You're building the habit of looking. If you find nothing surprising, great. If you find a leak, you just paid yourself for 15 minutes of work. Either way, you now have a baseline to compare against next week. --- ## Final Checklist: Your Weekly + Monthly Routine Print this. Set reminders. The tool doesn't matter. The consistency does. ### Every Week (Aim for <1 Hour Total) - **Take full inventory** (Sunday night/Monday AM): Count walk-in, dry storage, freezer. Use whatever method is fastest for you. - **Pull & snap invoices**: Collect all delivery invoices from the week. Check for shorted deliveries and price jumps. - **Calculate COGS**: Beginning inventory + purchases − ending inventory = COGS used. Calculate actual food cost %. - **Pull labor totals**: Payroll summary (wages + taxes + benefits + overtime). Calculate labor % of sales. - **Compute prime cost**: (COGS + labor) ÷ sales × 100. Compare to your target (≤60–65%). - **Check variance** (COGS focus): Actual vs. theoretical food cost. If above 3%, investigate: check your highest-dollar items first for portion drift, waste, or receiving errors. - **Quick labor scan**: Sales per labor hour? Schedule next week based on forecasted sales, not last week's pattern. - **Act fast**: Prime creeping? Adjust portions, 86 high-variance items, renegotiate with your vendor, trim hours on slow shifts. Fix food costs first. It's usually the bigger and more fixable lever. - **Log trends**: Record prime %, COGS %, and variance somewhere consistent. Patterns become visible after 3–4 weeks. ### Every Month (Deeper Review, 2–4 Hours) - **Review weekly logs**: Average your prime cost for the month. Is the trend going up, down, or flat? - **Re-cost key recipes**: If ingredient prices shifted, update your theoretical costs so your variance calculation stays meaningful. - **Menu engineering check**: Promote winners (high margin + high sales). Reprice or cut items that drag you down. - **Full overhead scan**: Rent, utilities, insurance, card fees. Any surprises? Negotiate or cut. - **Cash flow & profit reality**: After prime + fixed costs, what's actually left? Adjust next month's plan accordingly. - **Vendor & receiving audit**: Spot recurring shortages or price creep. Have the conversation with your rep if the data supports it. - **Plan ahead**: Forecast next month's sales, set a labor budget, adjust ordering based on what you learned. Do the weekly stuff like brushing your teeth. Skip it and problems compound fast. Monthly reviews are your deeper check-up. Operators who maintain this rhythm consistently tend to find margin improvements because they catch problems in days instead of months. --- ## Sources - National Restaurant Association, [_2026 State of the Restaurant Industry_](https://restaurant.org/research-and-media/media/press-releases/persistent-cost-increases-and-enduring-demand-will-shape-the-restaurant-industry-in-2026/) (February 2026): food cost increases, operator profitability, cost challenges - NRA, ["Elevated costs continue to pressure restaurant profitability"](https://restaurant.org/research-and-media/research/restaurant-economic-insights/analysis-commentary/elevated-costs-continue-to-pressure-restaurant-profitability/): cost breakdowns by category - NRA, ["Elevated labor costs had a significant impact on restaurant profitability in 2024"](https://restaurant.org/research-and-media/research/restaurant-economic-insights/analysis-commentary/elevated-labor-costs-had-a-significant-impact-on-restaurant-profitability-in-2024/): labor cost benchmarks (36.5% median for full-service) - YouGov, [_US Dining Out Report 2025_](https://yougov.com/en-us/reports/53193-us-dining-out-report-2025): consumer dining frequency and price sensitivity - Barmetrix, ["Restaurant Inflation: 2025 Trends"](https://www.barmetrix.com/blog/restaurant-inflation) (citing NRA/BLS/USDA data): utility and occupancy cost increases - CrunchTime, ["Explaining Actual vs. Theoretical Food Cost Variance"](https://www.crunchtime.com/blog/blog/explaining-actual-vs-theoretical-food-cost-variance): variance benchmarks - KROST CPAs, ["Restaurant Employee Theft"](https://www.krostcpas.com/restaurant-news/restaurant-employee-theft): NRA theft/shrinkage data - Restaurant365, ["How to Calculate Restaurant Prime Cost"](https://www.restaurant365.com/blog/how-to-calculate-prime-cost-in-a-restaurant/): prime cost benchmarks - NetSuite, ["11 Key Restaurant Benchmarks"](https://www.netsuite.com/portal/resource/articles/erp/restaurant-benchmarks.shtml): COGS and labor benchmarks by segment --- _This guide is from the [Stockcount](https://stockcount.io) team. We build voice-first inventory tools for independent restaurants. If you want to try it, [create an account](https://stockcount.io/signup). But honestly, the most important thing is that you pick a system and stick with it._ --- ### How to Calculate Food Cost Percentage URL: https://stockcount.io/blog/how-to-calculate-food-cost-percentage Published: 2026-03-01 | Updated: 2026-03-19 Keywords: how to calculate food cost percentage, food cost percentage formula, restaurant food cost, food cost calculator, COGS restaurant Food cost percentage is one of the first numbers a restaurant or cafe operator should learn to track. It tells you how much of every dollar you earn goes to ingredients. Get it wrong, and you could be serving beautiful dishes at a loss. ## What Is Food Cost Percentage? Food cost percentage is the ratio of ingredient costs to food revenue. For every dollar of food you sell, how many cents went to buying the ingredients? A food cost percentage of 30% means you spend 30 cents on ingredients for every dollar of food revenue. The remaining 70 cents covers labor, rent, utilities, and profit. ## The Formula **Food Cost Percentage = (Cost of Goods Sold / Food Revenue) x 100** If your restaurant did $50,000 in food sales last month and COGS was $15,000: ($15,000 / $50,000) x 100 = **30% food cost** Want to skip the arithmetic? Our free [food cost calculator](/tools/food-cost-calculator) runs this formula instantly — enter beginning inventory, purchases, ending inventory, and sales, and it returns COGS and food cost %. The tricky part is calculating [COGS](/blog/what-is-cogs-restaurant) accurately. ## How to Calculate Cost of Goods Sold (COGS) COGS is not just what you purchased. It accounts for what you actually used, based on inventory changes: **COGS = Beginning Inventory + Purchases - Ending Inventory** Example: - Beginning inventory: $8,000 - Purchases: $18,000 - Ending inventory: $11,000 COGS = $8,000 + $18,000 - $11,000 = **$15,000** Without accurate beginning and ending inventory numbers, your COGS is a guess. ## Industry Benchmarks What counts as a good food cost percentage depends on your concept. The ranges below come from the National Restaurant Association's annual _State of the Restaurant Industry_ reports and are consistent with data from restaurant accounting firms like BDO and RSM: - **Fine dining**: 28-35% - **Casual dining**: 28-32% - **Fast casual / QSR**: 25-30% - **Cafes and coffee shops**: 25-35% - **Bars**: 20-25% (for food; pour cost is separate) The commonly cited ideal is **28-32%** for full-service restaurants. But context matters. A pizza shop might run 25% food cost with high labor, while a sushi restaurant runs 35% with lower labor. What matters is that total prime cost (food + labor) stays under 60-65% of revenue. The NRA's 2024 data puts the median full-service restaurant at roughly 32% food cost, up from 29-30% pre-pandemic, largely driven by ingredient inflation. So if you are running 33% right now, you are not failing. You are in line with a shifted industry. ## Per-Item vs. Overall Food Cost Your overall food cost is the aggregate number above. Each dish also has its own food cost, called the [plate cost](/blog/plate-cost-guide-restaurants) percentage: **Plate Cost Percentage = (Ingredient Cost per Plate / Menu Price) x 100** A sandwich costing $3.50 in ingredients, sold for $12: ($3.50 / $12) x 100 = **29.2% plate cost** You want both numbers. Overall tells you how the business is performing. [Per-item plate costs](/blog/plate-cost-guide-restaurants) tell you which dishes are profitable and which are dragging you down. ## Common Mistakes That Inflate Food Cost Most restaurants struggling with food cost lose money in less obvious ways: **1. Not counting inventory regularly.** Monthly or quarterly counts let thousands of dollars walk out the door before you notice. Weekly counts are the standard for a reason. **2. Ignoring waste.** Trim waste, spoilage, and over-portioning increase actual food cost above what your recipes predict. Tracking waste separately helps you find the source. See the [theoretical vs. actual](#theoretical-vs-actual-food-cost) section below for how to measure the gap. **3. Using outdated ingredient costs.** Plate costs based on prices from six months ago are wrong. Prices change constantly, especially proteins and produce. See [keeping recipe costs current](#keeping-recipe-costs-current-when-prices-change) below for how to handle this without losing your mind. **4. Not accounting for comps and staff meals.** Even a small cafe giving staff one meal per shift and comping the occasional guest can run $50-100/day, which is $1,500-3,000/month. Larger full-service restaurants can easily hit $200/day or more. These are real costs that need tracking, either deducted from COGS or separated into their own line item. **5. Confusing purchases with COGS.** Your credit card statement shows what you bought, not what you used. You need inventory counts for actual COGS. ## Theoretical vs. Actual Food Cost This is one of the most useful concepts in food cost management, and most operators never use it. **Theoretical food cost** is what your food cost _should_ be based on your recipes, portion sizes, and sales mix. If you sold 100 burgers and each burger uses $3.20 in ingredients, the theoretical cost for burgers is $320. Add up every menu item sold and you get total theoretical COGS. **Actual food cost** is what you calculate from inventory counts using the COGS formula above. The gap between the two is where the money goes. Here is what this looks like in practice. Say you run a casual restaurant that did $40,000 in food sales last week: | | Theoretical | Actual (from inventory) | | ----------- | ----------- | ---------------------------- | | COGS | $11,200 | $13,200 | | Food cost % | 28.0% | 33.0% | | **Gap** | | **5.0 points = $2,000/week** | That 5-point gap means $2,000 per week is going somewhere your recipes did not account for. Over a month, that is roughly $8,000. The gap could be waste, over-portioning, theft, unrecorded comps, or receiving errors. You will not know which until you investigate, but now you know exactly how much money is at stake. To calculate theoretical food cost, you need costed-out recipes for every menu item and accurate POS sales data. It takes work to set up, but once you have it, the theoretical-vs-actual comparison becomes the most actionable report in your operation. ## Keeping Recipe Costs Current When Prices Change The theoretical vs. actual comparison only works if your recipe costs reflect what you are actually paying. This is harder than it sounds. Chicken thighs might be $2.10/lb one week and $2.45/lb two weeks later. Avocados can swing 40% in a month. If your recipe cards still say $1.80/lb from when you last updated them, your theoretical food cost is wrong and the gap analysis above becomes meaningless. There are three common approaches. Each has real tradeoffs: **Last purchase price.** Update each ingredient cost to whatever you paid on your most recent invoice. This is the simplest to maintain and the most common approach in practice. The downside is that a single anomalous order (a spot buy at a high price, or a one-time deal) can skew your theoretical cost until the next delivery. For most operations, this is good enough. **Rolling average.** Average the last 3-4 purchase prices for each ingredient. This smooths out spikes and gives you a more stable theoretical cost to compare against. The downside is that it lags behind real price movements. If chicken just jumped 15% and is staying there, a rolling average will understate your true cost for several weeks. It also takes more work to maintain. **Periodic update.** Pick a cadence (monthly or quarterly) and update all recipe costs at once using current vendor pricing. This is the least work per week, but your theoretical cost drifts between updates. In a stable pricing environment, quarterly works fine. In a volatile one, your numbers can be off by several points before the next update. **What actually works:** Use last purchase price for your high-volume, high-volatility items: proteins, produce, dairy, cooking oils. These are the ingredients where price swings hit your food cost hardest and where stale data costs you the most. For shelf-stable goods that rarely change price (spices, dry goods, canned products), a quarterly update is fine. You do not need to update the cost of oregano every week. You do not need perfect precision, just close enough that your theoretical-vs-actual gap tells you something real. If your recipe costs are within 2-3% of what you are actually paying, the gap analysis works. If they are six months stale, you are just comparing two wrong numbers. ## How Often to Calculate Food Cost **Weekly is the gold standard.** Monthly is too slow. By the time you see a problem in monthly numbers, you have already lost three or four weeks of margin. Count inventory on the same day each week. Pull your POS revenue for that period. Run the formula. The whole process should take 30-60 minutes once you have a system. If a full weekly count is not realistic for your operation, start with your top 15-20 items by dollar volume. In most kitchens, roughly 80% of your food cost comes from 20% of your items (proteins, dairy, produce). Counting just those weekly and doing a full count biweekly or monthly gets you most of the benefit. The operators who consistently hit their food cost targets are the ones who look at the number every week and act on it immediately. ## How to Lower Your Food Cost - **Count inventory weekly** to catch problems early - **Track waste** with a waste log - **Portion consistently** using scales, scoops, and standardized recipes - **Update ingredient costs** when vendor prices change - **Engineer your menu** to push high-margin items - **Negotiate with vendors** or compare prices across suppliers - **Cross-utilize ingredients** so trim from one prep becomes a component in another dish - **Review menu prices** at least quarterly. Ingredient costs go up, and menu prices need to follow. A 5% across-the-board price increase on a $50,000/month operation drops food cost by roughly 1.5 points. Many operators focus entirely on cutting costs when a price adjustment would be faster and less disruptive to quality. ## Doing This With a Spreadsheet You do not need software to track food cost. A spreadsheet works. Here is the minimum setup: 1. **Column A**: Item name. List every item you count. 2. **Column B**: Unit (case, pound, each). 3. **Column C**: Cost per unit. Update this when vendor prices change. 4. **Column D**: Beginning count. 5. **Column E**: Ending count. 6. **Column F**: Purchases (in the same unit). 7. **Column G**: Usage = Beginning + Purchases - Ending. 8. **Column H**: Cost = Usage x Cost per unit. Sum column H for total COGS. Divide by food revenue. That is your food cost percentage. The math is easy. Doing it consistently every week, keeping prices current, and avoiding data entry errors is where people fall off. If you can stay disciplined with a spreadsheet, that is a legitimate approach. ## Making It Easier If the spreadsheet becomes a bottleneck, or if you find yourself skipping weeks because the process is too tedious, that is where tools help. Stockcount removes the friction. Count inventory by voice while walking your storage. COGS, food cost percentage, and plate costs calculate automatically. No clipboards, no spreadsheets, no formulas. Your food cost percentage updates in real time as you count and log purchases, so you always know where you stand. [Try Stockcount free for 14 days](/#waitlist) and see what real-time food cost visibility looks like. --- ### Restaurant Inventory Counting Guide URL: https://stockcount.io/blog/restaurant-inventory-counting-guide Published: 2026-02-25 | Updated: 2026-03-17 Keywords: restaurant inventory counting, how to count restaurant inventory, inventory count best practices, food inventory management, restaurant inventory tips Counting inventory is the least glamorous part of running a restaurant. But accurate counts are the foundation of food cost tracking, ordering, waste reduction, and profitability. It does not have to take as long as most operators make it. ## Why Regular Counts Matter - **Catch waste and theft early.** A few missing steaks per week adds up to hundreds of dollars per month. Regular counts surface these patterns. - **Identify over-portioning.** If you are using 20% more chicken than recipes call for, the only way to know is comparing expected usage (from sales) against actual usage (from counts). - **Keep ordering accurate.** Without knowing what you have on hand, you guess when ordering, leading to waste or 86'd items. - **Calculate actual food cost.** You cannot calculate [COGS](/blog/what-is-cogs-restaurant) without beginning and ending inventory. Without COGS, your [food cost percentage](/blog/how-to-calculate-food-cost-percentage) is fiction. ## How Often Should You Count? **Weekly for a full count, daily for high-value items.** - **Full inventory**: Once per week, same day each week (Sunday night or Monday morning) - **High-value items** (proteins, seafood, specialty items): Daily or every other day - **Dry goods and shelf-stable items**: Weekly - **Beverages and alcohol**: Weekly, matched against POS sales Count more frequently when diagnosing a problem. Daily protein counts for a couple weeks can pinpoint where variance comes from. Consistency matters most. A count every Monday at 7 AM beats a thorough count done whenever you get around to it. ## Best Practices for Accurate Counts ### Count at the same time every session Pick a time when inventory is stable, before the first delivery and before prep starts. Counting mid-shift while prep and deliveries happen creates chaos. ### Organize by storage area Walk-in cooler, then freezer, then dry storage, then bar. Do not bounce around. Moving systematically through one area is faster and produces fewer errors. ### Use consistent units If you count milk in gallons, always count in gallons. Switching between units introduces conversion errors. ### Count partial containers A half-full container of olive oil has value. Estimate to the nearest quarter (3/4, 1/2, 1/4). Do not mark a quarter-full container as "1." ### Two people when possible One counts, one records. Two sets of eyes catch mistakes. Solo? Count each shelf, record, then spot-check a few items. ### Set par levels Par levels (minimum on-hand quantity per item) make ordering easier and make abnormally low counts obvious during a count. ## Common Counting Methods ### Clipboard Printed sheet with item names and quantity columns. Works, but transcribing to a spreadsheet after is time-consuming and error-prone. **Time: 2-3 hours counting + 30-60 minutes data entry** ### Spreadsheet on tablet Entering counts directly eliminates transcription, but holding a laptop in a walk-in is awkward and switching between cells is slow. **Time: 2-3 hours** ### Inventory management apps Dedicated apps with better UI than spreadsheets, sometimes with barcode scanning. Still requires tapping a screen with cold or wet hands. **Time: 1.5-2.5 hours** ### [Voice counting](/blog/restaurant-food-cost-tracking-ai) Speak counts out loud while the app records. Hands stay free. Move through storage naturally without stopping to type. AI matches what you say to your inventory list. **Time: 1-1.5 hours** ## The Real Cost of Manual Counting A 3-hour weekly clipboard count at $25/hour is $3,900/year in labor alone. But the bigger cost is stale data. If food cost creeps up 2% because you are not catching waste, on $40,000/month in food revenue that is $9,600/year in lost margin. A better counting process pays for itself many times over. ## Tips for Managing Team Counts - **Train once, thoroughly.** Walk through the entire process: how to measure partial containers, where items live, what units to use. - **Use a consistent item list.** Same items, same order, every week. Catches missed items and makes results comparable. - **Review for anomalies.** Had 12 cases of chicken last week, 2 this week, but only sold 6 worth? Something is off. - **Make it routine, not punishment.** Counting goes faster as a normal part of workflow rather than a dreaded chore. ## A Better Way to Count The biggest friction is not counting itself. It is data entry. Walking around and looking at what you have is fast. Typing every item into a device, then transcribing clipboard notes, is where the hours go. With Stockcount, you start a session, put your phone in your pocket, and speak naturally: "five gallons whole milk, three bags flour, two cases cherry tomatoes." The AI recognizes items, records quantities, and you keep moving. No screens to tap. No clipboards to transcribe. No spreadsheets to update. If your weekly count takes more than 90 minutes, [try Stockcount free for 14 days](/#waitlist) and see how much time you get back. --- ### What Is COGS in a Restaurant? URL: https://stockcount.io/blog/what-is-cogs-restaurant Published: 2026-02-20 | Updated: 2026-03-17 Keywords: COGS restaurant, cost of goods sold restaurant, restaurant COGS formula, food cost tracking, actual vs theoretical COGS COGS stands for Cost of Goods Sold. In a restaurant, it represents the total cost of food and beverage ingredients you used to generate revenue over a specific period. Not what you bought, but what you actually used. It directly determines your gross profit, yet many operators calculate it wrong, too infrequently, or not at all. ## The COGS Formula for Restaurants **COGS = Beginning Inventory + Purchases - Ending Inventory** Example for one week: - **Beginning inventory** (Monday morning): $12,000 - **Purchases received** (Monday through Sunday): $8,500 - **Ending inventory** (Sunday night): $10,500 COGS = $12,000 + $8,500 - $10,500 = **$10,000** That $10,000 is the value of ingredients consumed during the week. If food revenue was $33,000, your [food cost percentage](/blog/how-to-calculate-food-cost-percentage) would be: ($10,000 / $33,000) x 100 = **30.3%** Our free [food cost calculator](/tools/food-cost-calculator) does both steps at once — enter your inventory and purchases and it returns COGS and food cost %. ### Why "Purchases" Is Not the Same as COGS This is the most common mistake. Vendor invoices tell you what you bought, not what you used. If you bought $10,000 but $2,000 is still in the walk-in, actual cost of goods used was $8,000. This is why you need inventory counts. Without beginning and ending inventory values, you cannot calculate true COGS. You are just tracking spending. ## Actual vs. Theoretical COGS ### Actual COGS What we calculated above. Based on real inventory counts and purchases. Tells you what you actually used. ### Theoretical COGS What you should have used based on sales mix and recipes. If you sold 100 lattes at $0.60 in ingredients each, theoretical latte cost is $60. Calculate it by multiplying the [ingredient cost of each menu item](/blog/plate-cost-guide-restaurants) by units sold, then summing across all items. ### The Variance **Variance = Actual COGS - Theoretical COGS** If actual is $10,000 and theoretical is $8,500, you have a **$1,500 variance**, about 15% waste. Sources of variance: - **Over-portioning**: More on the plate than the recipe calls for - **Waste**: Spoilage, trim waste, dropped or burned product - **Theft** - **Unrecorded sales**: Comps, staff meals, and samples not tracked - **Recipe inaccuracy**: Recipes do not reflect how the dish is actually made The variance does not tell you the cause, but it tells you the magnitude and where to investigate. ## Using COGS to Make Better Decisions ### Menu pricing A popular dish with 42% food cost? Raise the price, reduce the portion, or find a cheaper substitute. Knowing your [plate cost per item](/blog/plate-cost-guide-restaurants) lets you decide with data. ### Vendor negotiation When you know exactly what you spend per ingredient category, you negotiate from knowledge. "I spend $3,200/month on dairy across three vendors. What can you do if I consolidate?" ### Portion control Comparing actual vs. theoretical by category pinpoints over-portioning. If protein variance is 20% but dry goods is 3%, you know where to focus training. ### Ordering decisions Accurate COGS reveals usage patterns. Consistently using 18 cases of chicken per week? Negotiate a standing order instead of ad-hoc purchases at retail pricing. ### Identifying theft A sudden spike in COGS for specific items (especially high-value proteins or alcohol) without a corresponding sales increase is a red flag. ## Why Monthly COGS Is Not Enough Most operators track COGS monthly, when their bookkeeper reconciles. A monthly number is too stale to act on. If food cost spiked in week one because a new cook was over-portioning, you will not know until four weeks later. Three more weeks of lost margin. **Weekly COGS** gives a much tighter feedback loop. You spot problems within days and correct before they compound. The tradeoff has always been time. Weekly counts, weekly data entry, weekly calculations. Most operators settle for monthly because the weekly process is too burdensome. ## Making COGS Tracking Practical A typical weekly COGS calculation requires: 1. Counting all inventory (1.5-3 hours) 2. Entering counts into a spreadsheet (30-60 minutes) 3. Gathering purchase invoices (20-30 minutes) 4. Running calculations (10-20 minutes) 5. Analyzing results (15-30 minutes) That is 3-5 hours per week. For a small operation where the owner is also on the line, that time does not exist. Stockcount compresses this. Voice counting cuts inventory to under an hour. Purchase data flows in from invoice scanning. COGS, both actual and theoretical, calculates automatically in real time. Instead of a number from your accountant once a month, you get a live dashboard that updates every time you count or log a purchase. When food cost drifts, you know this week, not next month. [Try Stockcount free for 14 days](/#waitlist) and see what real-time COGS tracking looks like. --- ### How to Calculate Plate Cost (With Examples) URL: https://stockcount.io/blog/plate-cost-guide-restaurants Published: 2026-02-15 | Updated: 2026-03-17 Keywords: plate cost, how to calculate plate cost, plate cost formula, menu engineering, recipe costing, food cost per plate Plate cost is the total ingredient cost to produce one serving of a menu item. Most operators either do not know it or are working with numbers months out of date. Knowing plate cost for every item tells you which dishes make money and which erode your margins. It is also the foundation for calculating [COGS](/blog/what-is-cogs-restaurant) and [food cost percentage](/blog/how-to-calculate-food-cost-percentage). ## What Is Plate Cost? Plate cost (also called recipe cost) is the sum of every ingredient cost in one serving: protein, starch, garnish, sauce, sides, condiments. **Plate Cost = Sum of (Ingredient Quantity x Cost Per Unit) for each ingredient** Our free [recipe cost calculator](/tools/recipe-cost-calculator) does this sum for you — add each ingredient with its cost, set the yield, and get cost per serving. The math is simple. The tedium is that a single item might have 8-15 ingredients, each purchased in different units than used. ## Example: Latte A 12-ounce latte: | Ingredient | Quantity Used | Cost Per Unit | Cost | | --------------------- | ----------------- | ----------------------- | ----- | | Espresso beans | 18g (double shot) | $12.00 / 1,000g bag | $0.22 | | Whole milk | 8 oz | $4.80 / 128 oz (gallon) | $0.30 | | Cup + lid | 1 | $0.15 each | $0.15 | | Sugar/sweetener (avg) | - | - | $0.03 | **Total plate cost: $0.70** At $5.50 selling price: ($0.70 / $5.50) x 100 = **12.7% food cost** Typical for coffee drinks. This is why cafes love beverages. ## Example: Turkey Sandwich | Ingredient | Quantity Used | Cost Per Unit | Cost | | --------------- | ----------------- | ------------------ | ----- | | Sourdough bread | 2 slices (80g) | $4.50 / 800g loaf | $0.45 | | Roasted turkey | 4 oz | $8.50 / lb (16 oz) | $2.13 | | Swiss cheese | 1 oz | $6.00 / lb (16 oz) | $0.38 | | Lettuce | 0.5 oz | $2.50 / lb (16 oz) | $0.08 | | Tomato | 2 slices (40g) | $3.00 / lb (454g) | $0.26 | | Mayo | 0.5 oz | $4.00 / 128 oz | $0.02 | | Pickle spear | 1 | $0.10 each | $0.10 | | Side salad | 2 oz mixed greens | $4.00 / lb | $0.50 | | Dressing | 1 oz | $0.15 | $0.15 | **Total plate cost: $4.07** At $14.00: ($4.07 / $14.00) x 100 = **29.1% food cost**, right in the sweet spot. ## Why Most Operators Do Not Know Their Plate Costs **It is tedious.** A 30-item menu with 8-15 ingredients each means 240-450 individual cost calculations. Every price change requires updating every recipe that uses that ingredient. **Unit conversions are error-prone.** You buy chicken by the 40 lb case, portion by the ounce, and recipes call for grams. **Prices change constantly.** Produce and protein prices fluctuate weekly. Plate costs from January may be significantly off by March. **Recipes are not standardized.** If cooks are not following exact recipes, calculated plate costs do not match reality. The result: most operators price by feel. Sometimes that instinct is right. Often, it leaves money on the table. ## Menu Engineering: Using Plate Costs Strategically Combine plate cost, selling price, and sales data to classify each item: ### Stars (High Profit, High Sales) Your best items. Popular and strong margins. Keep them prominent. Do not change without good reason. ### Plowhorses (Low Profit, High Sales) Customers love them, but margins are thin. Options: raise price slightly, reduce portion, find cheaper substitutes, or pair with high-margin add-ons ($3 side that costs $0.40). ### Puzzles (High Profit, Low Sales) Great margins, low orders. Reposition on the menu, rename, pair with popular items, or add server recommendations. ### Dogs (Low Profit, Low Sales) Low margin and low demand. Candidates for removal. Every menu item takes up space, requires prep, and ties up inventory. ## The Contribution Margin Perspective While [food cost percentage](/blog/how-to-calculate-food-cost-percentage) is useful, contribution margin often tells a more actionable story. **Contribution Margin = Menu Price - Plate Cost** - **Latte**: $5.50 - $0.70 = **$4.80 margin** (12.7% food cost) - **Turkey Sandwich**: $14.00 - $4.07 = **$9.93 margin** (29.1% food cost) The latte has a better percentage, but the sandwich puts $9.93 in your pocket versus $4.80. A 35% [food cost](/blog/how-to-calculate-food-cost-percentage) item at $28 generates $18.20 in margin versus $4.80 from a 20% item at $6. Both percentage and dollars matter. ## Keeping Plate Costs Current The challenge is not calculating plate costs once. It is keeping them current. Prices change, recipes evolve, portions drift. A plate cost from three months ago might be 10-15% off. - **Update ingredient costs** monthly at minimum, weekly if possible - **Recalculate** whenever you change a recipe or a key price shifts - **Audit actual portions** periodically against recipes - **Track trends** to see when a dish is becoming less profitable ## Automating Plate Cost Calculations Manually maintaining recipe and cost spreadsheets is a part-time job, and the first thing that slips when operators get busy. Stockcount calculates plate costs automatically from your recipes and current ingredient prices. When a vendor price changes, every recipe using that ingredient updates instantly. Contribution margins and food cost percentages for every item, no spreadsheet required. [Try Stockcount free for 14 days](/#waitlist) and get plate costs for your entire menu in minutes. --- ### Restaurant Food Cost Tracking with AI URL: https://stockcount.io/blog/restaurant-food-cost-tracking-ai Published: 2026-02-10 | Updated: 2026-03-17 Keywords: restaurant food cost tracking, AI inventory management, restaurant AI tools, food cost tracking app, how to track food costs restaurant, restaurant technology Every restaurant owner has heard the advice: track your food costs weekly, know your COGS, calculate your plate costs. The math is not complicated. The formulas fit on a napkin. So why do most operators not do it? Because the advice leaves out the hard part: the hours of data entry, spreadsheet maintenance, and manual calculations required to get those numbers. The math is simple. The process to feed it is brutal. AI eliminates that process. Not by replacing your judgment, but by removing the data entry that sits between you and the numbers you need. ## The Real Problem Is Not the Math If you have read our guides on [food cost percentage](/blog/how-to-calculate-food-cost-percentage) or [COGS](/blog/what-is-cogs-restaurant), you know the formulas are straightforward: - **COGS** = Beginning Inventory + Purchases - Ending Inventory - **Food Cost %** = COGS / Food Revenue x 100 - **Plate Cost** = Sum of ingredient costs per serving Our free [food cost calculator](/tools/food-cost-calculator) and [recipe cost calculator](/tools/recipe-cost-calculator) run these formulas for you. The catch is the same one this article is about: a calculator still needs accurate numbers fed into it. The problem is everything that has to happen before you can use them: 1. **Count every item in storage.** Walk-in, freezer, dry storage, bar. (1.5 to 3 hours) 2. **Enter counts into a system.** Transcribe clipboard notes, fix illegible handwriting, catch skipped lines. (30 to 60 minutes) 3. **Gather purchase invoices.** Dig through emails, match deliveries to the right period. (20 to 30 minutes) 4. **Run calculations.** For every category. (10 to 20 minutes) 5. **Analyze results.** Compare to last week, spot variances. (15 to 30 minutes) That is 3 to 5 hours per week. For a small operator who is also cooking, managing, and doing payroll, that time does not exist. So they track monthly at best, or never. By the time most operators see their numbers, the problems are weeks old. A cook over-portioning chicken in week one costs you three more weeks of margin before you know about it. ## What AI Actually Changes AI is not magic. But it is genuinely good at the specific tasks that make food cost tracking painful: ### Voice replaces data entry The biggest time sink is data entry: writing counts on a clipboard, then transcribing them into a computer. With voice counting, you walk through storage and speak naturally: "five gallons whole milk, three cases cherry tomatoes, two and a half bags flour." The AI matches what you say to your inventory list, handles unit conversions, and records everything in real time. No clipboard. No transcription. No tapping a cold screen with numb fingers. What used to take 2 to 3 hours now takes 45 minutes. ### Automatic calculations replace spreadsheets Once counts are recorded, every downstream calculation happens automatically. [COGS](/blog/what-is-cogs-restaurant), [food cost percentage](/blog/how-to-calculate-food-cost-percentage), [plate costs](/blog/plate-cost-guide-restaurants), and variance all update instantly. No formulas to maintain. No risk of a broken cell silently giving you wrong numbers for three months. When a vendor price changes, every recipe using that ingredient recalculates automatically. ### Real-time visibility replaces month-end surprises With AI handling data entry, weekly counts become practical. Some operators count high-value items daily. If your food cost spikes on Tuesday, you know by end of week, not end of month. You can investigate and correct before it compounds. ## What "Good Enough" Tracking Looks Like You do not need a perfect system. You need a consistent habit and a tool that makes it sustainable. **Weekly full count.** Same day, same time, every week. Consistency matters more than precision. A count done every Monday at 7 AM beats a perfect count done whenever you get around to it. **Daily counts for high-value items.** Proteins, seafood, anything expensive enough that a few missing units matter. Takes 5 to 10 minutes with voice counting. **Track purchases as they arrive.** Snap a photo of the invoice or enter the total. **Review weekly.** Spend 10 minutes comparing food cost percentage to last week. If it moved more than 2 points, dig in. If stable, move on. With AI handling data entry and calculations, this routine takes under 2 hours per week instead of 5. ## The Spreadsheet Ceiling Most operators who try tracking food costs start with a spreadsheet. It works for a while. Then: - An ingredient price changes and you forget to update three of the eleven recipes that use it - A new menu item never makes it into the costing sheet - The person who built the spreadsheet leaves and nobody understands the formulas - You skip a week and next week's numbers are meaningless without prior ending inventory - You discover you have been calculating COGS wrong because beginning inventory pulled from the wrong cell Spreadsheets are not bad tools. They are bad systems. They require constant maintenance and break silently. AI-powered tools avoid this because the calculations are built in, not duct-taped together with cell references. ## What This Means for Small Operators The operators who benefit most are not chains with 50 locations and a full-time inventory manager. It is owner-operators running one or two locations who are doing everything themselves. These are people who know they should track food costs but do not have the hours. They price by gut feel, order by habit, and discover margin problems only when the bank account looks wrong. For a broader playbook aimed squarely at this operator, see [Staying on Top of Your Restaurant Costs](/blog/staying-on-top-of-your-costs). AI gives them back 3 to 4 hours per week and turns food cost visibility from a luxury into something that happens as part of their existing workflow. You count by talking while walking your storage. The numbers update. You glance at them during Monday morning coffee. ## Getting Started If you are not tracking food costs, starting matters more than starting perfectly. 1. **Learn the basics.** Understand [food cost percentage](/blog/how-to-calculate-food-cost-percentage), [COGS](/blog/what-is-cogs-restaurant), and [plate costs](/blog/plate-cost-guide-restaurants). 2. **Pick a tool that removes friction.** The best system is the one you will actually use every week. If spreadsheets have not stuck, that is a tool problem, not a discipline problem. 3. **Start with a weekly count.** Commit to counting every Monday. Follow our [inventory counting guide](/blog/restaurant-inventory-counting-guide) for best practices. 4. **Review weekly, not monthly.** A 5-minute weekly review catches problems 4x faster than a monthly deep-dive. Stockcount is built for operators who want real food cost visibility without the spreadsheet tax. Count inventory by voice, purchases flow in automatically, and COGS, food cost percentage, and plate costs calculate in real time. No clipboards. No spreadsheets. No formulas. Just the numbers you need to run a more profitable kitchen. [Try Stockcount free for 14 days](/#waitlist) and see what happens when the busywork disappears.