Target average ticket pricing: traditional method vs the Masterestaurant method

Step 1: add up your real fixed structure and add the profit you demand

Before touching a single menu price, take twelve months of expenses that exist even when the dining room stays empty: rent, base payroll, utilities, accounting, licenses, software, insurance and the loan payment. A 62-seat steakhouse in Bogota with 14 million pesos of rent, 38 million of fixed payroll and another 9 million in utilities and administration carries 61 million monthly that has nothing to do with how many people walk in. To that figure add the profit you DEMAND from the business, not the one you would like; if you want 15 % on sales and your starting point is 61 million, the target moves. The deliverable here fits on one sheet: a single line stating how much money the operation must produce each month before anything gets distributed. Verify it against last quarter's income statement, and if the gap exceeds 5 %, the number is badly built. Installed capacity is not seats, it is seats multiplied by real turns and by the days you actually open.

Step 2: measure the transactions your installed capacity can genuinely produce

Sixty-two seats with 1.4 turns at lunch and 0.9 at dinner produce 143 covers a day, and across 26 effective operating days that reaches 3,718 monthly transactions, not the 5,580 that optimistic arithmetic of two turns per service throws out. Pull ninety days of POS history and keep the 50th percentile, never the best month. Worth remembering that casual dining traffic in the United States fell 4.3 % year over year in 2025 according to Rezku's QSR Industry Report, so projecting traffic growth to make the model work is manufacturing an accounting lie. The deliverable is one sustainable monthly transaction figure; verify it by comparing against the three weakest months of the year. Your target average check comes from dividing fixed structure plus demanded profit by sustainable transactions, adjusted for the contribution margin your menu mix leaves behind.

Step 3: divide, and get the target average check before any price

With 61 million in fixed cost, 9 million of demanded profit and 3,718 transactions, the business needs 18,827 pesos of contribution per guest; if your average food cost runs 28 %, every guest must leave 72 % of what they pay, and the target jumps to 26,150 pesos of gross contribution, meaning 58,000 pesos of sales once payment processing, waste and real shrinkage get loaded in. The steakhouse was selling at 41,000. That 17,000-peso hole per guest, multiplied by 3,718 transactions, is the 4 million monthly loss no squeezed supplier was ever going to hand back. The deliverable is one written figure against which the whole menu gets judged. A restaurant in 2026 does not sell through one channel, and averaging dining room with aggregator is the most elegant way of hiding the problem from yourself.

Step 4: split the target by channel, because a single average hides the problem

The dining room leaves the check intact; your own delivery subtracts packaging and driver; the aggregator takes between 18 % and 30 % in commission, so a 58,000-peso platform order deposits 42,000 and demands a gross check of 74,000 to produce the same contribution the dining room does. With 70 % of American diners having ordered delivery in the past month according to Escoffier's 2025 dining trends report, that channel is no longer marginal and cannot be treated as surplus. Calculate a target check PER channel plus an expected share for each. The deliverable is a three or four row table with target check, commission and net contribution; verify it against last month's actual platform settlements. Once the target figure sits in your hand, menu engineering stops being an aesthetic exercise and acquires an arithmetic goal.

Step 5: redesign the menu toward the check, not the check toward the menu

If you need 58,000 pesos and your average entree runs 34,000, the rest has to come from appetizers, beverages and desserts that today probably nobody even suggests: a 9,000-peso drink at 82 % margin, a shared starter at 16,000, a dessert at 12,000. Push beverage penetration from 40 % to 65 % and the check moves 2,250 pesos without touching a single price. Diego F. Parra has worked this order with owners for twenty years inside the Masterestaurant framework, and the sequence never changes: first the figure the business needs, then the menu design that produces it. The deliverable is a redesigned menu whose simulated check —price times sales probability of each item— hits the target with under 3 % of slack. The costliest error is loading payroll, rent and utilities onto the plate: that destroys traceability, because when the month closes badly you can no longer point at whether it was rent, dead labor hours or the sales mix.

The five errors that sink the calculation, and how you avoid them

The second is using your best month as the transaction base, and the third is forgetting payment processing, which at 2.8 % to 4.5 % eats an entire dish's margin every twenty covers. Fourth, more subtle: ignoring that a 28 % food cost is a weighted average that shifts when the mix shifts, so selling more of the cheap dish lowers the check and raises relative cost at the same time. And fifth is treating tips as revenue. With the independent restaurant sector contracting 2.3 % in 2025 according to Technomic, the margin for error on these five things is gone. Suppose you ran the calculation and the target check lands at 58,000 pesos, but your market will not pay more than 46,000 without occupancy collapsing. That result does not invalidate the method, it confirms it: the business model does not close with that structure, and you just found out on a sheet of paper instead of finding out two years from now.

What happens when you cannot reach the target check?

So the levers move elsewhere.

Either you cut fixed cost —renegotiate rent, rethink the org chart, kill the lunch shift if it contributes 18 % of sales with 40 % of labor cost—, or you raise transactions by stretching turns with reservations and seatings, or you open a channel with lower cost to serve. Loyalty genuinely helps: 55 % of loyalty customers visit at least twice a month according to Restroworks 2025, and that frequency converts into transactions that lower the required check. The exercise is finished when you can answer, without opening a computer, how many people you need to seat today to avoid losing money. On paper, verification carries six marks: fixed structure matches last quarter's income statement within 5 %; projected transactions do not exceed the 50th percentile of ninety days of history; the target check is calculated per channel rather than as a single average; the simulated menu reaches that figure with under 3 % slack; no indirect cost ended up loaded onto a dish costing sheet; and a review date exists, because rent climbs and mix drifts.

Closing checklist: how you know the exercise came out right

Put the target figure on the POS screen and compare it against the real check every Monday. If the gap exceeds 6 % two weeks running, the problem is not team motivation: the model moved and step two needs redoing. The direction of travel. Traditional pricing runs from plate to business and the Masterestaurant method runs from business to plate. It reads like a matter of sequence and it is the difference between finding the problem in January or in December, because the target ticket can be computed before opening, with the menu still in a Word file, while markup only gets validated once three months of sales and accumulated losses sit on top of it. How costs that do not live on the plate get handled.

Four differences that change how the month ends

Payroll, rent and utilities are NOT charged to the plate, and that rule irritates people because it looks like margin being given away; what it actually does is hand traceability back, because when the month closes badly you can point at rent, at payroll stretched across dead hours, or at a fallen ticket, instead of staring at an aggregate percentage that explains nothing. The unit of measurement. Markup measures percentage over cost while the target ticket measures currency per transaction and per seat-hour, the only unit comparable to a rent that also gets paid in currency. A plate at 24 % food cost selling four times a day contributes less cash than one at 31 % selling thirty, and the isolated percentage will tell you the exact opposite. Channel granularity. Target average ticket pricing gets computed per channel —dining room, own delivery, aggregator, dark kitchen— because cost to serve shifts radically between them, and a virtual restaurant business model inheriting dining-room prices hands over 18 to 30 commission points nobody ever decided to give.