How it works
Nothing is reconciled, because nothing ever disagreed.
Competitors sell you a piece and an integrations page. Villabase is three applications reading and writing one database. This page is the mechanism, the limits, and the data handling — in that order.
One database. Three doors.
Flow, Connect and Stay are not integrated tools. They are three applications on the same schema-per-concern database, wired with live triggers rather than sync jobs. A connector architecture cannot copy this claim truthfully, because a connector's whole job is to reconcile two records that already 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 →
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.
Security and your data →
Where it runs, how access is enforced, how you export everything yourself, and exactly what is not certified — no badges we have not earned.
Integrations →
What connects today, what is in active build, and what is deliberately not connected. A short list rather than a marketplace of logos.
And the one most vendors leave out: who we cannot serve — stated as policy rather than discovered in a sales call.