Back to blog
Guide

The Guest Who Books and the Guest Who Walks In Are Different Businesses

Booked and walk-in guests differ in spend, return rate and cost to acquire — but most venues run one set of numbers for both. How to split them, what the split usually reveals, and why the mix decides your door policy.

Two guests spend the same amount on the same night. One booked three weeks ago; one walked past and came in.

They are not the same guest, and treating them as one number hides most of what you need to know.

They differ in what they spend, whether they come back, what they cost to acquire, and how much control you have over whether they show up at all.

Four ways they differ

BookedWalk-in
SpendUsually higher — intent was formed in advanceUsually lower, higher variance
Return rateHigher. They chose you specificallyLower. They chose the street
Acquisition costReal — a channel delivered themNear zero, but not free (location, frontage, door)
PredictabilityYou know before the nightYou do not, which is the whole staffing problem

No line says one is better. A room that is all bookings is fragile — cancellations hit directly. A room that is all walk-ins cannot plan anything.

The mix is a choice. Most venues have never made it deliberately.

The number to split first

Revenue per head, booked vs walk-in

Run it for a month. The gap is usually larger than people expect, and it changes what the door is worth.

Then the second one, which matters more:

Return rate within 90 days, booked vs walk-in

This is where the real difference sits. A walk-in who returns is worth as much as a booking. A walk-in who does not is a single transaction with no follow-up path — you often do not even have a name.

The conversion nobody measures

The most valuable move in this whole area:

Walk-in → booked conversion
        = walk-ins who later made a booking ÷ total walk-ins

A walk-in you convert to a booking is the cheapest acquisition available. They already came. They already liked it. You just need a reason to capture the contact.

Most rooms capture nothing from a walk-in, then pay a channel to reach the same person later.

What captures it, in rough order of effectiveness:

A reason to give a phone number   … a booking for next time, at the table
A reason to give it at the door   … a guest list, an early-entry offer
A follow-up that is worth having  … not a broadcast. Something specific

The phone number is the asset. Everything downstream — return rate, lifetime value, channel attribution — depends on being able to recognise the same person twice.

The mix decides your door policy

Once you have the split, door decisions stop being about feel.

Bookings under-deliver (no-shows high)  → hold fewer tables, take more walk-ins
Walk-in spend well below booked         → walk-ins are filling space, not paying for it
                                          → raise the door or tighten entry
Walk-in return rate near booked         → your walk-ins are locals, not tourists
                                          → capture contacts aggressively
Walk-in return rate near zero           → transient traffic
                                          → maximise first-visit spend, do not chase retention

Each of these is a different room and a different policy. One aggregate number cannot distinguish them, which is why "should we take more walk-ins" gets argued rather than answered.

Recording it costs one field

Booked / walk-in, per guest, per visit

One field at the point of entry or first order. Everything above computes from that plus what you already have.

And it must be per visit, not per guest. A guest can walk in the first time and book the second — that transition is the conversion you most want to measure, and a guest-level flag erases it.

The trap

Do not conclude from one month. Walk-in mix is seasonal, weather-dependent, and event-dependent to a degree that makes a single month misleading.

Three months minimum, and compare like weekdays. A Saturday in December and a Tuesday in February are not the same experiment.

The system we built

tasteck is a booking and analytics system for night venues, built by people who ran them for sixteen years and grew from ¥200 million to ¥1.2 billion a year — six-fold, by attacking the business with systems rather than by pushing harder on sales.

This split was one of the levers. Once booked and walk-in were separate lines, the door policy stopped being a monthly argument and became a monthly decision.

What it does here: a booking screen wired to inbound calls, so a phone booking becomes a record without anyone retyping a number — which is where most of the contact capture actually happens. Guest records that persist across visits, so the walk-in who returns is recognised. Source recorded per booking, so channels are attributable. Visit history per guest, so first-visit type and later behaviour are both available.

What it does not do: there is no door-entry terminal and no automatic walk-in counter. The booked/walk-in flag is a field someone sets. What the product supplies is the guest identity that makes the flag worth setting.

The output no one else produces

tasteck outputs the maximum you can spend on each marketing channel next month, as an amount in your currency.

This is exactly where the split pays. If walk-ins convert to bookings at a decent rate, your frontage and location are a channel — one with a real cost (rent) and a computable return, sitting alongside the paid ones.

Most operators never price their own door. It is often the best-performing channel they have, and it never appears in a marketing budget.

Nothing else in the nightlife category produces that figure.

Ask it from ChatGPT

tasteck connects to ChatGPT over MCP: ask your numbers as a question and the answer comes back in the chat — how booked and walk-in spend compared last month, which walk-ins later booked, what each source delivered.

Measured against every vendor listed on Japan's principal nightlife-industry directory, this is the first implementation of it in the category, and the same interface is callable from anywhere rather than being tied to one assistant.

Multi-language is built in, the operating surface itself, with your language set put in place during onboarding.

From $34 a month for up to two venues. Thirty days free on every plan, cancel any time.Pricing

Start this month

  1. Add one field: booked or walk-in, per visit. Not per guest.
  2. Split revenue per head by that field. The gap will surprise you in one direction or the other.
  3. Split 90-day return rate the same way. This is the number that decides the policy.
  4. Compute walk-in → booked conversion. The cheapest acquisition you have.
  5. Wait three months before changing the door. Walk-in mix is seasonal.

Read next


On benchmarks. No target walk-in ratios, conversion rates, or spend gaps appear in this guide. We do not have a dataset broad enough to publish them, and they vary enormously by location, format, and foot traffic. Three months of your own split, compared on like weekdays, will settle a door argument that averages cannot.

Free, no signup, ~5 minutes

Map out your operations in 5 minutes

Eight questions cover reservations, customer management, shifts, and settlement. Results shown instantly with industry benchmark. Sales emails only if you request them.

Your answers are not stored. The assessment runs entirely in your browser.

Try tasteck free for 30 days

No credit card required. Full access to reservations, cast shifts, dispatch, and analytics.

  • No card required
  • Free data migration support
  • All features unlocked for 30 days