VenusLab

VenusLab OS

The PMS that holds the rest together

Rooms, bookings, accounts and compliance in one place — and the repetitive part done by itself. It is where the hotel's data is born, and where the rest of the suite starts.

Request a demo How it connects to the other modules →
The OS tableau: rooms down the side, days across the top, bookings as bars coloured by status, with icons for payment, document and source
The tableau — every room, every date. Bars are dragged, and the inventory refuses the move that would sell the same room twice. Interface shown in Italian.

Automation

What you no longer have to do

The difference between a PMS and an operating system is not the number of screens: it is how much of the work happens without anyone doing it. These nine run by themselves in OS, from data the system already holds.

  • Guest messages

    Confirmation, amendment, cancellation, payment receipt, option expiry reminder: each rule ties an event to a template, and goes out on its own. You write the text once.

  • The housekeeping plan

    Built from arrivals, departures and who is staying on: quick clean or deep clean, linen changed or not. The housekeeper opens a list that is already made, and corrects it if she needs to.

  • The meal sheet

    Who is entitled to breakfast, lunch or dinner comes from the board type on the booking, not from a sheet kept by hand in the dining room. Covers count themselves, dietary needs included — and yesterday's attendance corrects tomorrow's forecast.

  • The tourist tax

    The rules are written once — season, night band, per person or per room, age exemptions — and from there the calculation lands in the booking totals without anyone redoing it.

  • Books that close

    Charges follow the stay night by night. At month end the accounts are checked, not reconstructed backwards from a pile of receipts.

  • Tax documents

    Electronic invoices and commercial receipts are built from the closed folio and filed with the revenue agency. The numbering, the series and the archiving are not yours to keep.

  • Availability on the channels

    What sells at the property goes down to the portals, and bookings from the portals land on the tableau without passing through an inbox.

  • Rooms that assign themselves

    A booking that came in without a room is often not overbooking: the room exists, it is just in the wrong place. Where moving stays that have not arrived yet is enough, OS redoes the layout by itself — and nobody moves a guest who already has the key.

  • Faults that reach the right people

    Housekeeping reports a fault from their own page, with no account and nothing to install. From there it shows on reception's tableau, with the priority next to the room number, and on the technician's list — who has a page of their own and closes it there.

The Automations tab in OS: seven active rules tying an event — confirmation, amendment, cancellation, tax document, payment, option, expiry — to the message template to send
Automations: an event, a template, on or off. Seven on out of the box, and you write the text. Interface shown in Italian.

One system, not seven programs talking past each other

Most hotels keep the PMS in one place, the channel manager in another, the accounts in a spreadsheet and the tourist tax in a portal somebody fills in by hand the month after. Every hand-off is a place where the numbers drift apart. OS removes the hand-offs: the data is written once and counts for everything.

Tableau

The room plan at a glance, with drag-and-drop booking moves and inventory checks that rule overbooking out.

Bookings

Search, amend, check in and check out. Every action stays on the activity log.

Rooms and rates

Room types, layouts, rate plans and restrictions: the foundation every other module works on.

Distribution

Connections to your sales channels and a booking engine for the hotel's own site, on the same availability as the tableau.

Accounting

Payments, receipts and documents, with the books closing themselves instead of being rebuilt at month end.

Compliance

Tourist tax and VAT worked out from data already in the system, not retyped into a spreadsheet on the side.

Housekeeping

The day's room plan for the floor team, lined up with arrivals, departures and stayovers.

Food & beverage

Breakfast, lunch and dinner: covers, board types and dietary needs for each service, taken from the stays instead of a list kept by hand.

Reporting

Occupancy, revenue and production at a glance, on the same numbers that feed every other module.

The day's housekeeping in OS: for each room the type of clean, the linen to change, the attendant assigned and the linked booking
The day's housekeeping plan, generated from arrivals and departures.
The reporting overview in OS: occupancy, ADR, RevPAR, room revenue, total revenue and takings, with the daily trend and production by source
Reporting, on the same numbers that feed every other module.

Away from the front desk

Each department gets a link, not an account

The dining room, the floors and maintenance never enter the PMS: they open an address and see the day's work, and nothing else — no guest names, no prices. What they tick there comes back into OS: a room marked clean changes state on the tableau, a fault appears at reception, the covers served this morning correct tomorrow's forecast. And when somebody leaves you revoke their link, not everybody's password.

The three pages are shown in Italian.

The dining room sheet on a phone: 34 covers for breakfast, 4 of them children across 11 rooms, buttons to switch to lunch and dinner, the day's dietary needs and a card per room with covers and «served», «packed lunch», «no show» buttons
The dining room: covers, board types and dietary needs for the service. You tick who ate, and the forecast learns from it.
The housekeeping page on a phone: the attendant's name, «3/9 rooms cleaned», and for each room the floor, the type of clean, the linen to change and a «mark as cleaned» button
The floors: the rooms on the round, with clean type and linen. Mark it cleaned, and reception's tableau knows.
The maintenance technician's page on a phone: the list of open jobs, each with room number, priority, description, who reported it and a «mark as resolved» button
Maintenance: the open faults, with priority and who reported them. You close them here.

Compliance

Italian obligations, worked out from data you already have

Tourist tax and VAT are not a separate module to fill in: they are worked out from guest nights and documents already recorded. What in many properties is half a day at month end is a screen to check here.

No overbooking

Inventory is a constraint, not a hope

Availability is checked against the inventory rules on every write, whichever channel the booking arrives from. Selling the same room twice is not a mistake to correct afterwards: it is an operation the system refuses.

More than a PMS

The other modules come in here

RatePilot, CostCore and Ambra sell on their own too. But on top of OS they are not three more programs to keep open: their features are used inside the PMS, on the same account — and they cost far less than they do separately.

RatePilot

Reads occupancy and pickup, works the prices out every night and writes them back onto the tableau, ready to sell.

Revenue management →

CostCore

Takes the revenue from OS and puts it beside the costs, department by department, so you know what is left.

Cost control →

Ambra

Answers enquiries and builds quotes on the real availability and the real prices in OS.

The AI receptionist →

Want to see it on your own numbers?

We'll show you the PMS with your property in front of you, not a generic demo.

Request a demo