General Settings
Overview
General Settings defines the core configuration of a Brand in Tourpaq. These settings control identification parameters, numbering ranges, default contact information and selected functional modules available for that specific brand.
This section is mandatory for correct system behavior and must be configured before the brand is used in production.
Purpose
The purpose of General Settings is to:
Define the brand identity in the system
Configure unique numbering intervals for bookings, offers and gift cards
Set default contact details used in communication flows
Enable or manage connected modules such as Ticket, Insurance and Other Settings
Ensure that no ID conflicts occur between brands
Incorrect configuration can result in overlapping booking numbers or inconsistent communication output.
Instructions
1. Access the Section
Go to: System Setup → Brands → General
Select the relevant Brand from the list.
2. Brand Identification
Brand* - Enter the official brand name. This is displayed internally and in selected documents.
Brand Code - Optional short identifier for integrations or internal filtering. It is used in Flight Transfer List and Hubspot.
3. Contact Information
Contact Email Address* Primary outgoing email address used for communication from this brand. It is used in relation with the customers or partners - may appear on ticket, vouchers and export lists. Example: booking confirmations, notifications, system emails.
Bcc Email Address Optional. All outgoing emails will include this address as blind copy.
4. Booking ID Configuration
Each brand must have its own unique numbering interval.
Booking IDs Start From* Defines the first booking number that can be generated.
Booking IDs Ends To* Defines the maximum allowed booking number.
Important:
Ranges must not overlap with other brands.
Once bookings are created, changing the range requires caution.
5. Offer ID Configuration
Offer IDs Start From* Starting number for offers.
Offer IDs Ends To* Maximum offer number.
These ranges must also be unique per brand.
6. Gift Card ID Configuration
Gift Card IDs Start From* Starting number for gift cards.
Gift Card IDs Ends To* Maximum gift card number.
Ensure no overlap with other brands.
7. Up Sales Tooltip
Optional informational text shown in upsell context. Use this field to guide users when additional services are offered.
Additional Brand Sections
On the right side, the following expandable modules are available:
Ticket
Insurance
Other Settings
Each section contains configuration related to its functional domain and can be expanded individually.
Ticket
The Ticket section defines the legal, financial, and display information shown on customer tickets generated by the system.
All configurations in this section apply at brand level and affect every ticket created under the selected brand.
Expected Behavior
The system allows administrators to:
Define company and legal information displayed on tickets
Configure banking details for payment instructions
Add legal or explanatory texts
Control which sections are visible on the ticket
Upload branding elements such as logo and banner
All changes take effect after saving.
Configuration Fields
1. Company & Legal Information
These fields define the official company details displayed on the ticket:
Version – Selects the ticket layout version (Version 1 - Version 3)
Country – Company country
GeoMap Country – Country used for map integrations
Postcode – Postal code
Place – City
Address – Full company address
Cvr no – Company registration / tax number
Phone – Contact phone number
Fax – Fax number
This information is printed on the generated ticket.
2. Bank Information
These fields define payment-related details:
Bank – Bank name
Creditor number – Registered creditor ID
IBAN number – IBAN
BIC Code SWIFT Address – SWIFT code
These details appear in the payment section of the ticket.
3. Payment Info
A free-text field used to provide:
Payment method explanations
Legal fiscal notes
VAT information
Additional payment instructions
The text entered here will be displayed on the ticket.
4. Ticket Help Text
Two editable WYSIWYG text areas are available:
Ticket help text comment
Ticket help text explanation page footer
5. Display & Visibility Settings
These options control which sections appear on the ticket:
Hide Payment Area - If checked, this will make the payment plan section to not show on ticket.
Show SSR On Ticket
Show Allocation Area - If checked, this will make the allocation area appear on ticket.
Hide Payment Details - If checked, this will make the payment plan with IBAN and swift not show on ticket.
Hide Payment Info Box - If checked, this will make the payment info box not show on ticket.
Hide Payment Info Box On Individual Ticket - If checked, this will make the payment plan with IBAN and swift not show on ticket.
Show Hotel URL - If checked, hotel URL will appear on ticket
Show Hotel Info - If checked, hotel address and thelephone will appear on ticket
Show Travel Time - If checked, travel time will appear on ticket
Show Arrival Hour - If checked, arrival hour will appear on ticket
Add hotel description page - If checked, adds a page at the end of the ticket that represents the hotel description as set in web tab of the hotel
Add hotel facility dedicated page - If checked, adds a page at the end of the ticket that represents the hotel's selected facilities
Selecting or deselecting these options directly affects the ticket structure.
6. Visual Elements
Logo – Logo displayed on the ticket
Banner – Banner image used on the ticket
Uploaded images are automatically applied to all tickets for the selected brand.
Insurance
The Insurance section under Brands > General controls the integration between Tourpaq and the selected insurance provider.
This setup ensures that travel insurance products can be offered, booked, and transmitted correctly to the insurance company. The configuration is brand specific, meaning each brand can have its own insurance agreement and credentials.
Only one provider can be active at a time.
Purpose
The purpose of this configuration is to:
Enable insurance sales in bookings
Authenticate communication with the insurance provider
Define the valid sales window for insurance policies
Control where insurance notifications are sent
Incorrect configuration may result in failed insurance bookings or missing confirmations.
Fields Description
Insurance Provider
- Europaeiske / Gouda Select the insurance provider linked to the brand agreement. This determines which API and credentials will be used.
Insurance Agent Username * - The username provided by the insurance company. Used for authentication when sending insurance bookings.
Insurance Agent Password * - The password linked to the agent username. Used together with the username for secure communication.
Insurance Agent Code * - The official agent code assigned by the insurance provider. Identifies the agency within the insurance company’s system.
Insurance Agency Code * - The agency or branch code provided by the insurance company. Used for reporting and contract identification.
Days No Before/After Departure * - Defines the allowed time window for selling insurance in relation to departure date.
Example: If set to 120 and reference is Departure Date, insurance can be sold up to 120 days before or after departure, depending on provider rules.
This prevents insurance from being sold outside the allowed timeframe.
Insurance Notification Email - Email address that receives insurance notifications or error messages from the system.
Other Settings
Overview
The Other Settings section contains configuration options that control:
Web booking behavior
Customer data requirements
Cancellation and change restrictions
Pricing visibility
Localization (currency, culture)
Integrations and API fields
Brand-level system rules
These settings apply at brand level and impact both BackOffice and Web Booking flow.
Purpose
This section allows you to:
Define how customers interact with the web booking
Control what data is mandatory
Set time limits for changes/cancellations
Configure localization and pricing rules
Manage integrations and system behaviors
⚠️ Changes here affect all bookings under the brand. Always verify before modifying.
Field-by-Field Explanation
1. Web & Link Settings
Web Booking Link - URL used for staging enviroment booking
Confirmation Link
Website Reset Cache Link - URL used to reset website cache.
Terms and Conditions Page Link - Link to the brand’s Terms & Conditions page.
Personal Data Policy Page Link - Link to GDPR/privacy policy page.
Uses custom text - For the Web Booking to react to this change, please inform Tourpaq Support as a website restart is needed.
2. Voucher Settings
Voucher IDs start from - Starting number for generated vouchers.
Voucher IDs ends to - Maximum number allowed for voucher numbering.
Cancellation & Change Rules - These fields define how many days before departure changes are allowed.
Allow Cancel. Ins. changes - Number of days after booking date cancellation insurance can be modified.
Stop Web Transport seating selection - Number of days before departure when seat selection is blocked online.
Stop Web changes - Number of days before departure when general booking changes are blocked online.
Stop Name changes - Number of days before departure when passenger name changes are no longer allowed.
3. Age Settings
Max Child Age - Defines the maximum age considered as a child. Affects pricing and child-related rules.
Retrieve age from - Determines how the system calculates age. Usually from Date of Birth.
4. Localization & Currency
Currency - Defines the brand’s main currency (e.g., DKK).
Culture Info - Defines language and regional formatting (e.g., Danish – Denmark). Affects date format, number format, etc.
Economics Numeric - Enables numeric economic formatting rules. Used for financial data consistency.
5. Pricing & Cost Behavior
Ignore Transport Cost - If set to TRUE, transport cost is excluded from pricing calculation.
Min Price Per Child For Selling Price - Minimum allowed selling price for child passengers.
Hide included extras prices - Hides individual prices for included extras in booking view.
Show adjustment prices on booking - Displays price adjustments (manual corrections) in booking details.
6. Insurance & Web Control
Make cancellation insurance mandatory - Forces customers to add cancellation insurance.
Force web deposit - Requires deposit payment during web booking.
7. Passenger & Data Requirements
Mandatory DOB in Passenger Details in BackOffice - Date of Birth becomes required field when creating a new customer in Office, and DOB will be auto-filled in the passenger overview.
Mandatory email in Passenger Details in BackOffice - Email becomes required field when a new customer is created in Office
Ask for default adult age in BackOffice - Prompts user to enter adult age if not provided.
Autocomplete passenger names from last booking - Prefills passenger names from previous bookings.
8. Communication Settings
Send SMS from - Set the number that the receiver will see as the sender of the SMS (only for Compaya Provider)
Ask customer to opt in newsletter - Shows newsletter opt-in checkbox in booking flow.
9. Brand & UI Controls
Hide Brand - All information on the brand will be hidden in the system.
Use Wishlist - Enable ability for passengers to pay instantly for added products on fuly paid booking. If payment is canceled, products are stored in wishlist to be paid later.
10. Offers & API Integration
Uses Restful Offer API - Checks whether the agency uses the RESTful Offer API.
Rate Code - Used for rate mapping with external systems.
Destination API Token - Delete user tokens after X minutes. The default value is 30 minutes if not set.
Ticket Customization – Version 3
Overview
Ticket Customization is available only when the user selects Ticket Version 3. For other ticket versions, this section is not displayed and no visual customization can be applied.
This functionality allows configuration of the visual identity of the generated ticket. The settings defined here control colors, images, icons and typography used in the final ticket output. All changes apply to newly generated tickets after saving the configuration.
Purpose
The purpose of Ticket Customization is to:
Align the ticket design with the customer’s branding guidelines
Provide flexibility for different client templates
Improper configuration may lead to unreadable tickets or inconsistent brand presentation. Always validate changes in a test booking before deploying to production.
Field-by-Field Explanation
1. Faded Color
Secondary gradient color used in the ticket background. It works together with the Main Color to create the gradient effect in Version 3. Used for visual depth and background transitions. It usually represents a lighter tone of the primary brand color.
2. Main Color
Primary brand color used in headers, highlight areas, buttons and key visual sections of the ticket. Defines the dominant visual identity of the ticket.
Important: The Main Color directly impacts visibility of headings and structural blocks.
3. Customer Info Image
Main decorative image displayed in the Customer Information section of the ticket.
Instructions
Click “Click to browse or drag and drop here”.
Upload a high-resolution image.
Recommended format: PNG or JPG.
Recommended orientation: landscape.
Avoid text-heavy images, as text may overlap.
Best practice: Use compressed images optimized for PDF output to avoid large file size.
4. Customer Info Decorator Image
Small decorative graphical element displayed near the Customer Information section. Enhances visual appearance without affecting core content.
Instructions
Upload a transparent PNG for best results.
Keep the design minimal.
Avoid large images that dominate layout.
Typical usage: lines, abstract shapes, light branding accents.
5. Hotel Star Representation
Icon used to represent full hotel star classification. Defines how hotel rating stars appear visually on the ticket.
Instructions
Upload the icon that represents one full star.
Prefer SVG or high-quality PNG with transparent background.
Maintain small dimensions to ensure clean repetition.
Note: The system repeats this icon based on the hotel’s star rating.
6. Hotel Half Star Representation
Icon used when hotel rating includes a half star (e.g. 3.5 stars). Ensures accurate graphical representation of non-integer ratings.
Instructions
Upload a half-star version consistent with the full star design.
Ensure visual alignment with the full star icon.
Use transparent background.
Consistency between full and half star icons is mandatory.
7. Font Type
Defines the font file format used in the ticket.
Available Option:
opentype
truetype
woff
woff 2
Controls typography rendering in the generated document.
Instructions
Select the correct font format from dropdown.
Ensure uploaded font files match the selected format.
Confirm licensing rights before using commercial fonts.
8. Regular Font File
Font file used for standard text (paragraphs, passenger names, descriptions). Defines readability and base typography of the ticket.
Instructions
Upload the regular font file
Ensure file format matches selected Font Type.
Test special characters and multilingual support.
Important: If the font lacks character support, some languages may render incorrectly.
9. Bold Font File
Font file used for headings and emphasized text.
Instructions
Upload the bold version of the same font family
Ensure font family consistency with the Regular font.
Avoid mixing different font families unless approved by design guidelines.
Validation Procedure (Mandatory)
After making any changes:
Save configuration.
Generate a test booking.
Export the ticket.
Validate:
Color contrast
Image scaling
Star alignment
Font rendering
File size
Confirm no layout breaks occur.
Never deploy branding changes directly in production without validation.
Operational Notes
Ticket Customization is exclusive to Version 3.
Changes do not retroactively modify already generated tickets.
High-resolution images increase PDF size and processing time.
Validation Checklist
Before saving:
Confirm all mandatory fields are completed
Verify ID ranges do not overlap with another brand
Confirm email address is correct and active
Validate numbering intervals match business expectations
After configuration, save the changes and perform a test booking to confirm correct ID generation.
Last updated
Was this helpful?