Skip to main content

[Pricing Management] How to Choose a Rate Adjustment Method (Please Read First)

J
Written by Joelly See Toh

Overview

In AirHost, there are multiple methods available for adjusting and updating daily rates (pricing management).

This guide focuses on helping you decide which method to use for managing your rates.


Key Features (Quick Comparison)


※ ⚪︎ = Suitable / △ = Conditional / ✕ = Not suitable

Method

Small scale

(a few rooms)

Large scale (10 rooms or more)

Automation

Flexibility

Operational Difficulty

Features

Price calendar (manual)

⚪︎

⚪︎

⚪︎ (Easy)

Edit directly on a daily basis

Pricing Tier

⚪︎

Rule-based by weekday/season

Price Template

⚪︎

Apply seasonal calendars (peak/off-peak) across multiple properties

CSV Import

⚪︎

⚪︎

Bulk management via Excel, etc.

Pricing API

⚪︎

⚪︎

⚪︎

✕ (difficult)

Fully automated with custom logic

PriceLabs

⚪︎

⚪︎

⚪︎

Fully automated optimization using market data


Summary (Choosing the Right Approach)

The choice of rate management method depends on the number of properties and the scale of your operation.

  • Small scale → Price Calendar / Pricing Tiers / PriceLabs

  • Large scale → Templates / CSV / API / PriceLabs

👉 Start with Price Calendar or Pricing Tiers, then gradually move toward automation.


■ Features of Each Rate Adjustment Method

① Manual Management via Rate Calendar

👉 Rate Management (Calendar Editing)

  • Edit rates directly by day on the calendar

  • The simplest and most intuitive method

Advantages

  • Changes can be made immediately

  • Allows flexible adjustments

Disadvantages

  • Becomes complex as the number of properties and dates increases

Best suited for

  • Small-scale operations (a few rooms)

  • When you want to fine-tune rates for specific dates


② Rule-Based Management Using Pricing Tiers

👉Pricing Plans (Pricing Tiers)

  • Pricing rules are set according to the day of the week, season, and events.

  • Define a fee for each rank and assign it to the date.

Advantages

  • Reduces the need for manual adjustments

  • Enables standardized, rule-based operations

Disadvantages

  • Not well-suited for sudden demand fluctuations

  • Does not automatically optimize prices

Best suited for

  • Cases where pricing patterns are predictable (e.g., weekdays, peak seasons)

  • When you want stable operations based on predefined rules


③ Rate Templates (Bulk Adjustment)

👉 Rate Management (How to Use Rate Templates)

  • Apply rates in bulk across multiple dates and multiple properties

  • Suitable for seasonal pricing (peak/off-peak periods)

Advantages

  • Significantly reduces manual work

  • Allows bulk updates across multiple properties

Disadvantages

  • Not fully automated (manual execution is required)

  • Exceptions require separate handling

Best suited for

  • Operations that are still manual but have grown in scale

  • Bulk adjustments during campaigns or seasonal changes


④ CSV Import / Pricing API (In-house Logic Management)

👉 Rate Management (CSV Import)

  • Bulk apply externally created rates via CSV

  • Automatically update rates via API (Pricing API)

Common Features

  • Rate logic is managed outside of AirHost

  • AirHost is used as the destination system for updates

Advantages

  • Handles large volumes of data well

  • Allows fully flexible custom logic design

Disadvantages

  • CSV: requires manual operation

  • API: requires development work

Best suited for

  • Users managing rates via Excel or internal tools

  • Systems using RMS or custom pricing logic

  • Medium to large-scale operations


⑤ PriceLabs (Dynamic Pricing)

👉Dynamic Pricing (PriceLabs)

  • Automatically optimizes rates based on market data

Advantages

  • Fully automates rate adjustments

  • Strong for maximizing revenue

Disadvantages

  • Requires additional cost for the external service

  • Initial setup (e.g., minimum/maximum rates) is important

Best suited for

  • Users who want to reduce manual rate management

  • Those who want market-based dynamic pricing optimization


Did this answer your question?