LivionBack office
Hotel back-office software

The back of house, working as one system.

Warehouse, maintenance, room assets, meetings and the restaurant share one platform, one login and one operational history — beside your PMS, not instead of it. When a room item ages out, a ticket opens, stock is checked and a reorder is drafted. Nobody forwarded anything.

Five modules, one operational layer Roles and permissions per department Works beside your PMS
Sound familiar?

Every department has a tool. None of them talk.

“Stock in a spreadsheet, tickets on WhatsApp, events in a shared inbox.”
Livion keeps those workflows as connected operational records — with the hand-offs between departments built in.
“Our PMS was never built for the store room, the boiler or the banquet setup.”
It shouldn't be. The PMS keeps reservations and check-in; Livion covers the operational work beside it.
“We can't onboard five systems at once.”
You don't. Start with the highest-friction module and add the others later — same login, roles and history.
Inside the module

Five modules. One operational layer.

Each module stands on its own. Together they share departments, permissions, stock and history — which is where the compounding starts.

01 — Warehouse

One stock truth for the entire hotel.

Purchasing, deliveries, central and department stock, consumption, returns and HACCP-style registers in one traceable flow. Every movement stays explainable by item, department, date and cause.

  • Multi-department inventory with live balances
  • Supplier ordering, deliveries and price history
  • Consumption analytics with CSV export
02 — Maintenance

Every issue: reported, measured, resolved.

Tickets with photos and AI-assisted diagnostics, active-time measurement that pauses during supplier waits, recurring interventions and a searchable record of every contractor visit.

  • AI diagnostic and safety suggestions per ticket
  • Recurring planning: week, month, year, timeline
  • Intervention records with photos and export
03 — MICE

Meeting rooms, sold like inventory.

Capacity-aware availability, per-hour and per-person pricing with VAT-aware totals, operations-ready reservations and revenue and utilization reporting per room.

  • Only rooms that fit the group get offered
  • Net, VAT groups and gross on every quote
  • Utilization and revenue per room by default
04 — Restaurant

From reservation to receipt.

Branded online booking, a live floor, POS and kitchen display, Italian fiscal compliance and a guest CRM with consent-aware marketing — in early access with launch partners.

  • One availability engine for staff and online booking
  • POS, kitchen display and till reconciliation
  • Guest CRM, campaigns and automations in 5 languages
Early access — in development with launch partners
Part of one system

It doesn't replace your PMS. It completes it.

Reservations, distribution and check-in stay where they are. Livion runs the operational network around them.

Your PMS stays

Livion is not a PMS and doesn't want to be. It coordinates the back-of-house work that happens beside the guest-facing records.

Room Assets included

Room items live on room cards with age reviews and replacement flags — feeding Maintenance tickets and Warehouse reorders automatically.

Permissions decide

Departments see their own catalogs, queues and inventories. Roles decide who sees and does what, across every module.

What you get

One platform. Real modules.

Multi-department inventory with live balances Supplier ordering, deliveries and consumption analytics Maintenance tickets with AI diagnostics Recurring maintenance planning and records Auto-tickets from Room Assets, status synced Room items linked to Warehouse SKUs Capacity-aware meeting-room availability VAT-aware event pricing and reporting Restaurant reservations, POS and kitchen display Italian fiscal documents and SDI routing Roles and permissions per department Start with one module, add more later

See the whole back of house in one demo.

Bring the workflows of two or three departments — we'll walk them through the modules and show where the hand-offs disappear.

Keep exploring

The other modules it connects to.