As part of our design update, the screenshots are currently being revised.

TABLE OF CONTENTS


Introduction

A few hotel suppliers provide the daily rate + rate change indicator to DerbySoft.

For this model, each day has a daily rate and a rate change indicator("true" or "false"). If one day's rate change indicator is "true", it means that when calculating a stay through the day(not check-in), the day's rate will use its own rate. If the rate change indicator is "false", it means that the day's rate is the same as prior day. The check-in date rate will always use its own rate. The rate change indicator won't apply for the first day of the stay (check-in day).

Note: This feature applies exclusively to the Daily Rate Model of Go Push Distributors



How does it work?

There is a node named rateChangeIndicators in the request of AvailabilityPeer - Daily Push API. GO Distributors can obtain it as long as hotel suppliers provided it.

{
  "header": {
    "supplierId": "HILTON",
    "distributorId": "GTA",
    "version": "v4",
    "token": "18393849028490234"
  },
  "messageType": "Delta",
  "hotelId": "GATHI",
  "dateRange": {
    "startDate": "2018-01-01",
    "endDate": "2018-01-04"
  },
  "currency": "USD",
  "dailyAris": [
    {
      "roomId": "K1",
      "rateId": "BARB",
      "mealPlans": [
        "BB",
        "BB",
        "BB",
        "BB"
      ],
      "inventories": [
        9,
        0,
        9,
        9
      ],
      "rates": {
        "type": "OccupancyRate",
        "rates": [
          {
            "adultCount": 2,
            "childCount": 1,
            "amountBeforeTax": [
              502.19,
              502.19,
              502.19,
              502.19
            ],
            "amountAfterTax": [
              623.23,
              623.23,
              623.23,
              623.23
            ]
          }
        ]
      },
      "availStatuses": {
        "close": [
          false,
          false,
          false,
          false
        ],
        "minStayArrival": [
          0,
          2,
          0,
          0
        ],
        "maxStayArrival": [
          0,
          2,
          0,
          0
        ],
        "minStayThrough": [
          0,
          2,
          0,
          0
        ],
        "maxStayThrough": [
          0,
          2,
          0,
          0
        ],
        "minAdvanceDay": [
          0,
          2,
          0,
          0
        ],
        "maxAdvanceDay": [
          365,
          365,
          365,
          365
        ],
        "cta": [
          false,
          false,
          false,
          true
        ],
        "ctd": [
          false,
          false,
          false,
          true
        ],
        "fplos": [
          "1111111",
          "1001111",
          "1000001",
          "0000000"
        ]
      },
      "rateChangeIndicators": [
        true,
        false,
        true,
        false
      ]
    }
  ]
}



Example

The rate and rate change indicator is shown below.

DateRateRate Change Indicator
2023-01-01100false
2023-01-02150false
2023-01-03120true
2023-01-04100false
2023-01-05150false

  • For check-in on 2023-01-01 and check-out on 2023-01-02, the rates would be 100
  • For check-in on 2023-01-01 and check-out on 2023-01-03, the rates would be 100, 100; since for day 2023-01-02, the rate change indicator is false, it would use the same rate as 2023-01-01
  • For check-in on 2023-01-01 and check-out on 2023-01-04, the rates would be 100, 100, and 120; since for day 2023-01-03, the rate change indicator is "true", it would use its own rate
  • For check-in on 2023-01-01 and check-out on 2023-01-05, the rates would be 100, 100, 120, 120
  • For check-in on 2023-01-01 and check-out on 2023-01-06, the rates would be 100, 100, 120, 120, 120
  • For check-in on 2023-01-02 and check-out on 2023-01-03, the rates would be 150
  • For check-in on 2023-01-02 and check-out on 2023-01-04, the rates would be 150, 120
  • For check-in on 2023-01-03 and check-out on 2023-01-04, the rates would be 120