Back to blog
Guide

Pricing a Night Out Without Guessing

Most night venue prices were set by copying the room down the street and never revisited. How to test a price change safely, which items to move first, and why the menu item you are most afraid to reprice is usually the one that matters least.

Ask where a price came from and the honest answer is usually one of three: the room down the street charges that, it has been that since we opened, or someone picked it.

None of those is wrong to start with. All three are wrong to keep for four years while costs move.

The reason prices do not get revisited is fear, and the fear is specific: you cannot un-ring a price increase, and nobody knows what will happen.

You can find out, on one item, in three weeks, without risking the room.

Not every item is a pricing decision

Menu items do different jobs. Repricing them the same way is the mistake underneath most of the fear.

TypeWhat it doesPricing posture
AnchorWhat people check before deciding to comeMove carefully. This one they remember
VolumeMost units sold. Carries the margin by countMove in small steps, watch mix
MarginHigh margin, moderate volume. Quiet moneyMove first. Least risk, most upside
SignatureWhy they chose you. Little comparisonUnderpriced more often than not

Most operators are afraid of moving the anchor and never touch the margin items.

It is backwards. The anchor is the one price guests can quote from memory. The margin items are the ones nobody has a reference price for, and they usually have the most room.

What a price change actually does

Revenue change = (new price − old price) × new volume
               − old price × (old volume − new volume)

The second term is the one that scares people, and it is usually smaller than expected for a modest increase on a non-anchor item.

The measurement is not "did revenue go up." It is:

Units sold, before and after, same weekday, same weeks of the month
Revenue for that item, before and after
Mix share — did people switch to something else?

The third catches the failure mode nobody predicts. A price rise that pushes guests to a cheaper item with worse margin looks fine on the item and costs you money overall.

How to test one price safely

One item. Three weeks. Compared to the three before it.

Week 0     … record baseline. Units, revenue, mix share
Week 1-3   … new price
Compare    … same weekdays. Median, not mean

Rules that keep it honest:

  • Change one thing. If you reprice and add a promotion, you learn nothing
  • Do not announce it. An announced increase gets a reaction to the announcement
  • Pick a non-anchor item first. Learn the mechanics where the downside is small
  • Three weeks minimum. One week is noise; two is a trend you will misread

If units hold within a few percent and revenue rises, the price was low. That is the common outcome for margin items, and it usually surprises the person who was worried.

The item to move first

High margin / moderate volume / no obvious comparison / not what people ask about

A house cocktail. A premium mixer. An upgrade option. An extension.

Not the entry price. Not the standard course. Not the beer everyone knows.

And extensions are the most commonly underpriced thing in this business. A guest extending has already decided to stay. The decision was made before the price was quoted, which makes it the least elastic price on your list and often the oldest.

When not to reprice

Price is the wrong lever if:

Revenue per head is falling while volume rises   → capacity problem, not pricing
Return rate is falling                           → experience problem
Staff turnover is high                           → service problem, and repricing makes it worse
One channel is delivering low-value guests       → channel problem

Raising prices into a service problem accelerates it. The guests who leave first are the ones who were already marginal, and they are often the ones you needed.

The number that tells you whether it worked

Revenue per head, item-level margin, and mix share
— all three, three weeks after, weekday-matched

Any one alone can mislead. Revenue per head can rise while mix degrades. Item margin can rise while units collapse. The three together give you an answer you can act on.

And keep the record. In two years, when someone asks where the price came from, "we tested it in March 2026 and units held" is a better answer than "someone picked it."

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.

Pricing was part of it, and the discipline was the boring one: one item, three weeks, weekday-matched, written down.

What it does here: settlement broken out by line — course, extension, nomination, options, cosplay, transport, discounts and events — so item-level revenue and mix share are queryable rather than estimated. Courses defined with time and price, so a price change is a dated record. Revenue per head with weekday comparison. Guest records across visits, so you can see whether a price change affected return rate rather than just this month.

What it does not do: there is no A/B testing tool and no elasticity model. The three-week discipline is yours to run. What the product supplies is the line-item detail that makes before-and-after comparable at all.

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.

Pricing and acquisition are the same equation. The ceiling is lifetime value times target margin — so a successful price rise raises what you can afford to pay for every guest, on every channel.

Most operators treat them as separate projects. A five percent margin improvement changes the acquisition budget immediately, and that is usually worth more than the price rise itself.

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 that item sold before and after, what the mix looks like, whether return rate moved.

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 with one item

  1. Sort your items by margin and volume. Find the high-margin, moderate-volume, low-comparison one.
  2. Record three weeks of baseline before touching anything. Units, revenue, mix share.
  3. Change one price. Say nothing. Announcements produce reactions to announcements.
  4. Compare at three weeks, weekday-matched, median.
  5. Write down what happened. In two years this is the only record of why the price is what it is.

Read next


On benchmarks. No target margins, elasticity figures, or recommended price points appear in this guide. We do not have a dataset broad enough to publish them, and they vary enormously by market, format, and position. One item, three weeks, weekday-matched, in your own room, beats any published figure — and you can run it starting this week.

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