Releases

Overview

Hotel release rules automate when rooms are released back to the supplier.

Rules are configured by company administrators.

Each rule belongs to one hotel.

Rules cannot be reused across hotels.

Dates in the examples use the format DD-MM-YYYY.

Related pages

• Hotel release - automation

• Hotel release - Reporting

Purpose

• Release unused room allotments on time.

• Email suppliers a release report.

• Support both hotel-wide and room-type rules.

• Keep a log for auditing.

How “days in advance” is evaluated

Treat days in advance as the lead time.

• A value of 0 means “release on the same day.”

• A value of 5 means “release 5 days before the target date.”

When a release runs

Releases are executed by the daily release automation.

The automation runs once per day per company.

Each rule can therefore trigger at most once per day.

Single-day rule (specific target date)

Use this when you want a release tied to one target date.

The rule triggers on:

target date - days in advance

Example: target date 20-05-2026 with 5 days in advance triggers on 15-05-2026.

Period rule (runs once per day in a period)

Use this when you want releases evaluated daily within a start/end period.

On each daily run, Tourpaq releases the target date that matches the rule’s lead time.

Example: a rule with 3 days in advance evaluated on 15-05-2026 targets 18-05-2026.

Examples

Scenario setup

• Today: 15-05-2026

• Hotel “Grand Palace” has room types 1S, 2C, 3F

• Inventory period: 01-04-2026 to 01-09-2026

Hotel-wide release rule (all room types)

• Rule: Release date 20-05-2026, days in advance 5, email [email protected]

• Result: On 15-05-2026, all rooms (1S, 2C, 3F) are released.

• A log entry is created.

• A report email is sent.

If days in advance is blank, the system defaults to 0.

Room-type release rule (within a period)

• Rule: Start 01-05-2026, end 01-06-2026, room 2C, days in advance 3, email [email protected]

• Result: On 15-05-2026, room type 2C is released for 18-05-2026.

• A log entry is created.

• A report email is sent.

Supplier administration

Suppliers can review and manage released rooms in their Tourpaq supplier login.

They can decide if released rooms should be:

• removed from Tourpaq bookings, or

• reused for other channels.

Common filters:

• hotel

• room type

• time period

Release logs

Administrators can review release actions in Releases Log (Hotel → Tourpaq).

Filters include:

• supplier

• brand

• hotel

• room type

• period

Rule editing behavior

Edits to an active rule take effect after the current cycle completes.

Example:

• Old rule: 10 days in advance

• New rule: 4 days in advance

• Result: 10 continues until it expires, then 4 starts.

Editing releases in Allotment per Day

You can adjust release results per room type and date in Hotel → Allotment per Day.

This feature allows releases to be edited directly in Allotment per Day, at room and date level, using the same workflow as allotment corrections.

It is designed to handle frequent operational changes such as extending, shortening, executing, or revoking releases after they have already been applied.

See Allotments per day.

Release logic

• When a release is executed, the system stores how many allotment and secured rooms were released

• When a release is revoked:

  • Rooms are restored by default

  • Allotment room released (AR) and Secured room released (SR) become editable to allow partial restoration

• Allotment per Day values override the release defined in the contract

• Releases can be adjusted quickly at room and day level

How does the release work (value calculations)

This section documents the system behavior during the "Release" execution, comparing the pre-release state and the post-release state.

Before Release

After Release

Field	Before Release	After Release	Formula after release
NO	100	10	= Max(Book vs Guarantee)
SECURED	20	10	= Min(Secured vs NO After Release)
GUARANTEED	0	0	Remain unchanged
BOOK	10	10	Remain unchanged
AR	0	90	= NO Before release - NO After release
SR	0	10	= Secured Before release - Secured After release)

Release Behavior When Editing DAYS

When editing the DAYS value for a release, some of the affected dates may already be in the past. In this situation, the system will not clear the release checkbox if Current Date + custom days is earlier than the allotment date.

As a result, those past dates remain marked as released. Only dates that fall after the calculated release threshold will have the Release flag removed.

Example:

• Today’s date is February 2.

• All February dates are set to be unreleased, and the release period is changed to 7 days.

  
• According to the general rule, releases would normally start from Current day (February 2)+ 30 days.

  
• However, February has a custom release configuration, so the system instead applies February 2 + 7 days, which results in February 9.

  

Because the release calculation uses February 2 + 7 days (February 9) due to the custom configuration, any dates before February 9 will remain marked as released. Only dates from February 9 onward will have the Release flag removed.

FAQ

Who can create or change release rules?

Company administrators.

Can I reuse the same rule for multiple hotels?

No. Each rule belongs to one hotel.

What’s the difference between a hotel-wide rule and a room-type rule?

• Hotel-wide releases all room types for a hotel.

• Room-type releases one room type (typically within a period).

Can a release run multiple times per day?

No.

The release automation runs once per day per company.

What does “days in advance” mean?

It’s the lead time.

3 means the release runs 3 days before the target date.

Who receives the release email?

The email address saved on the rule that triggered the release.

Where can I see what was released?

Use Releases Log (Hotel → Tourpaq).

Filter by hotel and period for quick checks.

Do suppliers have to accept the release?

Suppliers can decide how to handle released rooms in their supplier login.