# Export ### Overview Tourpaq Office supports exporting structured data for various business roles: hotel suppliers, guides, transport managers, and reporting personnel. Exports are generated in **Excel-compatible XML format** and are filtered based on **date intervals**, **transport**, **resorts**, **hotels**, and more. *** ### Purpose The export module was designed to: * Provide relevant, filtered data to external partners. * Support integration with other systems via structured XML. * Enable custom exports per business role (guides, suppliers, managers). * Track changes to bookings over time for transparency and operations tracking. *** ### Preconditions Before generating an export: * User must be authenticated with export permissions. * Bookings, transports, hotels, and related data must be available in the system. * The export templates must be configured in the system backend. * Optional: Booking history tracking must be enabled for change logs. *** ### Export Types & Explanation #### 1. **Hotel List Export** * **Goal**: Provide hotel partners with grouped booking summaries. * **Grouped by**: Hotel → Stay interval → Room type → Booking * **Columns**: * Holiday interval (stay period) * Room code and name * Room units booked * Passenger count * Booking number and booking date * **Header**: Includes agency info, supplier contact, hotel name/code, export date * **Footer**: Total number of passengers for the hotel *** #### 2. **Rooming List Export** * **Goal**: Detailed room assignments and passenger-level data * **Grouped like hotel list**, with additional fields: * Passenger name, gender, age * Flight in/out numbers * Room number inside booking * Optional company-specific columns: * Extra pension/car/VIP/tours * **Used by**: Hotel front desk, logistics, on-site coordinators *** #### 3. **Guide List Export** * **Goal**: Help guides prepare for on-the-ground operations * **Grouping**: Hotel → Stay period → Room type → Booking * **Columns**: * All rooming list data + * Transfer status * Insurance code * Contact info (email, phone) * Guest comments (preferences, feedback) * Supplements selected *** #### 4. **Passenger List Export** * **Goal**: Provide a clean list of passengers for a stay period * **Grouped by**: Transport interval → Hotel * **Header**: Shows used filters (country, resort, flight) * **Columns**: * Stay period * Hotel code/name * Booking info * Passenger details * Transfer presence * **Footer**: * Totals by transport (with breakdown by age) * Totals by hotel * Totals by transfer presence *** #### 5. **Canceled Booking Export** * **Goal**: Show all canceled bookings (excluded from other exports) * **Grouped by**: Hotel → Stay period → Room type * **Columns**: * Stay interval * Room code and name * Booked units * Passenger count * Booking number and name * Cancellation date *** #### 6. **Bookings Change List Export** * **Goal**: Track all significant booking changes since a selected date * **New Filter**: `Changes From` (start date for change log) * **Types of Changes**: * **New bookings**: Created or changed from ERROR to OK * **Canceled bookings**: Changed from OK to ERROR (excluding transient or reverted changes) * **Modified bookings**: Any updates to hotel, room, passenger, period, etc. * **Data Grouping**: * Hotel → Stay period → Booking * **Columns per change**: * Booking no., date * Change date * Change type * Old value (From) & new value (To) * Element code/name if available * **Passenger-level changes include**: * Gender, age, name updates * Transfer added/removed * Discounts or extras (car, pension, VIP, etc.) *** ### Export Filters (All Templates) | Filter | Description | | -------------------------------- | -------------------------------------------------------------------------- | | **Agency / Brand** | Limits exports to one or more agencies | | **Arrival Date Interval** | Bookings where the stay begins within this period | | **Booking Date Interval** | Bookings created in this period | | **Report Type** | Choose from hotel list, rooming, guide, passenger, canceled, change list | | **Transport** | Multi-select filter by travel options used | | **Country / Resort** | Filter by destination country or specific resort(s) | | **Hotel** | Export only data related to selected hotels | | **Cancellation Date (Optional)** | Only for canceled exports; limits results to bookings canceled in range | | **Changes From** | Specific to Change List; defines starting point for change history logging | *** ### Notes & Special Behaviors * **Repeatable blocks**: Many exports (hotel, rooming, guide) are structured in repeatable XML blocks per hotel. * **Optional company fields**: Some exports include dynamic columns depending on company settings (e.g. VIP codes, party package names). * **Passenger focus**: Passenger exports are ungrouped, flat listings with optional statistical footers. * **Error state**: Bookings in `ERROR` status are conditionally included depending on context (e.g. revalidated as OK or canceled). *** ### Tips for Developers * Use XML templates with clear structure and schema validation. * Booking history module must track every relevant field for change logs to be accurate. * Pay attention to status transitions: `ERROR` ↔ `OK` define inclusion/exclusion in exports. * Many exports share structure logic (inherit or reuse parsers where possible). * Data anomalies usually stem from edge cases in booking status transitions or outdated rules. *** ### FAQ #### Which export should be used for hotel reception or room allocation? Use the **Rooming List Export**. It includes passenger-level details, room context, and arrival/departure information needed by hotel operations. #### Which export should be used for guides or destination staff? Use the **Guide List Export**. It adds transfer data, insurance details, contact information, comments, and selected supplements. #### Why are canceled bookings missing from standard exports? Canceled bookings are normally excluded from standard operational exports. Use the **Canceled Booking Export** when canceled bookings must be reviewed separately. #### When should **Changes From** be used? Use **Changes From** for the **Bookings Change List Export**. It limits the result to bookings changed on or after the selected date, based on booking history. #### Can bookings in `ERROR` status appear in an export? Yes, but only in specific cases. This mainly applies to change tracking or status transitions where a booking moved between `ERROR` and `OK`. #### Why does an export contain fewer bookings than expected? Check the active filters first. The most common causes are date intervals, hotel or resort filters, transport filters, or a mismatch between booking date and stay date. #### When should ZIP compression be used? Use ZIP compression when the export file is large or sent by email. This reduces file size and helps avoid attachment size limits. *** ### Related pages * [Lists](/export-1/lists.md) — Export booking lists with filters, report types, and scheduling support. * [Export - Scheduled Reports](/export/export.md) — Configure recurring export delivery. * [Extras List](/export-1/extras-list.md) — Export supplier-facing extra service data. * [Flight Transfer Export](/flight-transfer-export.md) — Export transfer-related transport data. * [Golf Course Report](/tee-time-extras-list/golf-course-report.md) — Export tee time and golf-related operational data. --- # 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/export-1/export.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.