What comes in, what goes back, and who changed what.
Livion works alongside your PMS. Where a connection exists, stays, rooms and closures come in, and room charges and housekeeping status go back. Every change in Livion is written to an audit log with the old and the new value. Italian supplier e-invoices arrive as proposals a person confirms.
30 minutes, on your own rooms and departments.
- One PMS per property
- Old and new values in the log
- E-invoices: Italy only
Three things to try
Each page has a small demonstration you can use.
Also in this module
Part of the module today, without a page of its own yet.
- Webhooks in and out, used in Automations: an automation can start from an incoming webhook and can call another system. They work with a token in a header, an idempotency key, signed calls and HTTPS addresses only.
- One-way calendar sync for Maintenance: planned work appears in an external calendar. Changes made there do not come back.
- Sales import from a file in Warehouse: a sales file from your point of sale becomes consumption per department, and Livion remembers the mappings.
Works with
Questions
Which PMS systems does Livion connect to?
That varies. Ask us about your PMS and we tell you plainly whether a connection exists and what it covers. A property connects one PMS at a time.
Does Livion work without a PMS connection?
Yes. Every module also works without a PMS. What only the PMS knows, such as stays and guests in house, is then not shown.
Is Livion a PMS?
No. Livion works alongside your PMS and runs the operations behind the stay.
Does Livion have a public API?
No. Other systems are connected through the PMS connection, through webhooks in Automations and through file imports.
Ask us about your PMS.
Tell us which PMS you use. In the demo we show you what a connection covers for your hotel, and what Livion does without one.