Hotel restaurants as local listings: 15% margin test—list or skip Food and Beverage (F&B)

This guide gives hotel operators a 15% contribution margin test for deciding whether to list an F&B outlet as a standalone local listing.

It covers the 90-day outlet-level data check—revenue minus food cost, labor, and allocated overhead—and when review dilution and ranking weight make skipping the better call.

How F&B listings enter local ranking

Before you decide whether your hotel restaurant deserves its own listing, you need to understand how it already exists in local search. Map platforms — Google Business Profile, Yelp, and TripAdvisor — treat a hotel restaurant as a separate place entity from the hotel itself. Each outlet gets its own category, its own review stream, and its own ranking signals, evaluated independently of the property listing. That separation is the mechanism: once an outlet is indexed as its own entity, it competes in local results on its own merits, and the hotel's authority does not automatically prop it up.

The first check is a duplicate audit, not a creation task. Search the map platforms for your outlet's name plus your address before you claim or build anything. Most hotel restaurants already have an auto-generated listing — created from user check-ins, menu scrapes, or reservation data — sitting unclaimed. If one exists, claim and correct it rather than creating a second listing, which splits reviews and confuses the entity matching that platforms use to consolidate places.

Once you've confirmed the entity exists, the question is whether it should be actively managed as a standalone listing, and that answer comes from the outlet's own economics. Pull 90 days of outlet-level data and run the margin test described in the costs section of this guide. To source the inputs credibly, use published benchmarks rather than gut feel: Restaurant365 publishes prime cost benchmarks in its guidance on calculating restaurant prime cost, and NetSuite publishes COGS and labor benchmarks by segment in its restaurant benchmarks guide — both compiled in Stockcount's benchmark roundup. Pull the segment matching your outlet type (full-service, bar, café) before you judge your own numbers.

If the outlet's contribution margin clears the threshold on its own P&L, the standalone listing is worth managing: it can rank, accumulate reviews, and drive incremental covers as an independent entity. If it doesn't, the listing still exists — you can't delete an auto-generated entity — but the ranking weight it carries and the review stream it dilutes cost more than the covers it drives. In that case, fold the outlet's presence into the hotel listing's own review and category signals instead of investing in the separate profile.

The practical sequence: audit for existing listings, claim what exists, run the margin test on real outlet data benchmarked against Restaurant365 and NetSuite segment figures, then decide whether to manage the entity standalone or let the hotel listing absorb it. The mechanism is fixed by the platforms; your only lever is whether the outlet's economics justify feeding it.

The evidence: margin math from operators

The margin test is not an abstraction — it is the same arithmetic operators already run when they justify any investment in the restaurant. TableMagic's restaurant inventory guide works the math explicitly: if a tool trims food cost by even two points on a restaurant doing $1M a year, that is $20,000 back, several times the typical software cost (source: tablemagic.co). That is contribution-margin thinking in miniature — a small percentage change on a known revenue base, measured against a known cost. The 15% test applies the identical logic one level up: instead of asking whether a tool pays for itself, you ask whether the outlet itself clears a margin that justifies its own listing.

The same source reports that 76% of operators say technology helps their margins (source: tablemagic.co). Read that statistic carefully, because it cuts both ways. Belief is widespread, but belief is not measurement. An operator who "feels" the restaurant is profitable cannot run the 15% test — the test requires an outlet-level P&L with revenue, food cost, labor, and allocated overhead separated out, not a gut sense that the dining room "does well at breakfast." If three-quarters of the market believes in margin tooling but far fewer can produce a clean outlet P&L on demand, the bottleneck is not technology adoption; it is attribution.

Here is the check that separates the two. Take your restaurant's revenue for the measurement window, subtract food cost, subtract the labor actually charged to the outlet, subtract the overhead you can defensibly allocate to it, and divide what remains by revenue. If the result clears 15%, the outlet has a margin story strong enough to stand on its own listing. If it does not, the $20,000-style arithmetic above tells you what to fix first: two points of food cost on a seven-figure revenue base is real money, and recovering it changes the listing decision more than any marketing tactic will.

The comparison below shows how the same two-point move plays out at different revenue bases — the same percentage discipline, scaled:

Notice what the table implies for smaller outlets: the absolute dollars shrink faster than the margin percentage does. A two-point save on a quarter-million-dollar outlet is still a two-point save, but it is $5,000 — which is why the 15% threshold, not the dollar figure, is the right gate for the listing decision. Percentage margin travels across revenue scales; dollar intuition does not.

One caution before you act on any of this: the $20,000 figure is a worked example of what a two-point food-cost improvement returns, not a promise of what any tool or listing will deliver for your outlet. Your own P&L is the only number that counts. Run the division, get the percentage, and let that single figure — not belief, not the 76% — make the listing call.

List, fold in, or fix first: compared

