3 June 2026

How Vacation Rental Hosts Can Earn Commission from Restaurant and Experience Recommendations

You are already running a referral channel — you just are not getting paid for it. Here is how to convert the informal recommendations you already make into a commission arrangement, how to approach local businesses, and what the model realistically pays out at modest scale.

The restaurant five minutes from your property has had twelve of your guests through its door this year. You know this because the owner mentioned it last month — he recognises the apartment number on the reservations. He thanked you. He did not pay you. You have been the highest-converting marketing channel he has, and the relationship is operating on goodwill.

This pattern is so common in short-term rental hospitality that most hosts do not notice it as a missed revenue opportunity. They recommend local restaurants because guests ask. They recommend experiences because it is what good hosts do. The recommendations convert. The local business benefits. And the host gets a thank-you, sometimes a free drink the next time they visit, and zero share of the value they created.

The structural reason this happens is that hosts have not been taught to think of their guest channel as a commercial referral surface. They think of it as part of the service they provide. Restaurants and experience operators, meanwhile, are entirely used to paying commission for referred customers — they pay it to OTAs, to concierge services, to influencer partnerships, to local guide apps. The host is the only category that is not at the table, even though their conversion rate is higher than any of the others.

This article covers why this asymmetry exists, how to convert informal recommendations into commission arrangements, the practical difference between restaurant referrals and experience referrals, and what the realistic payouts look like for a host operating at modest scale.


Why Most Hosts Already Have This Revenue Stream Without Realising It

A vacation rental host already does the work of a referral channel. They have a captive audience — guests staying nearby, in active decision-making mode about where to eat and what to do, who trust the host's local knowledge by default because they have already booked the property. They send those guests, at scale, to a small set of local businesses they like. They do this consistently across the year.

That is, structurally, a referral business. The host is functioning as a curated discovery channel for a specific geographic and demographic segment. The only thing missing is the commercial layer that would convert the referral activity into income.

The reason most hosts have not added that layer is rarely that they object to the idea. It is that they have not framed what they are doing as a referral channel — they have framed it as helpfulness. Helpfulness does not generate invoices. Once the framing shifts, the conversation with the local business becomes straightforward, because the business is already paying for exactly this from other sources.

For the broader picture of how this fits into the host's revenue mix, see How Vacation Rental Hosts Can Earn Referral Income from Local Business Recommendations.


How the Commission Model Actually Works in Hospitality

There is no single standard for how referrals from a host to a local business get paid out, but the patterns cluster into three forms.

Per-cover or per-attendee commission. The business pays a fixed amount for each guest sent. Restaurants often pay a flat fee per cover or per table — five to fifteen euros per cover is a common range in European markets, more in higher-margin venues. Experience operators sometimes pay a flat fee per attendee.

Percentage of bill. The business pays a percentage of what the referred guest spends. This is more common with experience operators (tours, classes, tastings) where the booking value is known. Ten to twenty percent is a common range. It is less common with restaurants because attributing the exact spend per cover requires the restaurant to surface that data, which most do not want to do.

Fixed monthly retainer. The business pays a flat monthly fee in exchange for being the host's primary recommendation for a category — "the restaurant" or "the wine bar" or "the cooking class." This is rare but exists, usually for high-volume properties or hosts running multiple units in the same neighbourhood. The advantage to the business is predictability; the disadvantage is that they pay whether the host's traffic that month was strong or weak.

The pattern most accessible to small operators is per-cover or per-attendee. It is the easiest to track, the easiest to invoice, and the most familiar to the businesses you will be approaching. The percentage and retainer models are worth pursuing once the relationship has matured and the data exists to justify them.


Restaurants vs. Experiences: Two Different Conversations

These two categories look operationally similar but the commercial structure is different in ways that matter.

Restaurants have lower per-transaction value but much higher volume. A guest might eat at one of your recommended restaurants three times in a four-night stay. The conversion rate of a well-timed restaurant recommendation is very high — guests have to eat, and they are biased toward recommended places. The commission per visit is small, but the visits compound. A restaurant relationship is built on a high-volume, low-cost trickle of revenue.

Experiences have higher per-transaction value but much lower volume. A guest might do one experience during a stay, or none. The conversion rate is lower because experiences are more discretionary and more personal. But when an experience is booked, the commission is meaningful — often three to five times what a restaurant cover commission pays. An experience relationship is built on a lower-volume, higher-value pulse.

This shapes how to approach each. With restaurants, the model needs to be effortless on both sides — minimal admin, no per-transaction friction, monthly reconciliation. With experience operators, the model can carry more administrative overhead because each transaction is worth defending.

Approaching both with the same playbook produces friction. Restaurants do not want to manage a percentage-of-bill arrangement, and experience operators do not want to track per-attendee referrals manually when the bookings are already in their system.


Approaching a Local Business About Referral Income

The conversation that opens the arrangement is shorter and more direct than most hosts expect. Local businesses that benefit from your traffic already understand the model — what they do not have is data about which of their customers came from your recommendation.

