Merma por robo hormiga: the before and after of auditing your theoretical vs actual food cost

Merma por robo hormiga —the slow ant-theft bleed of a restaurant— closes with measurement, never with surveillance: compare the theoretical cost your recipe book produces against the actual cost your inventory produces, and suspicion turns into a figure in dollars. A venue billing 60,000 USD a month at 31 % food cost with a 3.2-point theoretical-to-actual gap is giving away roughly 1,920 USD every month, straight out of EBITDA. In the closings I supervise, the BEFORE is usually a gap of 2.5 to 4 points that nobody watches; the AFTER, once 60 days of weekly blind inventory, scale portioning and comp control are in place, is a gap of 0.8 to 1.2 points, which is tolerable operating noise. No camera replaces that arithmetic.
An owner in Bogotá sent me his March P&L with a three-word note: «doesn't add up». Sales were 8 % above January and profit was 4,000 USD lower. Food cost had drifted from 29.4 % to 33.1 % with no change of supplier and no change of menu, and his first reaction —everyone's first reaction— was to blame protein inflation.
It wasn't inflation. Inflation moves your purchase price, and purchase price shows up on the invoice; what he had was a hole between what the menu said each dish cost and what the stockroom said had actually left the shelf. That hole has an old name in this trade: merma por robo hormiga, ant theft. A little at a time, every day, through different hands, in amounts no annual audit ever catches because there is never one big event to investigate.
One distinction orders all the work that follows, and almost nobody makes it: shrinkage is NOT theft. Shrinkage is total product loss between purchase and sale, and it includes protein trim, expired product, returned plates, over-portioning, unlogged comps and yes, also pilferage. Ant theft is one slice of that shrinkage. Start your diagnosis hunting thieves and you will wreck team morale while leaving the other five sources untouched, and those usually weigh more.
The Masterestaurant financial pillar treats this as what it is: a measurement problem, not a trust problem. Diego F. Parra insists on a sequence that sounds obvious and is almost never respected: install the measuring stick first, read the number second, decide about people only at the end. Inverting that order is why so many restaurant expense control programs die in month two.
Side-by-side comparison
| BEFORE · no shrinkage control | AFTER · Masterestaurant protocol at 60 days | |
|---|---|---|
| Theoretical vs actual food cost gap | ✕2.5 to 4.0 food cost points with no documented explanation | ✓0.8 to 1.2 points, inside acceptable operating noise |
| High-value inventory frequency | ✕Monthly, sometimes skipped; done by whoever buys | ✓Weekly and blind on 18 to 25 class-A items; done by someone outside purchasing |
| Estimated leak on 60,000 USD monthly sales | ✕1,500 to 2,400 USD a month nobody books | ✓480 to 720 USD a month, measured and reported |
| Protein portioning | ✕By the cook's eye; real variation of 12 to 20 % per plate | ✓Mandatory scale on 6 class-A dishes, variation under 4 % |
| Comps and voids control | ✕No log; the server voids from their own POS code | ✓Manager-code voids, hard cap at 0.8 % of daily sales |
| Effect on prime cost | ✕Prime cost of 66 to 69 %, outside the healthy range | ✓Prime cost of 60 to 62 %, with 3 to 4 points recovered |
| Owner time spent on the issue | ✕Reactive: 6 to 10 hours a month firefighting | ✓90 scheduled minutes a week reading one report |
| Translation into EBITDA | ✕Margin explained with anecdotes and gut feel | ✓2.5 to 3.5 EBITDA points recovered and traceable |
Step 1: split the hand that buys from the hand that counts
Start by breaking apart a function that almost always lives in one person: whoever buys cannot be whoever counts inventory, because the system then loses its only contrast and variance gets dressed up with no effort at all. The deliverable here is a one-page memo with two names, two signatures and a weekly cutoff date, and you verify it by checking that count sheets carry the signature of someone who appears on no purchase order from the same period. It costs nothing and usually hands back the first point of food cost. In a restaurant billing 60,000 USD a month, that point is 600 USD monthly, 7,200 a year, money already sitting in the register that walked out without an invoice. If your operation is too small for two hands, you do the counting. Frequency beats precision, so the second step shrinks the universe: rank every reference by monthly consumed value, flag the ones carrying 80 % of spend —usually between 15 and 25 lines— and leave the rest out of the weekly count.
Step 2: pin down your 20 class-A items and ignore the other 280 for now
An imperfect weekly inventory over 20 items catches a leak in seven days; a perfect monthly one over 300 references catches it after two months of profit are gone. The deliverable is a signed list with those 20 lines, their counting unit and current unit cost, verified by adding up: that list's monthly value should land between 75 % and 85 % of your purchases. Beef deserves particular attention this year, since the USDA projects wholesale beef prices climbing 9.4 % during 2026. BLIND inventory shifts the result more than anyone expects, because when the count sheet arrives with the theoretical balance printed on it, the eye confirms the expected figure and counting becomes paperwork. Print the sheet with item, unit and an empty box, nothing else. Over the first three weeks you will see gaps of 8 to 15 % on your highest-value items, and those gaps are not a failure of the method but the first time you are looking at reality.
Step 3: count blind, with no system balance in sight
The deliverable is a signed count sheet, with start and finish times, loaded into the system that same day; verify it by confirming no box arrives pre-filled with the system's round number. I got this wrong for years: I believed handing over the balance saved time. Now you read the number, and you read it as money. Take the theoretical cost your recipe book throws for the week's sales, subtract the actual cost your inventory throws, and that gap is your variance. A 60,000 USD monthly restaurant with theoretical food cost at 29.4 % and actual at 33.1 % —the Bogotá case I opened with— loses 3.7 points, meaning 2,220 USD a month and 26,640 a year, more than an executive chef's salary. Percentages anesthetize; dollars force a decision. The deliverable is a weekly four-column table: item, theoretical cost, actual cost, difference in USD, sorted from largest loss down.
Step 4: calculate variance in dollars, never in percentage
You verify it when that column's total matches the hole in your P&L. Shrinkage is NOT theft, and confusing the two sinks these programs. Shrinkage is every loss between purchase and sale: protein trim, spoiled product, returned plates, over-portioning, unrecorded comps and, yes, sustraction too. Petty theft is only a fraction of it. Before suspecting a person, assign each variance line to a measurable cause: weigh trim for five days, log comps in a notebook, measure each cut's real yield against its spec sheet. Over-portioning and trim usually explain more than half. The Masterestaurant financial pillar treats this as a measurement problem rather than one of trust, and Diego F. Parra insists on the order: first the measuring stick, then the number, and only at the end the people. Flip that order and the program dies in month two. First comes the manhunt: staff meeting, prosecutor's tone, new cameras.
The four mistakes that derail this guide
It wrecks morale, drives off your good cook and leaves the other five sources of shrinkage untouched. Second is blaming inflation, which moves purchase cost and shows up on the invoice —the USDA reported food prices rising just 2.3 % through 2024 and forecasts 3.6 % for food away from home in 2026, figures that cannot explain three points of food cost. Third is rewriting the recipe book mid-measurement, because variance then blends two causes and stops saying anything. And the fourth, costliest of all, is measuring one week, finding 2,200 USD of leakage and never measuring again; without weekly cadence the leak returns to its prior level within roughly forty days. Check seven things, and none of them accepts an "almost". Two different names sign purchasing and counting. The 20-item class-A list exists and covers between 75 % and 85 % of purchases. Your last four count sheets went out blind, with start and finish times.
Closing: how to know it all landed
The USD variance table has four consecutive weeks loaded. Every line above 100 USD carries a written cause beside it, not a person's name. Total prime cost holds under 60 % of sales, the healthy target per Toast and Restaurant365, with limited-service median sitting at 65 cents per sales dollar according to the National Restaurant Association. And week four's variance runs lower than week one's. Meet all seven and the leak stopped being a suspicion and became a figure you govern. Who counts inventory decides whether the data is worth anything. When the buyer also counts, the system loses its contrast and variance can be dressed up effortlessly; separating those two hands costs nothing and usually explains the first recovered food cost point. BLIND counting —counting without seeing the system's theoretical balance— changes the result more than anyone expects. Counting in sight of the balance, the eye tends to confirm the expected figure; counting blind, differences of 8 to 15 % surface on the highest-value items during the first three weeks.
Five differences that decide whether the number drops
Frequency beats precision. An imperfect weekly count on 20 class-A items catches a leak in seven days; a perfect monthly count on 300 SKUs catches it after 2,000 USD are gone. Choose speed over completeness, every time. Your recipe book is the measuring stick, and a miscalibrated stick ruins the whole measurement. If theoretical cost runs on old prices or ignores yield factor —the tenderloin arriving at 1.2 kg and yielding 0.86 kg usable—, much of the gap you are chasing is an accounting error rather than a leak. Closing the bar is a separate job from closing the kitchen, with its own unit of measure and its own rhythm. A bar without ounce control runs 15 to 25 % variance quite normally, and that single front can outweigh all five kitchen shrinkage sources combined wherever liquor passes 30 % of sales.
Before vs after, criterion by criterion
What the restaurant losing money without knowing it doesBEFORE
- Monthly inventory run by the same person who issues purchase orders, on a spreadsheet with no theoretical cost formula.
- Stale standard recipe book, carrying purchase prices from nine months ago and no yield factor per cut.
- Comps and voids loose in the POS, with no daily cap and no authorization code separate from the server's.
- Bar with no open-bottle count and no liquid shrinkage control; pours run free and variance never closes.
- Trash and trim leaving through the back door unweighed, so real waste never enters the calculation.
- Food cost reviewed once a month, when the accountant hands over the P&L, which is thirty days too late to fix anything.
What the Masterestaurant financial pillar installsMasterestaurant
- Weekly blind inventory on class-A items, counted by someone outside purchasing, double-blind on protein.
- Living recipe book with cost per gram kept current and yield factor measured per cut, the base of theoretical cost.
- Weekly theoretical-to-actual variance report by product family, with an alarm threshold at 1.5 points.
- Portioning scale on the six dishes carrying the largest protein volume on the menu.
- Void policy with manager code, a hard cap, and a monthly review of the ten largest voided tickets.
- A 45-minute cost meeting every Monday, with the number on the table and one action per drifting family.
Side-by-side comparison
| BEFORE · no shrinkage control | AFTER · Masterestaurant protocol at 60 days | |
|---|---|---|
| Theoretical vs actual food cost gap | ✕2.5 to 4.0 food cost points with no documented explanation | ✓0.8 to 1.2 points, inside acceptable operating noise |
| High-value inventory frequency | ✕Monthly, sometimes skipped; done by whoever buys | ✓Weekly and blind on 18 to 25 class-A items; done by someone outside purchasing |
| Estimated leak on 60,000 USD monthly sales | ✕1,500 to 2,400 USD a month nobody books | ✓480 to 720 USD a month, measured and reported |
| Protein portioning | ✕By the cook's eye; real variation of 12 to 20 % per plate | ✓Mandatory scale on 6 class-A dishes, variation under 4 % |
| Comps and voids control | ✕No log; the server voids from their own POS code | ✓Manager-code voids, hard cap at 0.8 % of daily sales |
| Effect on prime cost | ✕Prime cost of 66 to 69 %, outside the healthy range | ✓Prime cost of 60 to 62 %, with 3 to 4 points recovered |
| Owner time spent on the issue | ✕Reactive: 6 to 10 hours a month firefighting | ✓90 scheduled minutes a week reading one report |
| Translation into EBITDA | ✕Margin explained with anecdotes and gut feel | ✓2.5 to 3.5 EBITDA points recovered and traceable |
The figures behind the case
“We arrived at 33.1 % food cost and total certainty that the meat supplier was the problem. Week one of blind inventory showed something else: 41 kg of tenderloin more in theory than in the stockroom, 18 % bar variance and 62 comps in a single month that nobody had authorized. I fired no one. I put scales on six dishes, a manager code on voids and a closing count at the bar. In 60 days we hit 29.8 % and recovered 2,180 USD a month; month three closed at 29.1 %.”
How to close ant-theft shrinkage in 60 days, step by step
Three things must exist before your first count, and without them the rest is theater. One: a standard recipe book for the 20 dishes carrying 80 % of your sales, with real gram weights and last month's purchase prices. Two: yield factor measured per cut, weighing input against usable output for every protein, because a tenderloin yielding 86 % costed at 100 % invents a gap that does not exist. Three: your class-A item list, the 18 to 25 SKUs that typically hold 70 % of stockroom value. DELIVERABLE: a signed theoretical cost sheet per dish. CHECKPOINT: no menu item exceeds 32 % theoretical food cost; anything above gets redesigned or repriced before you move on. COMMON ERROR: costing with list prices instead of the price you actually paid after discounts.
Count class-A items every Monday before opening, same format and same hour, and count BLIND: whoever counts never sees the system's theoretical balance. Do not let the buyer count. Load the count, let the system calculate actual consumption, then compare it against theoretical consumption derived from sales mix times recipe. DELIVERABLE: a weekly variance report by family —protein, dairy, liquor, dry goods— in units and in dollars. CHECKPOINT: by the end of week three you hold three comparable readings and know which family concentrates more than 50 % of the leak. COMMON ERROR: changing the count format between weeks, which makes those three readings incomparable and drops you back to square one.
With the guilty family identified, attack the process. Put portioning scales on the six dishes with the highest protein volume and train gram weights across two shifts, not through a memo. Install a waste sheet in the kitchen where everything discarded gets logged and weighed: trim, expired product, returned plate, ticket error. Whatever leaves through the back door gets weighed. DELIVERABLE: a daily waste sheet signed by the shift chef, plus a 10-plate portioning sample each week. CHECKPOINT: weight variation between portions of the same dish falls under 4 %, and documented waste explains at least 60 % of the protein family gap. COMMON ERROR: punishing the first high waste log, because the team then stops logging and you go blind.
The bar runs its own arithmetic and deserves its own protocol. Open-bottle count at closing with a level rule or scale, mandatory jigger on menu cocktails, liquor variance calculated weekly against ounces sold. In parallel, close the POS: voids only with a manager code, comps with a mandatory reason, hard cap at 0.8 % of the day's sales. DELIVERABLE: a liquor variance report plus the ten highest-value voided tickets of the month, reviewed one by one. CHECKPOINT: liquor variance under 5 % and comps inside the cap for three consecutive weeks. COMMON ERROR: leaving the manager code taped to the monitor, which is the most elegant way to have no control at all.
Any control that depends on your presence dies the day you travel. Set a 45-minute cost meeting every Monday with three numbers on the table: actual weekly food cost, theoretical-to-actual gap by family, month-to-date prime cost. One action per drifting family, with an owner and a date. Close the loop by carrying the saving into the P&L, because one recovered food cost point on 60,000 USD of sales is 600 USD dropping straight to EBITDA. DELIVERABLE: a one-page minute with three figures and the week's actions. CHECKPOINT: the theoretical-to-actual gap stays under 1.2 points for four consecutive weeks. COMMON ERROR: celebrating one good month and dropping the weekly count, which is exactly when the leak returns.
And with AI?
Project your food cost, spot margin leaks and simulate pricing scenarios in minutes. Diego F. Parra is an expert in AI applied to restaurants.
Free tools to apply this now
Ecosystem tools to sustain the control
No tool counts inventory for you, and distrust anyone promising otherwise. What the Masterestaurant ecosystem tools do is sustain discipline: turn weekly variance into an economic decision, project what each recovered food cost point is worth in your cash box, and keep the recipe book a living measuring stick rather than a dead file on the chef's desktop.
Frequently asked questions on shrinkage and ant theft
How do I know whether my restaurant has ant-theft shrinkage or just buys expensive?
How do I know whether my restaurant has ant-theft shrinkage or just buys expensive?
By comparing theoretical cost against actual cost. When purchase prices rise, theoretical cost rises alongside actual cost and the gap between them stays flat. When the gap widens beyond 1.5 food cost points with no price change, you have product leaking, not inflation. One week of blind inventory settles that question.
How much does an average restaurant lose monthly to uncontrolled shrinkage?
How much does an average restaurant lose monthly to uncontrolled shrinkage?
Between 2.5 and 4 food cost points, which on 60,000 USD of monthly sales means 1,500 to 2,400 USD. The National Restaurant Association estimates internal theft and shrinkage take roughly 4 % of sales in full service. That money already sits inside your operation and only needs a measuring stick to appear.
Do cameras work for controlling ant theft in the kitchen and bar?
Do cameras work for controlling ant theft in the kitchen and bar?
Alone they help little; as backup they work well. A camera documents a single event, while ant-theft shrinkage is a drip of grams and ounces no recording reveals. Effective control is arithmetic: weekly blind inventory, a living recipe book, variance by family. Install measurement first and use video only to confirm a case the number already flagged.
Should I fire the team when the first count shows high variance?
Should I fire the team when the first count shows high variance?
No, and doing so usually gets expensive. That first high variance mixes recipe errors, a badly calculated yield factor, over-portioning and unlogged comps, all before any pilferage. Fix processes for 60 days, measure again, and only then judge people on clean evidence. Replacing a line cook costs more than one month of the leak.
How often should I run inventory for the control to actually work?
How often should I run inventory for the control to actually work?
Weekly on 18 to 25 class-A items, plus a full monthly count. Frequency matters more than completeness: an imperfect weekly count catches the leak in seven days, while a perfect monthly count catches it after roughly 2,000 USD are gone. Start with protein and liquor, which hold most of the value at risk.
Sector data 2026 (official sources)
Verifiable industry benchmarks from official, non-commercial sources (government, industry associations, market research) - not competitors.
| Metric | Benchmark 2026 | Source |
|---|---|---|
| PIB de alojamiento y preparación de alimentos y bebidas en México (3T 2025) | $838,530 millones MXN (+4.85% interanual) | Data México — Secretaría de Economía 2025 |
| Ticket promedio en restaurantes de servicio rápido (QSR) en EE. UU. (2025) | $8–$12 por persona | One Haus — Rising Check Averages |
| Ticket promedio en restaurantes fast casual en EE. UU. (2025) | $11–$16 por persona | One Haus — Rising Check Averages |
| Ticket promedio en restaurantes casual dining en EE. UU. (2025) | $15–$35 por persona | One Haus — Rising Check Averages |
| Ticket promedio en restaurantes de alta cocina (fine dining) en EE. UU. (2025) | Más de $60 por persona (a menudo $50–$150+) | One Haus — Rising Check Averages |
| Tasa de incumplimiento (default) de préstamos SBA para restaurantes en EE. UU. | 12%–15% en condiciones económicas normales | Crestmont Capital — SBA Loan Default Rates by Industry 2026 |
Related content
Grow your restaurant with the Masterestaurant method
Applied in +8.400 restaurants across 43 countries.
