In summary
What you need to know
Practical ways to improve occupancy, spend and protected revenue using existing capacity.
- Optimise inventory before adding capacity
- Protect peak demand selectively
- Design upsells around deliverability
- Best for
- Hospitality operators reviewing revenue management
- Reading time
- 4 min read
- Last reviewed
- 2 August 2026
Share this guide
Revenue growth does not always require more seats. Often it comes from selling existing inventory more deliberately and removing preventable leakage.
01
Improve the booking mix
Release inventory in stages, preserve valuable table combinations and pace arrivals. Use a waitlist to refill cancellations and keep direct website availability accurate.
- Protect large-table combinations
- Open lower-demand times strategically
- Review source and party-size mix
02
Protect committed revenue
Apply deposits, card guarantees or minimum spend to premium bookings. Automate reminders and make cancellation easy so released tables return to sale sooner.
Experiment register
Test one revenue lever without losing the guardrail
Every experiment needs one commercial outcome and one service-quality measure.
| Experiment | Primary metric | Guardrail |
|---|---|---|
| Release held tables earlier | Accepted peak demand | Seating delay |
| Offer an early package | Off-peak contribution | Full-price displacement |
| Add a celebration extra | Net attachment value | Fulfilment errors |
| Change booking duration | Sellable seat-hours | Guest complaints |
03
Increase value per visit
Offer relevant extras such as celebration packages, premium areas or pre-ordered items during booking. Keep choices limited and operationally deliverable. An upsell that surprises service staff is not incremental revenue.
04
Build repeat demand
Use guest history to recognise regulars, invite suitable segments to quieter services and measure repeat behaviour. Direct relationships reduce dependence on paid marketplace demand.
05
Procurement and operating depth
Create a small experiment register with hypothesis, affected inventory, start date, owner, primary metric and guardrail. Examples include releasing protected tables earlier, adding an off-peak package or offering a paid extra. Record other changes such as menu price, staffing or advertising so the review does not attribute every movement to the experiment. One clean test produces more learning than nine simultaneous tactics.
Venue-specific application
A realistic operator example
A venue tests one change per service segment: a better direct-booking call to action for lunch, a waitlist for Friday dinner and a paid celebration add-on for weekend bookings. Each tactic has a baseline, an owner and one primary metric. After six weeks, the team keeps the waitlist because it recovers cancelled covers, rewrites the lunch widget because conversion is unchanged and retains the celebration package because contribution exceeds fulfilment cost.
- Choose one constrained service to improve
- Name the behaviour each tactic should change
- Set a baseline and guardrail
- Avoid running overlapping tests on the same inventory
- Include labour and fulfilment cost
- Document the keep, change or stop decision
What to measure
Signals that belong in this review
Next operational step
Use the relevant UpSalt workflows
- Optimise inventory before adding capacity
- Protect peak demand selectively
- Design upsells around deliverability