1. Revenue Management System
  2. Data model
Reference

The tables behind Revenue Management System

Revenue Management System ships with 12 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.

Tables
12
Features
7, plus shared settings
Change it
Add fields and tables in Proto

How the model is organised

Stay identity

Parties, Units and Reservations identify the guest, physical unit and booking interval.

Revenue decision

Rate plans defines effective nightly terms; demand snapshots records observations; rate recommendations records proposed and reviewed changes.

Stay money

Folio charges and Payments attach separately to Reservations.

Operating work

Service tasks links a unit and reservation to an assignee in People, whose user identity lives in Users.

Reference rates

Exchange rates stores effective currency rates for configured use.

Every table, by feature

Reservations

5 tablesAbout this feature
  • Reservations

    Guest stays with arrival, departure, rate and lifecycle status.

    Linked to Parties, Units
  • Parties

    Guests and corporate accounts that book stays.

  • Units

    Rentable rooms and suites with capacity and housekeeping status.

  • Folio charges

    Itemized charges posted to a reservation folio.

    Linked to Reservations
  • Payments

    Payments received against a reservation, separate from folio charges.

    Linked to Reservations

Units and availability

3 tablesAbout this feature
  • Units

    Rentable rooms and suites with capacity and housekeeping status.

  • Reservations

    Guest stays with arrival, departure, rate and lifecycle status.

    Linked to Parties, Units
  • Service tasks

    Housekeeping, maintenance and guest service work assigned to staff.

    Linked to Units, Reservations, People

Rate plans

4 tablesAbout this feature
  • Rate plans

    Seasonal nightly rate plans by unit type with minimum stay rules.

  • Units

    Rentable rooms and suites with capacity and housekeeping status.

  • Reservations

    Guest stays with arrival, departure, rate and lifecycle status.

    Linked to Parties, Units
  • Rate recommendations

    Proposed nightly rate changes for a stay date, with reason and review status.

    Linked to Reservations

Demand snapshots

4 tablesAbout this feature
  • Demand snapshots

    Daily demand and competitor rate observations for a stay date and unit type.

    Linked to Reservations
  • Reservations

    Guest stays with arrival, departure, rate and lifecycle status.

    Linked to Parties, Units
  • Units

    Rentable rooms and suites with capacity and housekeeping status.

  • Rate recommendations

    Proposed nightly rate changes for a stay date, with reason and review status.

    Linked to Reservations

Rate recommendations

4 tablesAbout this feature
  • Rate recommendations

    Proposed nightly rate changes for a stay date, with reason and review status.

    Linked to Reservations
  • Reservations

    Guest stays with arrival, departure, rate and lifecycle status.

    Linked to Parties, Units
  • Demand snapshots

    Daily demand and competitor rate observations for a stay date and unit type.

    Linked to Reservations
  • Rate plans

    Seasonal nightly rate plans by unit type with minimum stay rules.

Folio and payments

3 tablesAbout this feature
  • Folio charges

    Itemized charges posted to a reservation folio.

    Linked to Reservations
  • Payments

    Payments received against a reservation, separate from folio charges.

    Linked to Reservations
  • Reservations

    Guest stays with arrival, departure, rate and lifecycle status.

    Linked to Parties, Units

Service work

4 tablesAbout this feature
  • Service tasks

    Housekeeping, maintenance and guest service work assigned to staff.

    Linked to Units, Reservations, People
  • People

    Staff members who own operational work in the revenue management system.

    Linked to Users
  • Units

    Rentable rooms and suites with capacity and housekeeping status.

  • Reservations

    Guest stays with arrival, departure, rate and lifecycle status.

    Linked to Parties, Units

Shared and settings

2 tables
  • Exchange rates

    Read-only effective exchange rates for this app.

  • Users

    Users

    Linked to Users

Keys and references

A reservation refers to one guest and one unit. Demand and recommendation records refer to a reservation through operational record. Charges and payments refer through Reservation. Service tasks refer to Unit, Reservation and assigned to. Preserve the source identifiers during migration and resolve those references before comparing totals or making rate decisions.

Migration order

  1. Import Users, People, Parties, Units and exchange rates with stable identifiers.
  2. Import rate plans with the property’s unit type names and effective dates.
  3. Import Reservations with valid guest and unit references.
  4. Import demand snapshots and rate recommendations with their linked reservation references.
  5. Import folio charges, Payments and service tasks after the referenced stay and assignee exist.
  6. Compare a sample stay from request through charge, payment and unit turnover.

Set up Revenue Management System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started