Once the 90-day margin number is on the page, the decision narrows to three moves, and each has a different winner condition. The question is not which option sounds ambitious — it is which one the margin test and the outlet's review position actually support. Running all three against the same evidence keeps a property from listing a sub-15% outlet because a competitor did, or from burying a high-margin restaurant inside the main profile.

Option A, listing standalone, wins when contribution margin clears 15% and the outlet has or can earn its own review stream — enough independent review velocity to build a position without borrowing the property's name. The cost is duplicate management: hours, menus, photos, and owner responses maintained across every platform hosting the profile, plus a second set of accuracy checks each time anything changes. Where review velocity cannot be sustained independently, that profile stalls and the management cost buys nothing.

Option B, folding the restaurant into the property profile, wins when margin sits below 15% but the outlet still drives room demand. The restaurant becomes an amenity signal on the main listing rather than a ranked entity. The check is traceability: front-desk questions, reservation notes, or a guest-source field captured at arrival. If margin is under 15% and that link cannot be shown, neither listing nor folding is the answer — the outlet has a cost problem or a demand problem, and a profile change settles neither.

Option C, fixing margin first, wins when margin is below 15% and food cost is the driver. The diagnostic is line-specific: rerun the 90-day test with the COGS line isolated and compare it against segment benchmarks, the way the Stockcount cost guide points operators to Restaurant365's prime-cost method and NetSuite's segment figures. When food cost is the outlier, the gap is a purchasing, inventory, or portioning problem, and the arithmetic worked in the margin-math section shows how few points of COGS improvement move the result. Set a re-test date rather than a launch date.

Name the winner this way: list standalone when margin is at or above 15% and independent review velocity exists or can be earned; fold into the property profile when margin is below 15% but the outlet demonstrably drives room demand; fix margin first when it is below 15% and food cost — not demand — holds it there. In every branch, the test runs before the listing does.

Costs and the numbers that matter

The margin test only tells you something if each of its four inputs comes from a ledger. Guess at any one of them and you are deciding whether to build a standalone local listing on a number nobody can defend six months later. Here is each input line, where to source it, and the check that keeps it honest.

Outlet revenue. Pull 90 consecutive days of net sales at the outlet level from your POS. TouchBistro and KOA POS both include outlet-level analytics inside the platform — Business.com's 2026 TouchBistro review and KOA's product spec list analytics as a built-in feature — so no additional tool purchase is needed to get this figure. Reconcile it against the outlet's deposits and comps for the same window before you use it.

COGS. Resist estimating this from a menu-cost spreadsheet. Run the period through a free calculator such as the one at trackitweekly.com, using the standard formula: (beginning inventory + purchases − ending inventory) ÷ revenue. The result only holds if both inventory counts come from the same counting method at each end of the window.

Labor. Total it from outlet payroll records, not just hourly wages: include salaries assigned to the outlet, payroll taxes, and benefits. Restaurant365's prime-cost guidance and NetSuite's restaurant benchmark set, both cited in Stockcount's cost guide, treat COGS and labor as a single prime-cost figure for exactly this reason — a test that stops at food cost understates the number that decides whether you clear 15%.

Allocated overhead attributable to the outlet. This is the line operators skip most often, and it flips the answer most often. Include only costs that move with the outlet: its share of hotel rent or square footage, utilities, POS and reservation software subscriptions, and any portion of shared management salary you can tie to outlet hours. Then stress-test the allocation: if the outlet closed tomorrow, which of these lines actually disappears? Cut the rest.

Run all four lines on the same 90-day window: revenue minus COGS, labor, and the trimmed overhead allocation, divided by revenue. That quotient is your contribution margin. At 15% or above, the outlet's own P&L can carry a standalone listing; below it, the margin test says the listing has to pay for itself before anything else does.

What the evidence does not establish

Before you commit to the 15% rule, be honest about what it does not prove. No source in the operational literature — not the TableMagic inventory guide, not the Stockcount cost benchmarks, not the POS and analytics vendors — publishes a figure for how many incremental covers a standalone local listing actually drives for a hotel restaurant. The upside side of the ledger is unmeasured. Treat any vendor claim of listing-driven traffic as a hypothesis, not a fact, and verify it yourself: pull 90 days of outlet covers before you create the listing, then 90 days after, and compare the same day-of-week windows. If covers do not move, the listing's only value is visibility you cannot bank.

The downside is equally undocumented. No grounding source quantifies a review-dilution penalty for splitting reviews between the hotel listing and the outlet listing — there is no published percentage of rating erosion or review-velocity loss when a restaurant separates from its parent property. That silence does not mean the penalty is zero; it means nobody has measured it for you. Run your own check monthly: track review counts per entity side by side. If outlet reviews grow slower than hotel reviews after the split, that divergence is your dilution signal, and it is data no vendor will hand you.