What works in practice:

  • Show up with a number. "I send between five and twelve guests a week to your venue across the season" is more useful than "I recommend you to my guests." The business needs to know the scale before they can think about the commercial terms.
  • Propose a specific arrangement. Not "would you be interested in a referral fee" but "I am proposing a fee of five euros per cover, tracked by guests mentioning the apartment name when they book." The specificity converts the conversation from open-ended to negotiable.
  • Make it easy to track on their side. A code, a phrase, a referral card the guest hands over. The business needs a low-friction way to attribute the visit. Asking them to maintain a spreadsheet of mystery referrals is what makes the arrangement fall apart in month two.
  • Agree on a billing cycle. Monthly is standard. Quarterly works for lower-volume relationships. Anything less frequent loses the visibility that keeps the relationship active on both sides.

The businesses most likely to say yes are the ones already paying commissions to other channels — most of the time, the OTAs they are listed on. The ones that resist are usually new operators who have not yet had to think about cost-of-acquisition. With those, the strategy is to start informal, generate visible traffic, and revisit the conversation once they have data of their own.

For the timing layer of how to deliver these recommendations effectively, see How to Send Proactive Local Recommendations to Guests at the Right Moment During Their Stay.


Tracking and Getting Paid

The arrangement only works if attribution is reliable on both sides. Two patterns hold across most working examples.

The guest mentions a phrase or shows a code. "Tell them you are staying at [property name]" or "Show this card for a small house gift." The business records the mention against the bill or booking. The host receives a monthly count and invoices accordingly. This is low-tech and reliable because both parties have a clear signal at the moment of transaction.

The booking comes through a tracked link. For experience operators with online booking, a unique URL or code embedded in the recommendation makes attribution automatic. The booking system records the source; the host's payout is calculated against the bookings tagged with the host's code. This works better for experiences than restaurants because experiences are pre-booked online and restaurants typically are not.

What does not work well is asking the business to attribute referrals from memory at the end of the month. They will under-count, sometimes by half, because the people taking bookings or seating tables are not the same people calculating the monthly invoice. Either the attribution is captured at the transaction moment, or it is lost.

For more on the structural difference between guidebook content and dynamic recommendations — which directly affects which businesses will be worth approaching — see Static Guidebook vs. Dynamic Guest Recommendations: Why the Difference Matters for Your Revenue.


What This Pays Out To in Practice

The numbers depend heavily on property volume, location, and the quality of the recommendation library. A useful frame for a host operating two to five properties at moderate occupancy in a city:

  • Restaurant referrals: a few euros per cover, several covers per week per property in peak season, dropping off-season. A working setup with three to five restaurant partnerships generates a low-three-digit monthly figure during the season for a host of this size.
  • Experience referrals: more variable, but each successful booking pays meaningfully more. A host with two to three active experience partnerships, generating one to three bookings a week across the portfolio in season, can match or exceed the restaurant line.
  • Combined, these revenue lines do not replace property income. They do, however, often cover the cost of the host's cleaning operation or guest communication platform, with margin. The mental model worth holding is "covers the operational stack," not "primary revenue source."

The economics improve sharply at higher portfolio sizes. Ten properties in the same city, with mature partnerships, can produce a referral line that is a meaningful percentage of net operating income. The work to maintain the relationships does not scale linearly with property count.


The Trust Constraint: Why You Cannot Recommend What You Wouldn't Eat

The single thing that breaks this model is recommending businesses you do not personally vouch for. The conversion rate of host recommendations is high because guests trust the implicit endorsement. The moment guests realise they have been sent somewhere because of a commercial arrangement rather than because the host genuinely likes the place, the trust evaporates — and with it, the conversion rate that justified the arrangement in the first place.

This sets a hard ceiling on how many partnerships any individual host can sustain. You cannot have a referral arrangement with every restaurant in a five-block radius. You can have one with the few you actually recommend. The discipline is to keep the list short, vetted, and current — to add a partner only when you would already be sending guests there without one, and to drop a partner the moment the place stops being one you would recommend on its own merits.

The commercial layer adds revenue. It cannot replace the editorial judgement that makes the channel work.


The Operational Picture

The hosts already running this revenue stream did not invent something new. They formalised what they were already doing. The same recommendations, the same guests, the same local businesses — with a commercial layer added that the businesses were already paying for elsewhere.

The work to set it up is a conversation with each business and a tracking mechanism. The work to maintain it is monthly reconciliation, occasional re-vetting of the partner list, and the same recommendation discipline that produced the conversion in the first place. The revenue is not transformative on its own, but it covers operational costs at modest scale and grows meaningfully with portfolio size.

What makes the model sustainable is the trust signal that drives the conversion. Guests have to believe the recommendation is genuine. Hosts who treat their guest channel as an editorial publication first and a referral channel second protect that signal. Hosts who treat it as a referral channel first lose the signal and, with it, the revenue.


More in This Series

How Vacation Rental Hosts Can Earn Referral Income from Local Business Recommendations

Why Your Vacation Rental Guidebook Is an Untapped Revenue Stream How to Send Proactive Local Recommendations to Guests at the Right Moment During Their Stay Static Guidebook vs. Dynamic Guest Recommendations: Why the Difference Matters for Your Revenue