In summary
What you need to know
Use demand, time and table inventory to improve revenue without compromising hospitality.
- Treat tables and time as linked inventory
- Shape demand with targeted rules
- Balance revenue with operational capacity
- Best for
- Hospitality operators reviewing revenue management
- Reading time
- 4 min read
- Last reviewed
- 2 August 2026
Share this guide
Restaurant yield management aims to sell the right capacity, at the right time, under the right conditions. Unlike hotels, restaurants manage combinations of tables, party sizes and meal durations inside short service windows.
01
Understand constrained inventory
A four-seat table sold to two guests may block a later party of four. A long booking at 20:00 can remove the possibility of two turns. Map these opportunity costs before changing prices or policies.
02
Shape demand
Use availability, pacing, packages, minimum spend or deposits to direct demand. Offer attractive early or late times instead of simply closing the peak. Apply conditions transparently and only where the value justifies them.
Seat-hour model
Compare contribution using time as well as covers
A table used for a quick lunch and the same table used for a tasting menu are different inventory products.
| Service product | Contribution | Seat-hours used |
|---|---|---|
| 2 guests, 75 min | €54 | 2.5 |
| 4 guests, 105 min | €132 | 7.0 |
| 2 guests, 150 min tasting | €120 | 5.0 |
| Decision metric | Contribution divided by seat-hours | Compare within similar experiences |
03
Measure contribution
Covers alone do not show performance. Review average spend, duration, no-show rate and contribution by service, source and area. Include the cost of marketplace commission and discounts when comparing channels.
04
Protect the experience
Shorter turns and tighter pacing have limits. Monitor waiting time, kitchen load, staff feedback and guest satisfaction. Sustainable yield comes from removing avoidable gaps, not pushing every table beyond service capacity.
05
Procurement and operating depth
Use seat-hours carefully when experiences have different durations and values. A quick lunch and a tasting menu do not consume identical inventory even if both use the same table. Build contribution and duration assumptions by service segment, then test whether availability rules actually steer demand as intended. If guests are simply displaced to unavailable searches, the strategy has reduced access without creating value.
Venue-specific application
A realistic operator example
A 60-seat restaurant has strong demand from 20:00 to 21:00 but spare capacity at 18:30. Rather than discount the entire evening, it opens a limited early package, protects table combinations for peak four-tops and sets realistic durations by party size. The team measures contribution per available seat-hour and seating delay. If revenue rises but queues and late seating worsen, the pacing rule, not simply the price, needs adjustment.
- Map available seat-hours by service
- Identify demand the venue cannot currently accept
- Calculate contribution rather than revenue alone
- Test targeted availability or package changes
- Protect kitchen and service capacity
- Review guest experience alongside financial results
What to measure
Signals that belong in this review
Next operational step
Use the relevant UpSalt workflows
- Treat tables and time as linked inventory
- Shape demand with targeted rules
- Balance revenue with operational capacity