Airbnb, Vrbo and PMS: Who Controls Operations After Booking?

A confirmed reservation does not yet constitute a functioning operation. Guest and stay information must subsequently be complete, cleaning and partner services coordinated, service requests processed, deviations clarified and completed work documented.

As long as one individual manages a small number of properties, many of these steps can be handled through messages, calendars and personal oversight. The situation changes when additional properties, rotating teams or external partners become involved. It is then no longer sufficient for information merely to exist somewhere. It must be assigned to the correct stay, reach the responsible role and result in a traceable action.

The decisive question is therefore not merely: Where does the booking originate? It is: Which system ensures that operations function reliably afterwards?

Three Types of System, Three Different Functions

Airbnb, Vrbo, PMS solutions and Oprivia should not be treated indiscriminately as direct alternatives. They operate at different points within the accommodation process and can be used in combination.

Airbnb and Vrbo facilitate bookings. Both belong to the category of online accommodation-booking platforms. They provide reach, present listings and enable reservations within their respective ecosystems. Airbnb and Vrbo are therefore comparable, but not identical: their fee models, management functions, target groups and processes differ.

Their primary purpose is to facilitate and process bookings. They are not designed to manage every internal workflow of an operator across multiple properties, teams and external service providers according to the operator’s own governance logic.

A PMS consolidates accommodation and booking management. A property management system typically brings together reservations, availability, rates, units and guest data. Modern solutions may additionally provide channel management, automated communication, payments, housekeeping, reporting and other operational functions.

The distinction is therefore not between “operational” and “non-operational” systems. What matters is the depth of execution: Are responsibilities and access rights clearly separated? Are deadlines, deviations and evidence managed on a case-specific basis? Are defined escalation paths available? Can it subsequently be established who processed, approved or completed a particular action and when?

Oprivia controls operational execution after booking. Oprivia is conceived as a role-based operational and governance layer between the confirmed booking and documented completion. The platform connects guest registration, mandatory information, requests, cleaning, partner assignments, processing statuses, evidence, approvals and escalations.

Guests see their stay and the processes intended for them. Operators receive assigned tasks. Hosts and accommodation operators retain oversight of their properties. Governance roles handle defined exceptions and escalations. Critical processing steps remain assigned to the relevant case.

In summary: Airbnb and Vrbo deliver reservations. A PMS consolidates accommodation and booking management. Oprivia is intended to ensure that the resulting operational work is assigned, performed, verified and documented.

The Operational Gap Arises at the Handover Points

The greatest risks rarely result from a single system failure. They arise at the many small transitions between people, information and operational steps.

Before arrival, guest or stay information may still be missing. Questions are handled through individual messages while the team remains uncertain whether information is outstanding, already being reviewed or requires manual clarification.

Between departure and arrival, a unit must be prepared on time. A calendar entry does not establish whether the responsible person accepted the assignment, completed the checklist, reported deviations and released the accommodation as guest-ready.

During the stay, a defective lock, missing consumables or a Wi-Fi outage requires more than a response. The case needs a priority, a responsible person, a processing status and a clearly recognisable conclusion.

After execution, a message stating “completed” is frequently insufficient in a professional operation. Checklists, photographs, notes, timestamps and approvals provide a more reliable basis for quality assurance, corrective work and potential disputes.

Oprivia connects this information with the relevant stay, property and assignment. This transforms a distributed collection of messages, files and personal arrangements into a controllable operational case.

From Manual Coordination to Controlled Automation

Oprivia’s long-term objective is not merely to provide another interface for existing manual work. Recurring digital processes should be automated wherever this is useful and appropriate.

Depending on the module, operating model and configuration, data requests, completeness checks, assignments, deadlines, reminders, evidence requirements, processing statuses and escalation triggers can be managed through predefined rules. Additional identity, plausibility and risk checks may be integrated where they are required for the specific operating case, technically available, contractually agreed and legally permissible.

One principle remains clear: automation structures routine processes and identifies cases requiring review. It does not replace accountable decisions. Unclear information, sensitive approvals, relevant findings and exceptional situations are referred to the designated person.

Depending on the operating model, a substantial proportion of digital post-booking operations can consequently be automated. Physical services and material approvals, exceptions and decisions remain with the responsible people.

The value therefore lies not in uncontrolled autonomy, but in a targeted division of work: the system handles repeatable processes, while people deal with the cases that genuinely require attention and decision-making authority.

Comparing Prices: Distribution, Software or Operations?

Percentage-based fees can only be compared meaningfully when it is clear which service they pay for. A booking platform, PMS, full-service property manager and Oprivia provide different services.

As of August 1, 2026, the following publicly stated models apply, among others:

• Airbnb: Under the single-fee structure, most hosts pay 15.5%. Under other arrangements, hosts typically pay 3%, while guests pay between 14.1% and 16.5%.
• Vrbo: Under its Pay-Per-Booking model, Vrbo states a 5% commission fee and a 3% payment-processing fee. Different fees may apply to listings managed through PMS software, particularly in Europe. Guests may additionally pay a variable service fee.
• PMS software: PMS providers typically use pricing tiers, property-based fees, modules or individual quotations.
• Full-service property management: Revenue-based commissions are common because the provider supplies not only software but also marketing, rate management, guest communication and operational services. Publicly stated offers may begin at approximately 15% and can be higher depending on the market and scope.
• Oprivia: The published models combine a base fee with a revenue-based component. The self-managed setup costs CHF 99–149 per property per month plus 2–3% of monthly booking revenue. Supported operations cost CHF 299–499 per property per month plus 5–8%. The portfolio setup costs CHF 1,000–1,500 per portfolio per month plus 8–10%.

These figures are not directly interchangeable. Oprivia’s revenue-based component does not pay for market reach or booking distribution. It reflects the agreed depth of platform operation, operational support, governance and cross-property control.

Where Airbnb, Vrbo or other booking channels continue to be used, their fees remain payable in addition. Oprivia therefore does not become economically reasonable solely because of a lower percentage. Its economic value depends on whether the platform measurably reduces manual coordination, errors, corrective work, point solutions or part of the operational services otherwise purchased externally.

The correct pricing question is therefore not: Who charges the lowest percentage? It is: Which service does the fee pay for—demand generation, software, operational execution or governance?

When an Additional Control Layer Becomes Appropriate

Not every host managing a single, straightforward property immediately requires an additional platform. Oprivia becomes relevant where personal oversight and informal arrangements no longer scale reliably.

In particular, assess whether several of the following points apply to your operation:

• You coordinate multiple properties, locations, teams or external partners.
• Tasks and changes are distributed across different communication channels.
• You regularly need to ask whether a service has actually been completed.
• Evidence subsequently proves difficult to assign to the correct stay.
• Requests remain unresolved because responsibility or escalation is unclear.
• Standards are applied differently depending on the person or property involved.
• You want to automate recurring processes without relinquishing control over critical decisions.

The more of these points apply, the less likely it is that the problem is merely one of communication. What is missing is a shared and binding operational logic.

The appropriate system architecture is rarely a simple either-or decision. Booking platforms can continue to generate demand. A PMS can continue to manage accommodation and reservation data. Oprivia complements these systems by providing the operational control and governance layer after booking.

For smaller operating models, Oprivia may consolidate several operational point solutions and reduce the need for an extensive PMS. Within larger structures, the platform is more likely to be deployed as an additional layer. The decisive factor is that information progresses from the reservation to documented completion without unnecessary duplication of work.

Oprivia focuses precisely on this part of the process: making post-booking operational work automatable, assignable, verifiable and scalable.