Hotels and groups
Channel parity, overbooking, and a rate plan matrix that grew until nobody can explain a price.
Inventory that stays true across every channel, rate rules a revenue manager can change, a booking record that survives a schedule change, and a refund path that matches the law.
Tell us what you are building
Travel software development builds the systems behind the sell: one authoritative inventory, rate rules a revenue manager can change, a booking record that survives a schedule change, and a refund path that matches the law. Supplier certification, not engineering, usually sets the calendar.
Our work
We have no hotel, tour operator, online travel agency or airline among our clients, and saying so now is cheaper than you finding out on the second call. We have built the two things a booking system is made of: capacity sold against a slot that must still be right at the door, and channel feeds that restate themselves and must not be counted twice.
By operation
There is no single best: a vendor who names one is selling what it already built. Travel is one word for six businesses, each breaking differently. The seventh card is the one we are not the answer for.
Channel parity, overbooking, and a rate plan matrix that grew until nobody can explain a price.
Several suppliers with different cancellation terms, a combined liability modelled nowhere, and margin discovered after the season.
Search must be fast against inventory that changes constantly, every supplier answers in a different shape, and look to book makes caching a commercial call.
One booking exists as a passenger name record, an e-ticket and miscellaneous documents, so ancillaries reconcile separately.
Timed slots, per person rules and last minute capacity make availability a per minute question.
Build or buy
Sometimes the answer is to buy less software, not more. This is where we think the line falls, and we say it on this vertical more than any other.
Keeping dozens of online travel agency certifications current is commodity work with a permanent cost and no differentiation.
The booking
A trip can sit in three records, which is why an ancillary reconciles on a different path from the fare. IATA's ONE Order page calls those three gradually phasing out, with no completion date.
| Record | What it holds | What it means for the build |
|---|---|---|
| Passenger name record | The itinerary and the passenger. IATA's ONE Order page names PNRs among the records being phased out. | A schedule change can reissue the supplier reference, so key on your own identifier and keep theirs with history. |
| E-ticket and EMD | The fare document, plus separate miscellaneous documents for bags, seats and lounge access. IATA's ONE Order page names both among the records an Order replaces. | Store the issuing reference and the fare conditions, and model each ancillary as its own line with its own refund rule. |
| The Order | One record for fulfilment and accounting, under Resolution 797, dated June 2017 on IATA's ONE Order page. | Build an order shaped record now and keep speaking legacy beside it. Nothing published says when the old records stop. |
Each row is a record someone else owns, so your booking needs its own identifier. See our database and data modelling work.
Inventory and rates
Neither of the two IATA pages we read still states a version openly. Re-read on 17 November 2026: the NDC download page at iata.org is a request form that names no version, and standards.iata.org is a sign in workspace. On 13 November 2026 those same two pages showed 24.4 Schemas under a heading reading Latest release, December 2024, and release 26.3 dated 17 September 2026 called the IATA Offer and Order Standard. So get the version in writing from the party you integrate with, pin it in your message namespace and treat it as a long lived contract.
| Layer | What it is | The constraint that decides the plan |
|---|---|---|
| GDS | Amadeus, Sabre and Travelport. Legacy distribution still carries much of the traffic and assumes a PNR with separate documents. | A build cannot assume the airline side offers Orders, so keep a legacy path and plan for both. |
| IATA NDC | The XML standard for exchanging Offers and Orders directly. IATA's press release of 7 August 2014 calls Resolution 787 its foundation document. | A conference resolution is not a mandate, so support is per carrier and must be discovered. |
| The Offer and Order Standard | Read 13 November 2026: release 26.3 on the IATA standards portal, dated 17 September 2026, and 24.4 from December 2024 on the NDC branded download page. Re-read 17 November 2026, neither page states a version openly any more, so both figures are dated observations rather than what you will see today. | Target 26.x for new work while supporting partners on 21.3.x and 24.x. IATA's retailing page sets a goal of 100% Offers and Orders with no date on it, saying timelines vary by airline size and region. |
| Channel manager and ARI push | The layer pushing availability and rates outward and pulling bookings back. Every channel has its own retries and certification. | Make each handler idempotent on the channel's own reference and reconcile daily. Certification is calendar, not hours. |
| Hotel and cruise messaging | OpenTravel's download form, read 13 November 2026, lists 2024A as the newest 1.0 XML release while the 2.0 track stops at 2019A. | Specifications come on request, so plan that step before coding. HTNG joined the American Hotel and Lodging Association, announced 25 March 2021, and publishes no version numbers, so pin the file you were sent. |
Proving that a feed and your own records agree next morning is half the work. See the Django platform work behind our daily reconciliations.
Compliance
Six instruments, each with the date it applies from, the page it was read on and the date it was last read.
| Instrument | What it forces the software to do | Applies from |
|---|---|---|
| Regulation (EC) No 261/2004 | Article 7(1) on EUR-Lex sets EUR 250 up to 1,500 km, EUR 400 for intra-Community flights above that and others to 3,500 km, and EUR 600 beyond. Article 7(2) lets the carrier reduce them by 50 percent where the re-routing arrives within two, three or four hours of the original arrival, and Article 7(4) uses great circle distance. | In force 17 February 2005, per Article 19. Read 17 November 2026. |
| UK261 | The CAA calls it UK Reg (EU) No. 261/2004, also known as UK261, and sets GBP 220, GBP 350 and GBP 520 by distance at two, three and four hours late at the final destination, halved to GBP 110, GBP 175 and GBP 260. So a claims engine needs distance and actual arrival delay, in two currencies. | UK retained law, read on caa.co.uk. Read 13 November 2026. |
| Directive (EU) 2015/2302, Package Travel | Article 17 on EUR-Lex makes organisers secure the refund of all payments and, where carriage is included, repatriation on insolvency. So the protection reference is first class data. | Adopted by 1 January 2018, applied from 1 July 2018, per Article 28. Read 17 November 2026. |
| Directive (EU) 2026/1024 | The amending directive of 29 April 2026, on EUR-Lex, gives the organiser a refund from the service provider within seven days of a cancelled service, and a traveller must be told before accepting a voucher that a refund within 14 days is theirs by right. | Adopt by 29 September 2028, apply from 29 March 2029, per Article 3. Read 17 November 2026. |
| ATOL certificates | The CAA states a certificate must be issued immediately when a consumer makes the first payment, and that taking card details counts as payment. So generation is synchronous inside the payment transaction, never a nightly batch. Re-issue if a detail changes over 72 hours before departure. | The Civil Aviation (Air Travel Organisers' Licensing) Regulations 2012, as amended. Read 13 November 2026. |
| PCI DSS, as an accreditation condition | IATA's PCI DSS page states that IATA Accredited Travel Agents now need to become PCI DSS compliant. Holding cardholder data pulls the platform into that scope, and travel authorises early and captures late. | IATA names no version and no deadline there. Read 13 November 2026. |
We are not an IATA accreditation body and not your consumer law adviser. We encode the policy you were given and store the version in force at the sale. See how we build agents that handle change requests without a queue.
Transparency
We publish the hours, with the arithmetic, so you can argue with any line. A fixed price follows discovery.
Phase one hours
1,170 to 2,280
Every module at its minimum, through to every maximum.
Typical timeline
3 to 5 months
Plus certification weeks nobody bills or can accelerate.
Worked example
1,580 hours
The eight modules added up, each inside its range.
| Driver | Hours |
|---|---|
| Supplier or channel connectionsThe second is expensive because it forces the abstraction. The fifth is cheap because it exists. | 80 to 200 each |
| Complexity of the rate modelOne flat rate per unit is a different project from seasonal and corporate rates. | High impact |
| Whether you sell packagesComponent level terms and insolvency protection change the booking model. | Adds real scope |
| Payment timingDeposits, balance dates, authorisation held for weeks, partial refunds. | 140 to 280 |
| Certification calendarEach channel's sign-off takes weeks nobody bills. It moves the launch date. | Schedule, not hours |
| Module | Hours |
|---|---|
| Discovery and channel inventory | 60 to 120 |
| Inventory and availability model | 180 to 340 |
| Rate plans and pricing rules | 160 to 300 |
| Booking and order record | 200 to 380 |
| Supplier and channel integration | 180 to 360 |
| Payments, deposits and capture | 140 to 280 |
| Changes, cancellations and refunds | 150 to 300 |
| Reconciliation and reporting | 100 to 200 |
Delivery
Two artifacts bracket the build, both named rather than implied, so you can ask to see either.
Phase 01
Every channel, what it accepts, what it sends back, and where availability is authoritative today. This one usually surprises the operator.
Phase 02
Each connection through its own test environment and sign-off, tracked as a dependency, not folded into a ticket.
Travel software is the set of systems that sell and service a trip: inventory and availability, rate plans, a booking record, payments, and changes and refunds. A booking engine faces the customer. Behind it sit the reservation system, the channel connections and the nightly reconciliation.
There is no single best. A hotel group needs channel parity and a rate plan it can explain. A tour operator needs component level supplier terms and a combined liability. Pick by what breaks in your week.
We publish hours rather than a figure. A phase one across eight modules spans 1,170 hours at every minimum to 2,280 at every maximum, over three to five months, with a worked example of 1,580. Channel connections run 80 to 200 hours each, and certification adds weeks nobody can accelerate.
NDC is IATA's XML standard for exchanging Offers and Orders directly rather than through legacy messaging, and IATA's press release of 7 August 2014 calls Resolution 787 its foundation document. A conference resolution is not a mandate, so keep a legacy path. Neither IATA page we read states a version openly any more. Re-read on 17 November 2026, the NDC download page is a request form and the standards site needs a sign in; on 13 November 2026 they showed 24.4 Schemas from December 2024 and release 26.3 dated 17 September 2026 as the IATA Offer and Order Standard. So ask each partner which version they certified against, get it in writing, and pin it.
The supplier may reissue its own reference, so a booking keyed on it is orphaned the moment a flight or sailing moves. Key on your own identifier, hold theirs as an attribute with history, and store the policy version in force at sale, so entitlement is computed, not argued over.
Under Regulation (EC) No 261/2004 the duty sits with the operating air carrier, and the UK has a parallel set in sterling the CAA calls UK261. If you are not the carrier, your system still has to show the right number and route the claim, which needs distance and the actual arrival delay. We are not your consumer law adviser.
Usually the channel manager you already pay for will do. Keeping dozens of connections certified is commodity work with a permanent cost. What operators lack is an authoritative inventory and a rate model they can edit, and a distribution audit often concludes exactly that.
Three steps with a shape attached to each. You then choose whether we build it, your team does, or your incumbent extends.
Bring your channel list, your rate plan structure, and the last time you oversold.
We establish where availability is authoritative and how many systems hold a copy. That explains most symptoms.
The modules, the hour ranges and the arithmetic, with certification weeks shown as calendar.
Almost every question here resolves to whether one system is authoritative about what you can sell. We establish that, say which rules bind you, and give you the hours.
Real feedback from the people we've proudly partnered with.
Zyneto Global Technologies provided excellent project management and technical expertise throughout the engagement. The team was responsive, collaborative, and adaptive, ensuring the project met our expectations and set a strong foundation for future growth.
We engaged Zyneto to design and develop a custom web platform for Moneteo, aimed at improving project management, data tracking, and collaboration across internal teams and external partners. Their work included full-stack web development, custom modules for workflow automation, API integration, and comprehensive testing.
Overall, their responsiveness and timely deliveries contributed positively to the project's success. The client achieved better data management and quality. The service provider delivered the project on time and ensured prompt responsiveness throughout the engagement. Their innovative approach was outstanding.
Explore further
Inventory, holds, booking record
Search, checkout and the agent console
Traveller and on-property apps
Forecasting and rate advice
Servicing and change requests
Jobs and reconciliation
Transfers, dispatch and capacity
Restaurants and hotel food
Every sector we build for
Forecasting and automation work that applies to booking and distribution systems.