Skip to main content

Manage prices for days services

The Bookla platform offers a straightforward system for defining price rules for days services, which are typically used for longer-term bookings such as hotel stays or vacation rentals. This documentation outlines the key concepts and best practices for implementing effective pricing strategies for services that are booked by the day.

Core Concepts​

Per-Day Pricing​

In days services, the base price is set per day. The total price for a booking is calculated by multiplying the per-day price by the number of days booked.

Price Rules​

Price rules for days services include:

  • A price per day
  • Priority level
  • Optional limitations (days, resources)
  • Active period (start and end dates)

Rule Priority and Selection​

When a booking is made, the system selects the price from the rule with the highest priority that matches the booking conditions for each day of the stay. If multiple rules with the same priority match, the most recently created rule is selected.

Currency​

Before creating any price rules, you must select the currency for your company. This setting applies to all price rules.

Implementing Price Rules​

Basic Structure​

price
{
  "id": "077890d3-5acc-48a5-bc62-efd529fb68d7",
  "createdAt": "2024-01-01T00:00:00Z",
  "limitation": {},
  "price": {
    "comparedPrice": 200,
    "price": 100
  },
  "priority": 1,
  "serviceID": "a118dfd3-95b0-4635-895c-4e06d22f5dbc",
  "type": "days"
}

Pricing API Documentation

Pricing Calculation​

The total price is calculated by summing the applicable daily rate for each day of the booking.

Example:

  1. Weekday rate: $100 per day
  2. Weekend rate: $150 per day
  3. Client books a 4-night stay from Thursday to Monday

Resulting price: $500 ($100 + $100 + $150 + $150)

Limitations​

You can narrow the applicability of a price rule using the following optional limitations:

  1. Days: Specify days of the week when the rule applies using a 7-bit bitmask. Each bit represents a day of the week, starting from Monday. For example:
  • 1111111 (127 in decimal) represents all days
  • 1111100 (124 in decimal) represents Monday through Friday
  • 0000011 (3 in decimal) represents Saturday and Sunday
  1. Resources: Apply the rule to specific resources, enabling different pricing per resource.
  2. Activity Period: Set a start and end date for the rule's validity.
limitation
{
  "limitation": {
    "dates": [
      {
        "start": "2021-01-01T00:00:00Z",
        "end": "2021-02-01T00:00:00Z"
      }
    ],
    "daysOfWeek": 3,
    "resourceIDs": [
      "6c5cba5e-52da-4ca3-8f86-25b3d09e0fb5"
    ]
  }
}

Best Practices and Considerations​

  1. Cover All Scenarios: Ensure your price rules cover all possible booking scenarios to avoid pricing gaps.
  2. Rule Hierarchy: Organize rules from most specific (highest priority) to most general (lowest priority).
  3. Seasonal Pricing: Use activeFrom and activeTill dates to implement seasonal pricing strategies.
  4. Resource-Specific Pricing: Utilize the resource limitation to set different prices for different room types or properties.
  5. Testing: Thoroughly test your pricing rules with various booking scenarios, including stays that span different price rule periods.
  6. Documentation: Maintain internal documentation of your pricing strategy for easier management and troubleshooting.

API Reference​

For detailed information on implementing and managing price rules through our API, please refer to the Pricing API Documentation.

By leveraging these pricing capabilities, you can create effective pricing strategies for days services that balance profitability with attractiveness to clients, while ensuring a smooth booking experience for longer-term stays.