Chapter 02 of 10 · Availability, rates, bookings
Inventory and reservations
A booking hub lives or dies on the calendar. Every accommodation type behaves differently: a cottage lets by the week with a Saturday changeover, a B&B room by the night, a glamping pod by the short break with a two night floor. The data model has to hold all of it without special cases, and it has to stop two guests booking the same pod twice. This is also the layer that replaces the booking engine, channel manager and availability calendar each member runs today, so the booking finishes here and nowhere else.
Member, property, unit, rate plan, booking
This chain is the core of the platform. Everything else, from payouts to marketing performance, hangs from it, and every staff screen and member screen is a view onto it.
- A member can own several properties
- A property can hold several units of mixed types
- A rate plan carries season, length of stay, occupancy and inclusions
- A booking always points at a unit and a rate plan
Accommodation models that fit real farms
Self-catering, farmhouse B&B, glamping, camping and experience-led stays do not share the same rules, so the platform treats rules as data rather than code.
- Nightly, weekly and short-break pricing patterns
- Minimum stays, arrival days, changeover days
- Room-level and bed-level inventory for B&B
- Extras and add-ons: hot tub, logs, breakfast, stabling
- Group and multi-unit bookings under one reference
Live availability and prices
Availability is calculated from bookings, blocks, closures and channel imports, then quoted with the member's own rate rules applied. A member changes a price and the public page quotes it immediately.
- Seasonal and event-driven price bands
- Length-of-stay and early-booking discounts
- Deposits, staged payments and balance due dates
- Cancellation policies resolved to a specific refund at the time of booking
Working with the systems members already use
Many members already run a property management system or list on other channels. The platform should sit above those tools rather than asking a farm to abandon a system that works.
- Two-way inventory sync with common property management systems
- Channel manager connections where members sell elsewhere
- Duplicate-booking prevention at the point of confirmation
- Sync health visible to members and to Farm Stay support
- An exception queue for failed syncs rather than silent gaps
The design decision
One availability ledger owns each unit. Channel managers and external calendars subscribe to it. When two sources disagree, the ledger wins and the exception is surfaced, never averaged or overwritten.