Skip to content

Collect two years of Guestline exports from the hotel #83

Open

Description

@selvarajuv

Problem

The only hotel data we import today is one nightly export with final rooms sold and revenue. It can tell when a night's price was too high (rooms left empty), but not when it was too low: at 93–99% occupancy almost every night looks sold out, whether it filled weeks early or at the last minute. To tell them apart we need booking-level history from the hotel's PMS (Guestline Rezlynx).

Goal

The team has two years of the five Guestline reports below, cleaned of guest details, with the open questions about them answered, and a decision on which ones the manager uploads every day.

Scope

Collect these reports from Menu → Reports in Rezlynx, as CSV:

Report Date range Filter by
Daily New Reservations 2 years back to today booking date
Cancellations same 2 years cancellation date
Daily Rate Analysis 2 years back to 3 months ahead stay date
Rate Override same 2 years applied date
Actual & Forecast 2 years back to 3 months ahead stay date; Blocks, Wait List and ROOS on; one row per day
  • Export month by month if a report won't run over two years.
  • Delete guest columns before sharing (Guest Name, Surname, Profile Ref, Created By, Operator); keep BookRef / Reference.
  • Share through a private drive, never the repo. Record the filter settings used, nett or gross, and anything that failed.
  • Decide which reports the manager uploads daily and which are a one-off history backfill.
  • Answer these questions about the data and write the answers in the shared folder:
    • Does each report export as CSV and cover two years?
    • Does Daily New Reservations include bookings that were later cancelled?
    • Is Date in Cancellations the cancellation date?
    • What does /1 in BookRef mean (a room within a multi-room booking?)
    • Does Daily Rate Analysis show room type, and are its prices nett or gross?
    • Do amended bookings keep their original dates?
    • What does DFS mean in Actual & Forecast?
  • Put small anonymised sample files where tests can use them (outside the repo or fully synthetic).

Considerations

  • If short on time, start with one past month of Daily New Reservations, Cancellations and Actual & Forecast; that's enough to check the rebuild of how full each night was.
  • The earliest months will be partial: some of their bookings were made before the range starts.
  • Nett vs gross must be consistent across reports (gross = nett + 13.5% VAT).

Acceptance criteria

  • All five reports collected for two years (or what Rezlynx allows), with no guest names in them.
  • The questions above answered in writing.
  • The daily vs one-off split decided.
  • Sample files available to the team.

Metadata

Metadata

Assignees

Labels

featureIntroduces a new and complete featurehotel dataGuestline PMS exports, parsers, upload endpoint and checks

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions