Case study

Country house rental listings platform

Bookings with calendar availability synced from other platforms, overlap handling, invoices and host payouts.

Home page: search by region and service, with a category bar below.

ProblemHosts list on several platforms at once, so dates are booked elsewhere too. A double booking damages the platform's reputation, not the host's.

SolutionCalendars are synced with other rental systems, and overlapping bookings are flagged and left for a person to resolve. Host payouts are accounted for separately, with bank details and history.

Context

A country house rental platform brings together three different interests. The guest wants to book without phoning. The host needs the calendar to reflect reality and the money to arrive on time. The platform needs both to use the system rather than make arrangements by phone.

The hardest part is the calendar. Most hosts list on several platforms at once, so dates get booked elsewhere as well.

What needed solving

The main risk is a double booking. If a guest pays for a date that is already taken on another platform, it is the platform's reputation that suffers most.

Payouts also needed sorting out. The platform takes the guest's payment, but the money belongs to the host, so it had to be clear when and how much is paid out after commission.

Extra services change the final price too: a sauna, a hot tub, extra beds, late check-out. Each host has their own list.

How the platform is organised

Calendars are synced automatically with other rental systems, so booked dates are visible regardless of where they were booked. The data does not update instantly, so there is a dedicated conflict-handling step: if two bookings overlap, the system flags them and the overlap does not go unnoticed.

Each booking has a status history from enquiry to payment and completion. Every change is recorded with a timestamp, so in a dispute the whole sequence is visible.

Extra services are added to a booking as separate lines with their own prices. Both guest and host can see what makes up the final amount.

Host bank details and payout history are stored separately from the account. They make it quick to answer how much a particular property earned in a season.

Alongside bookings there is an articles section with categories, because most visitors to platforms like this come from search engines.

Technical decisions

Conflicts are flagged, not overwritten. When another platform passes on data late, the system does not decide for a person: it flags the overlap and leaves it for a person to resolve.

Full booking status history. The current status alone shows where a booking is today. In a dispute over money, you need to know what happened earlier and when.

Payout data separate from the account. Bank details change less often than contact details, and their history is needed for accounting.