Hotels

Search and manage hotel records in Tourpaq Office for booking, contract, web, and supplier setup.

The Hotels page is the entry point for hotel master data in Tourpaq Office. It supports searching and validating hotel records before continuing setup in Hotel creation and commercial configuration in Hotel Contracts. The same hotel records are used in booking flows and operational reporting, including Booking overview and All bookings.

Navigation

Open Hotel → Hotels.

Requirements

• Access to the Hotel module.

• Permissions to view hotel master data.

• Administrator permissions for Create using wizard, Create, Edit, and Delete.

• Setup data for Destination and Resort before new hotel creation. See Destination and Resorts.

This page is typically used by administrator roles.

Overview

The page supports three tasks:

1. Filter and locate a hotel record.

2. Validate key master data from the result table.

3. Open or create a hotel for further setup work.

Purpose

Hotel master data is a dependency for:

• hotel selection in booking flows

• hotel allotment and release workflows

• supplier communication and supplier reporting

• web content and API output for accommodation

• finance flows that rely on supplier relations and contract data

Interface overview

The screen contains:

• Filters for narrowing the hotel list.

• A result table with core hotel master fields.

• Actions for creating, editing, and deleting hotel records.

Hotels list: filters, results table, and actions.

Field descriptions

Filters

Hotel

Filters the list by a hotel record.

This field is not mandatory.

This filter is used to locate a specific hotel before continuing maintenance in Hotel creation or reviewing commercial setup in Hotel Contracts.

Destination

Filters hotels by destination.

This field is not mandatory.

This filter relates to the destination structure used across Tourpaq. Destination setup is maintained in Destination.

Resort

Filters hotels by resort.

This field is not mandatory.

This filter relates to the resort structure used in hotel grouping, booking selection, and reporting. Resort setup is maintained in Resorts.

Display only Bed Banks

Shows only hotels linked to a bed bank/provider source.

This field is not mandatory.

This filter is used for validating imported hotels and for troubleshooting provider-linked content. Provider/import setup is maintained in System Setup – Hotel Providers and System Setup – Hotel Import.

Show hidden

Includes hotels hidden from normal selection.

This field is not mandatory.

This filter relates to the hotel status maintained on the hotel record in Hotel creation. Hidden hotels can still exist in historical bookings and remain visible in reporting depending on filters. See All bookings.

Clear

Resets active filters.

This control is not mandatory.

This control affects only the list view. It does not change hotel master data.

Table columns

All columns are read-only on this page. Changes are made via Edit.

Code

Shows the hotel code.

This field is not mandatory on the list page.

This value is a core identifier for internal reference, exports, reporting, and integrations. The value is set during hotel creation in Hotel creation or Create using wizard.

Name

Shows the hotel name.

This field is not mandatory on the list page.

This value is used for operational identification and can affect downstream display depending on web configuration. Web-related setup is maintained in the hotel record under Hotel creation.

Resort

Shows the resort linked to the hotel.

This field is not mandatory on the list page.

This value controls grouping and search behavior in several workflows. It also impacts reporting slices by resort. Resort setup is maintained in Resorts.

Supplier

Shows the supplier linked to the hotel.

This field is not mandatory on the list page.

This value is used in supplier communication and supplier reporting. Supplier master data is maintained under Suppliers.

Address

Shows the hotel address.

This field is not mandatory on the list page.

This value supports operational identification and can feed downstream documents and exports depending on setup.

City

Shows the hotel city.

This field is not mandatory on the list page.

This value helps distinguish hotels with similar names and improves reporting context.

Country

Shows the hotel country.

This field is not mandatory on the list page.

This value supports geographic segmentation and improves reporting context.

Phone

Shows the hotel phone number.

This field is not mandatory on the list page.

This value supports operational contact and follow-up when supplier communication is handled manually.

Fax

Shows the hotel fax number.

This field is not mandatory on the list page.

This value supports legacy communication flows where fax is still used.

Order No.

Shows the internal sort order number.

This field is not mandatory on the list page.

This value is typically used for controlling ordering in downstream lists, such as web lists or other consumers of hotel master data.

Bed Bank

Indicates whether the hotel is linked to a bed bank/provider.

This field is not mandatory on the list page.

This value supports troubleshooting of provider-sourced hotels and clarifies which hotels are managed directly versus imported. Related configuration exists in System Setup – Hotel Providers and System Setup – Hotel Import.

Actions

Create using wizard

Starts the guided hotel creation flow.

This action is not mandatory.

This action is used to create a hotel with minimum required data first. The wizard is documented in Create using wizard.

Create

Opens a blank hotel form.

This action is not mandatory.

This action is used when manual setup is required from the first step. Hotel fields are documented in Hotel creation.

Edit

Opens the selected hotel for maintenance.

This action is not mandatory.

Changes made via Edit can affect booking selection, contract logic, web display, exports, and reporting. Common next pages include Hotel creation and Hotel Contracts.

Delete

Permanently removes the hotel record.

This action is not mandatory.

Deletion can break references in reporting, contracts, and integrations. Hiding the hotel via status is typically safer than deletion.

Delete is destructive.

Deletion can impact reporting and historical references.

Configuration steps

1

Find and validate a hotel

Set Hotel, Destination, and Resort filters.

Validate the correct record via Code, Name, Resort, and Supplier.

2

Create a hotel record

Select Create using wizard or Create.

Continue setup in Hotel creation.

3

Continue downstream setup

Configure commercial logic in Hotel Contracts.

Configure metadata used for display and filtering in Facilities.

System behavior

Filters

• Filters affect only the list view.

• Clear resets filters and refreshes results.

• Display only Bed Banks is a fast way to isolate imported/provider hotels.

Hidden hotels

• Hidden hotels are excluded from most selection flows.

• Hidden hotels can still appear in historical contexts and reporting, depending on filters and report logic. See All bookings.

Deletion

• Delete removes the master record.

• Contract, reporting, and integration dependencies can be impacted.

Examples

Example: Troubleshoot a bed bank hotel

1. Enable Display only Bed Banks.

2. Filter with Destination and Resort.

3. Validate Bed Bank and Supplier in the list.

4. Continue provider/import checks in System Setup – Hotel Providers and System Setup – Hotel Import.

Example: Locate a hidden hotel for maintenance

1. Enable Show hidden.

2. Filter with Hotel or Resort.

3. Open with Edit and validate status and dependencies in Hotel creation.

Related pages

• Hotels list page

• Hotel creation

• Create using wizard

• Facilities

• Hotel Contracts

• Hotel reporting

• Destination

• Resorts

• Suppliers

• System Setup – Hotel Providers

• System Setup – Hotel Import

• Booking overview

• All bookings