The 15% threshold itself carries the same caveat. The margin inputs — revenue minus food cost, labor, and allocated overhead attributable to the outlet — are standard restaurant arithmetic, and the cost-control literature supports measuring them at the outlet level: Stockcount's cost guide points to prime cost and COGS benchmarks by segment, and tools like the trackitweekly COGS calculator exist precisely because operators need this number per unit, not per property. But the specific 15% cutoff is a decision rule, not a published benchmark. It is defensible because it forces the listing to clear a real P&L bar, not because a study validated it.

What the evidence does establish is narrower: TableMagic's guide shows that small margin improvements compound into real dollars — two points of food cost on a restaurant doing $1M a year returns $20,000 — and that 76% of operators believe technology helps. Belief in tools is not evidence about listings. Keep the two separate.

The practical takeaway: run the margin test on 90 days of outlet-level data, then treat the listing decision as a measured experiment with two open variables — covers and review velocity — each checked on its own calendar. If either check fails, you have learned the listing costs more than it returns, and no published figure was ever needed to find that out.

And the test worksheet

The worksheet is simple enough to run in one sitting, but only if you fill it in honestly. Pull 90 days of outlet-level data and lay the four lines side by side: revenue, food cost, labor, and allocated overhead attributable to the outlet. The test is subtraction, not judgment. Here is the filled-in example at the $1,000,000 annual revenue scale used in TableMagic's restaurant inventory guide.

Read the base case first: 100 − 32 − 30 − 25 = 13%. That is below the 15% line, so the outlet does not get a standalone local listing this quarter. The listing's ranking weight and the review dilution it would cause cost more than the incremental covers it drives at that margin.

Checkpoint 1 shows why the test is a gate, not a verdict. If food cost drops two points, from 32% to 30%, TableMagic's worked figure puts that at $20,000 a year back on a $1M restaurant — and the margin math moves to 100 − 30 − 30 − 25 = 15%. That clears the line. Re-run the test on fresh 90-day data to confirm the reduction is holding, then list the outlet.

Checkpoint 2 is the failure direction. If labor runs at 33% instead of 30%, margin falls to 100 − 32 − 33 − 25 = 10%, and even the two-point food-cost win only gets you to 12% — still short. In that state, a standalone listing amplifies an operation that is losing money on every incremental cover it attracts. Fix labor before touching the listing decision.

The cost of being wrong runs in both directions. List a sub-15% outlet and you split reviews and ranking signals across two entities for a restaurant that cannot profit from the traffic. Skip a 15%-plus outlet and you leave covers on the table while a competitor's restaurant ranks in your place. The worksheet makes both errors visible before you make either one — which is the entire point of running it quarterly rather than once.

Decision rules for the 15% test

The test resolves to one comparison, run on 90 days of outlet-level data: if the outlet's contribution margin is at or above 15%, claim or create the standalone listing — its own primary category, its own menu data, its own hours and photos. If it lands below 15%, fold food and beverage into the hotel listing as an amenity: a restaurant paragraph, a photo set, and menu highlights inside the property's profile. Treat the threshold as a switch, not a scale. A partial listing — a separate profile with no menu, no hours, and no owner responses — inherits the ranking and review weight of a standalone entity without earning much of the conversion benefit.

One override sits above the margin rule. If an auto-generated outlet listing already exists and carries reviews, claim it regardless of what the test says. An unmanaged listing is a liability whether or not you would have created one: guests keep posting to it, you cannot respond as the business, and the profile's categories, hours, and attributes stay outside your control. Claiming converts an orphaned profile into one you can edit.

Margins landing within two points of the threshold — the 13% to 17% band — should not be decided on the listing question yet. Fix the largest cost-of-goods gap first, then recompute. TableMagic's restaurant inventory guide is the practical starting point for locating that gap, because its size only becomes visible when purchasing is tracked at the item level rather than in monthly totals. A fix that moves an outlet from 14% to 16% changes the answer; a listing decision made before the fix locks in the weaker number for as long as the profile stays live.

Re-run the same 90-day test every quarter and record the result next to the previous one. Ranking weight and review history accumulate, and a standalone profile that drifts below the line is harder to unwind than one you never launched. Adopt a two-quarter confirmation before retiring an existing listing: a single soft quarter can reflect seasonality or one bad month of purchasing rather than a structural margin problem.

Keep the test auditable on one page: the 90-day outlet P&L, the test date, the margin, and the decision. When you claim a listing, note the category and menu data you loaded. When you fold, note where the amenity content sits on the hotel profile. Six months later, that page is the only record explaining why the outlet is listed the way it is.

What to do next

Quick answers

Also worth reading: Auditing Deliveroo and Wolt ranking disclosures under DSA Article 27: what restaurants can actually verify since 17 February 2024 — and what platforms still hide: Auditing Deliveroo and Wolt ranking · Duplicate local shop results: 90% corroboration favors entity-preserving merges: Duplicate local shop results: 90%