Proposal — June 2026

Reservation Request
Management System

Two solutions designed for Le Barth Villas: one to launch fast, one to scale without limits.

Basic Solution
Advanced Solution
EN / FR
Stripe Payments
256 Villas

Inventory is under control.
Requests are not.

Le Barth Villas manages 256 luxury properties with a sophisticated system for availability, seasons and rates. Yet when a guest wants to book, the process still depends on manual validation, back-and-forth communication, and no mechanism to protect inventory in the meantime.

The result: requests without real purchase intent, villas that cannot be confirmed or rejected quickly, and high-profile guests expecting an experience that does not yet exist.

Exposed inventory
Without a formal hold mechanism, the same villa can be in active conversations with multiple guests at the same time.
📋
Unqualified requests
The team spends time on inquiries that never convert into reservations because no verified purchase intent is required upfront.
Slow response cycles
Every confirmation requires manual coordination between the team, the owner and the guest. The cycle is slow and lacks visibility.

Two paths.
One objective.

Both solutions solve the core problem: protect inventory, qualify the guest and automate the approval flow. The difference is how far you want to go.

Basic Solution

From request chaos to an ordered process

Today Le Barth Villas receives unstructured inquiries, with no verified intent and no inventory protection. This solution changes that from day one: the guest requests, pre-authorises their card as proof of real intent, and the team approves or rejects from a clear panel. All with automatic notifications to the owner, the team and the guest — in English and French.

What it includes

  • Real-time availability calendar
  • Reservation request form
  • Stripe pre-authorisation (Authorization Hold)
  • Approval flow: Owner → Le Barth Villas → Guest
  • Automated email notifications (4 types)
  • Status update in CMS / Backend
  • Multilingual interface EN / FR
Advanced Solution

A rejection stops being a loss

Everything the Basic Solution resolves, plus a layer of intelligence that turns rejections into opportunities: when a villa is unavailable, the system automatically suggests alternatives to the guest by proximity, room count, rate and date availability. Also includes an advanced season calendar, UX improvements, formal documentation and team training.

Everything in Basic, plus:

  • Alternative villas engine (proximity, rooms, rate, availability)
  • Automatic suggestions to guest on rejection
  • Calendar with advanced season and blackout granularity
  • UX improvements to the request form
  • Formal technical and operational documentation
  • Structured team training
  • Post-launch stabilisation support

Technologies included

Stripe LBVR API Matching Engine EN / FR

What does
each solution include?

A quick view of all features and which solution they are available in.

Feature Basic Advanced
Booking Flow
Real-time availability calendar
Reservation request form
Stripe pre-authorisation (Authorization Hold)
Automatic fund capture and release
Approval Flow
Villa owner notification
Admin panel (approve / reject)
Guest notification (approved / rejected)
Status update in CMS / Backend
Experience & Languages
Multilingual interface EN / FR
Calendar with advanced season granularity
UX improvements to the request form
Alternative Villas Engine
Automatic suggestions to guest on rejection
Matching by proximity, rooms, rate and availability
Delivery & Support
Formal technical and operational documentation
Structured team training
Post-launch stabilisation support

How every
notification flows.

Click each step to see what fires, to whom and when. The flow runs across 4 sequential moments with 4 distinct actors.

1
Moment 1
Guest submits request and pre-authorises card
Selects villa, dates, completes their information and authorises the temporary hold. Request enters with Pending status.
→ Villa Owner → CMS / Backend
2
Moment 2
Owner validates — Le Barth Villas decides
The owner confirms availability and gives the go-ahead. Le Barth Villas reviews and decides whether to approve or reject.
→ Le Barth Villas
3
Moment 3 — Approval
Reservation approved — payment captured
Stripe executes the capture. Guest and owner are notified. CMS blocks the villa on the corresponding dates.
→ Guest → Villa Owner → CMS / Backend
4
Moment 3 — Rejection
Reservation rejected — funds released and alternatives suggested
Stripe releases the pre-authorisation. CMS restores availability. In the Advanced Solution, the engine automatically suggests alternative villas to the guest.
→ Guest → Villa Owner → CMS / Backend

Click a step
to see the notifications
that fire

Moment 1 — Request Received
Guest submits request and pre-authorises card
◆ Villa Owner
New request for your property
Villa requested, dates and length of stay. Guest contact details are managed exclusively by Le Barth Villas.
🔒 Contact details not included — managed by Le Barth Villas
◆ CMS / LBVR Backend
Status: Request Pending
The villa is flagged with an active request. Availability is not yet blocked.
Moment 2 — Internal Validation
Owner validates — Le Barth Villas decides
◆ Le Barth Villas
Request ready for review
The owner has confirmed availability. Full request details are in the admin panel for approval or rejection.
Moment 3 — Reservation Approved
Payment captured. Reservation confirmed.
◆ Guest
✓ Your reservation is confirmed
Official confirmation with villa details, dates, amount charged and arrival instructions.
◆ Villa Owner
Reservation confirmed at your property
Stay dates, number of guests and reservation amount. Guest communication is coordinated through Le Barth Villas.
🔒 Contact details not included — managed by Le Barth Villas
◆ CMS / LBVR Backend
Status: Villa Blocked
The dates are blocked on the calendar. Availability updates automatically.
Moment 3 — Reservation Rejected
Funds released. Alternatives suggested.
◆ Guest
− Request not confirmed
Rejection notice with reason (optional). The pre-authorisation has been released with no charge.
◆ Villa Owner
Request cancelled for your property
Confirmation that the request was rejected and the villa is available again.
◆ CMS / LBVR Backend
Status: Availability Restored
The dates are released. The villa reappears as available on the booking calendar.
◆ Alternative Villas Engine
Advanced Solution
Suggestions sent to the guest
Instead of a flat rejection, the system automatically proposes other villas matching similar criteria.
Proximity Rooms Rate Availability
Villa Azur — same area, 5 rooms95% match
Villa Sereine — equivalent rate88% match
Villa Coraline — same dates82% match
Villa Owner
Le Barth Villas
Guest
CMS / Backend
Alternatives Engine

Choose the solution
you need today.

Fixed price per complete solution. No variable costs, no surprises.

Basic Solution
$3,000
USD — one-time payment
From request chaos to an ordered process, with inventory protection from day one.
Advanced Solution
$5,500
USD — one-time payment
Includes everything in Basic plus the alternatives engine, team training and stabilisation support. A rejection stops being a loss.