Skip to main content

Introduction

The OTS FlatFile is developed to allow customers to store a limited set of prices and availability without any calculation logic. As portfolio is client-specific and client-specific, marketing actions, guarantees, etc. need to be considered, the OTS FlatFile can only be used for the ClientID it has been generated for. It is meant as an immediately searchable cache file. Three versions available:
  • Version 1: Without RatePlans.
  • Version 2: Accommodates RatePlans.
  • Version 3: Extended RoomCodes (30 chars) and RateplanCodes (20 chars).
The file format provides for all hotels in the client portfolio, all rooms and boards available, end-prices for all arrival dates, all occupancies, and all possible length of stays up to 28 days. This results in an extreme volume of data. Example calculation:
  • 5,000 hotels
  • Average 3 room types
  • Average 3 boards
  • Lengths of stay: 25 (3–28)
  • Arrival days: 330 (not all hotels have a valid contract for a full year)
  • Adults: 1–3 (2.6 used for calculation)
  • Children: 1 of 5 years old (1.7 used for calculation)
This can result in over 1.6 billion lines per delivery if all hotels have availability for all arrival dates.
FlatFile is not suitable for systems that must produce search results for any occupancy or child age outside the agreed parameters. For more flexibility, use the Notification based model.
Before installation, limitations are agreed with the client to limit data size and focus on relevant concepts. For example, only certain lengths of stay or occupancies may be included.

Delta deliveries

From Q2 2026, FlatFile allows delta deliveries. File Logic
  • When delta deliveries are active, one FlatFile per hotel is sent at every delivery (full or delta), instead of one FlatFile for the whole portfolio.
  • A delta delivery is a zip containing one file per changed hotel.
  • The expected frequency when working with deltas is a weekly full and a couple of delta deliveries a day.
  • An individual hotel file from a delta should substitute the previous file from that hotel and all its rates.
  • A hotel deactivation will be shown with an empty file.

FlatFile Schedule Parameters


FlatFile Structure

V03 (RatePlan + Multicontracting) Separated RatePlan

V03 (RatePlan + Multicontracting) Concatenated RatePlan

V02 (RatePlan 10 chars, Room code 20 chars)

V01 (No RatePlan, Room code 10 chars)


FlatFile Details

  • Version number: Current version is 03. Older versions available for backward compatibility.
  • Record format / Action:
    • I: insert
    • U: update (partial)
    • D: delete
    • F: full update (replace)
  • PriceLine number: Unique per provider.
  • Hotel code: 17 chars, may have empty spaces for shorter codes.
  • Room code: Assembled from room characteristics (type, grade, view, etc.).
  • RatePlan code: Assembled from RatePlan characteristics (type, group, refundability, etc.).
  • Board code: Defines meal plans (e.g., Half Board, All Inclusive).
  • Arrival date: yyyy-mm-dd
  • Length of stay: 2 chars, e.g., 08 for 8 nights.
  • Occupancy: Total, adults, children, infants, with ages.
  • Price: Currency, right-aligned, 2 decimals.
  • Remaining rooms: Number of free hotel units at the time the PriceLine was produced.
  • Offers applied: Specification of offers applied in this PriceLine.

Offer Codes Table

Check our codes -> Price Breakdown Codes

Examples

When developing the FlatFile, always request an example file generated with your parameters from our INT environment to test the full flow, including making Quotes to test price consistency.

Generation Report via Email

Clients can receive daily generation emails with a list of hotels included in the generation. The email contains:
  • Type of generation
  • Status (Success/Error)
  • Additional info/Errorcode
  • Parameters (Client, Stock group, Boards, Dates, Durations, Min/Max adt/chd, Max pax, Chd age, Offers version, Search type, Offers specified)
  • FTP Transfer Details (Server type, Host, Username, Output filename, File size, Transfer times and speeds)
  • Operation Details (Threads, Parts, Compression, Download/Processing/Generation times and speeds)
  • Report (Searched stocks, Emitted stocks, Emitted datasets)

For any implementation, coordinate with Axis Data to define the exact FlatFile parameters and structure for your use case.