# Extras
Applies to Administrator
Extras are optional services/products that a customer can book; like transfer, catering, pension, rental car, etc. This page allows users to create and configure various extras that can be associated with bookings or transport options.
#### Brands
Allow the user to assign an extra to an agency. An extra can be assigned as follow:
* not assigned
* for sale - the extra can be booked only on office;
* internet sale - the extra can be booked only on WB
* for sale + internet sale - can be booked both, office and WB
* guide sale - can be booked only by a guide agent
* hotel sale - can be set only by a hotel agent
* guide sale + internet sale + for sale - can be booked by a admin, guide or a WB
### **Overview:**
| Field | Description |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name** | The public name of the extra, visible to customers. This is required. |
| **List Name** | Internal name used for lists or back-office reference. |
| **Code** | Unique identifier for the extra. Used for backend reference or integration. |
| **Status** | Visibility status. Set to `visible` to allow the extra to appear in search and bookings. |
| **Stop Sales Hours** | Time before departure when this extra will no longer be available for booking. |
| **Minimum Length** | Minimum number of days a trip must be to allow this extra. |
| **Contract Type** | Specify the contract type (Allotment, Guarantee, Request, FreeSell). |
| **Days Prices Option** |
Allows limiting the prices per day options presented to the web user. Default is 0 if no variation. Only works for prices declared with days!!!!!! If no Days are declared, the product will be removed! Ex: stay days = 14 days price option = 1 price days = 7,14,21
price days >= stay days - X
7,14,21 >= 14 - 1 => 14,21
|
| **Allotment Type** | Is used to control the number of products available and the time they are available in. The choices are **Manual, Generic** and **Linked to transport** |
| **Extras Category** | Categorize the extra (e.g., Meal, Transfer, Tour). The user can choose from the dropdown one of the categories created in the Extras Category. This is required. |
| **Age** | Define the applicable age group (e.g., Adult, Child, Infant). |
| **Period/Trip Length** | Limit availability by trip length interval. |
| **SSR Codes** | Assigns a SSR code to the extra and when chosen in a booking, the SSR code is reported to the transport company, thus keeping an evidence of passengers |
| **Select Supplier** | Assign a supplier responsible for fulfilling the extra. |
| **Round Rule** | Set rounding logic for pricing |
| **One-Way (only)** | Tick this box if the extra applies to one-way trips only. |
| **Currency** | Choose the currency for pricing. |
| **Maximum Length** | Specify max trip duration for which the extra is valid. |
| **Currency Prices** | Enable this to input separate prices per currency. If selected, the sales price for each brand will be calculated from the default price, using the relevant currencies. The sales prices are not updated for existing bookings. **Example:** The company currency is EUR, and the brand currency is SEK. The currency rate has changed from 11,55 to 11,3. This update will trigger the service to run an automatic update of the pricelist. |
| **Show Supplier on Ticket** | Toggle if supplier details should appear on customer tickets. |
### Custom Text
Used to customize the appearance and description of the extra in booking flows or documentation.
| Field | Description |
| --------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Name** | Custom label to override the default extra name. |
| **Description** | Rich text editor for detailed descriptions, highlights, or disclaimers. This text can be found in Guest APP and Guide APP. |
### Automatic Billing
Allows integration with internal billing and accounting systems for accurate cost tracking and supplier payouts.
| Field | Description |
| ------------------------ | -------------------------------------------------------------------------------------------- |
| **Department Code** | Accounting department code for internal tracking. |
| **Account Debit** | Account to be debited for this extra. |
| **Account Deposit** | Account to receive the deposit related to the extra. |
| **Add Own Schedule** | Enable to add the extra to its creditor extra schedules, which generates a separate invoice. |
| **Schedule** | Define one or more billing schedules (Daily, Weekly, Monthly and Annually). |
| **Select Creditor** | Choose the supplier to be paid for the extra. |
| **Creditor Currency** | Set the currency for the creditor’s payout. |
| **Automatic Billing** | Enable automated billing upon booking. |
| **Schedule in the Past** | Allows scheduling billing for past dates (use with caution). |
### Golf Course
This section is shown **only when an Extra is configured with the type *****Golf***.\
If the Extra has a different type, this section is not displayed.
#### Rounds
Defines how many golf rounds are included in this extra.
* Numeric value
* Represents the maximum number of rounds for one booking. Valid number are 1 to 99
* Used by the system when calculating and validating the golf product in the booking
Example:\
If **Rounds = 5**, the guest is entitled to five rounds of golf.
#### Product Parent ID
Internal identifier that links this golf extra to its parent product in Tourpaq.
* Used internally by the system to connect related products
* Fill Product ID when you want to use genarated allotment from another Product.
#### Important
These fields are **only relevant for Extras of type Golf** and are ignored for all other Extra types.
### Behaviour Settings
These settings control how the extra behaves in the booking process and what logic or restrictions apply to its use.
Setting
Description
Autoselect in booking & offer
Automatically selects this extra during booking and in special offers. Useful for mandatory or strongly recommended extras. The product will already be selected by default in a new booking. When using this feature, please make sure the product does not have a discount linked to it.
Unremovable On Web Booking
Prevents customers from removing the extra themselves during online booking. Ideal for required services.
Unremovable On Customer Center
Prevents removal by users in the customer self-service portal.
Add price to deposit
Includes the price of this extra in the booking deposit calculation.
Include in basic price
If checked, this will include the price of the extra in the basic prices of the booking. This is often used in combination with "Autoselect in booking & offer.
Add On All Pax
If selected for one passenger in webbooking, the product will be automatically selected for all eligible pax of the booking; If removed, will be removed from all.
Add only one per room
Limits the extra to one per room regardless of the number of passengers.
Available to book (API)
Check whether a product should be shown as available to book in the Offer API, without adding it to the total.
***
### Other Settings
These settings influence how the extra interacts with billing, privacy regulations, and system integrations.
| Setting | Description |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **Issue Voucher** | Enables the generation of a voucher for the extra. |
| **GDPR Sensitive** | Flags the extra as containing GDPR-relevant data. Triggers data protection measures. |
| **Content Type** | Used to classify the extra as a specific content asset, useful in API or content-driven environments. |
| **Package Type** | Treats the extra as a package rather than a standalone item. May impact how it's displayed or billed. Activate the Package Content tab |
| **Use Stay Dates in Prices** | Prices are calculated based on the customer’s actual stay dates rather than fixed pricing. Helpful for seasonal or dynamic pricing models. |
***
### Board Supplement
This section is shown **only when an Extra is configured with the type Pension**.\
If the Extra has a different type, this section is not displayed.
#### Fields Description
**Board type**
Dropdown field that defines the target board for this supplement.
Example:
* HB – Half Board
When selected, the Extra is treated as a supplement related to that board type. This means the system understands that the Extra modifies or upgrades the board basis of the room.
**Board basis filter**
Filter is used on Board Supplements to specify which Board Basis should be on the Room for the Board Supplement to be available.
### Clone Extras
The **Clone** functionality allows you to duplicate an existing extra configuration and reuse it for another product, period, or brand.
Instead of creating a new extra from scratch, cloning copies:
* Core configuration (Overview, Basic Setup)
* Prices
* Allotment
* Resources
This reduces manual work and ensures consistency across products.
{% hint style="info" %}
After cloning has been done, the new extra must be reassigned to a Brand and the rest of the settings that were not cloned must be redone.
{% endhint %}
The Clone Extras feature is used to:
* Create similar extras quickly
* Reuse seasonal configurations
* Copy extras to another accommodation
* Duplicate pricing structures
* Maintain standardized setup across brands
#### How to Clone an Extra
1\. Locate the Existing Extra - Navigate to: Extras → Search → Open the extra you want to duplicate.
2. Click “Clone” - Select the **Clone** option
3. Select the code for the new Extras
4. Define Clone Settings
You need to:
* Enter a new Name
* Assign to another category
* Adjust validity dates
* Update brand assignment
* Modify price if needed
4. Save - Confirm creation of the cloned extra.
5. Review Configuration
Important:
* Verify pricing
* Check validity dates
* Confirm category
* Test booking flow
* Review communication rules
***
### FAQ
#### 1. Why can’t I see the extra when I try to book it?
**Q:** The extra exists, but it doesn’t show up in Office/Web Booking. Why?\
**A:** Check `Status = visible`, and check the `Brands` channel setup (for sale / internet sale / etc.). Also confirm it’s in the right `Extras Category` and matches any `Minimum Length`, `Maximum Length`, and `Period/Trip Length` limits.
#### 2. What’s the difference between “for sale” and “internet sale” in Brands?
**Q:** Which one should I use?\
**A:** `for sale` means Office only. `internet sale` means Web Booking only. Use `for sale + internet sale` if it should be bookable in both channels.
#### 3. Why does the product disappear when using Days Prices Option?
**Q:** I set a `Days Prices Option`, and now the extra gets removed.\
**A:** `Days Prices Option` only works for prices that have `days` defined. If none of the prices have `days`, the product is removed from the selection.
#### 4. How do I make an extra mandatory?
**Q:** I want it selected by default, and customers shouldn’t remove it.\
**A:** Enable `Autoselect in booking & offer`. Then enable `Unremovable On Web Booking` and/or `Unremovable On Customer Center`, depending on where it must be locked.
#### 5. What does “Include in basic price” actually do?
**Q:** Does it hide the extra or remove it?\
**A:** It hides the extra from the customer view in Web Booking and Customer Centre. It still increases the base price. It affects booking totals.
#### 6. Will “Currency Prices” update existing bookings?
**Q:** We changed currency rates. Will old bookings get updated?\
**A:** No. Currency price calculation affects new pricing logic. It does not update sales prices for existing bookings.
#### 7. Where does “Custom Text” appear?
**Q:** Who will see the name/description entered here?\
**A:** The `Description` text can be shown in Guest App and Guide App. It can also be used to control how the extra is presented in booking flows.
#### 8. What are SSR Codes used for?
**Q:** Why should I add an SSR code to an extra?\
**A:** If the extra is selected in a booking, the SSR code can be reported to the transport company. This creates an evidence trail for passenger requests.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://manual.tourpaq.com/extras-setup/extras.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.