Nothing is reconciled, because nothing ever disagreed.

The triggers, named

• Booking promotion. An agent booking in Connect promotes itself into the Flow P&L with commission already subtracted.
• Receipt sync. A receipt recorded in Flow appears on the agent's booking in Connect the same minute.
• Guest dedupe. Every reservation, from any door, builds or updates one guest profile in Stay.
• VIP tiers. Stay's guest history is computed from the reservations Flow already holds.

What Villabase does not do

Stated here rather than discovered in month two. A limitation you know about is a decision; one you find later is a betrayal.

• No channel manager or OTA sync. Airbnb and Booking calendars are handled outside Villabase today. In active build — it is not in the product yet, and this page will say so until it is.
• No card processing. Villabase records payments; it does not charge your guests' cards.
• No Greek tax or myDATA integration, or any e-invoicing regime.
• Connect is single-tenant. One villa company per deployment; the multi-vendor network is a roadmap direction, not a shipped feature.
• No WhatsApp Business API. Email and Telegram are the wired channels.
• Euro only. Villabase prices, reconciles and reports in euro. There is no multi-currency handling, and no interface translation — the product is in English. We are listing this because we promise to tell you what is missing, and a gap we forgot to mention would make that promise worthless.
• No migration importer for an incumbent PMS. Moving off Guesty or Hostaway means an export, a column mapping and an import, done with us. What switching actually involves →

What our films show that the product does not

Our product films are allowed to show where Villabase is going, not only what has shipped. That licence is worth nothing unless we say, on this page, exactly where we used it. Nothing in the list above is softened by what follows.

• The agent network. The Connect film closes on agents moving between villa companies through one identity. None of that scene is built — not the shared login, not the cross-company identity, not the network. Connect is single-tenant today, exactly as the list above says.
• The guest sign-in. The Stay film shows a guest typing a booking reference and receiving a code on their phone. That mechanism does not exist. What is built and live today is a private link we send the guest, which is how they reach their stay. The film shows a direction we are considering for that entry — not a replacement we have committed to.
• The concierge request, end to end. The film on our home page shows a guest asking for a chef, your team confirming it, and her having the email before anyone picks up a pen. Both halves are live and in daily use — the staff confirmation is a real database write, and the guest email is a real transactional send. What we have not done is test the whole loop start to finish on a clean dataset, so we will not call it proven. It is the one beat in that film a prospect could probe and find unproven, and we would rather name it here than have you find it.
• Four interface details shown ahead of shipping, each on an otherwise real screen: a live "new booking" notification, emailing an owner statement from its own screen, merging duplicate costs rather than deleting one, and a "deposit due" payment state. Real screens; one affordance apiece that we have not built.
• Every film carries its own line-by-line ledger. Each scene is marked built or intended in that film's blueprint, against the code behind it. If you would rather check that than take our word, ask and we will send you the ledger itself.

The rest of the hard questions

Each of these gets its own page rather than a reassuring paragraph here, because a buyer checking them deserves something they can read end to end.

And the one most vendors leave out: who we cannot serve — stated as policy rather than discovered in a sales call.