Travel software development for operators and distributors

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.

  • IATA NDC and ONE Order
  • GDS, channel manager and ARI
  • Package Travel and passenger rights
  • Phase one 1,170 to 2,280 hours
What this involves

Tell us what you are building

By submitting this form, I authorize Zyneto to collect and process my personal data in accordance with theZyneto Privacy Policy.

We reply to every enquiry within one business day.

What does travel software development cover?

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.

Phase one hours
1,170 to 2,280
Worked example
1,580 hours
Timeline
3 to 5 months
Each channel
80 to 200 hours

By operation

What is the best software for the travel industry?

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.

Hotels and groups

Channel parity, overbooking, and a rate plan matrix that grew until nobody can explain a price.

Tour operators

Several suppliers with different cancellation terms, a combined liability modelled nowhere, and margin discovered after the season.

Online travel agencies

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.

Airlines and air distribution

One booking exists as a passenger name record, an e-ticket and miscellaneous documents, so ancillaries reconcile separately.

Activities and attractions

Timed slots, per person rules and last minute capacity make availability a per minute question.

The booking

How a booking works, and why it lives in several records

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.

RecordWhat it holdsWhat it means for the build
Passenger name recordThe 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 EMDThe 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 OrderOne 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

Where inventory and rates come from

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.

LayerWhat it isThe constraint that decides the plan
GDSAmadeus, 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 NDCThe 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 StandardRead 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 pushThe 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 messagingOpenTravel'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

Which rules apply to you

Six instruments, each with the date it applies from, the page it was read on and the date it was last read.

InstrumentWhat it forces the software to doApplies from
Regulation (EC) No 261/2004Article 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.
UK261The 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 TravelArticle 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/1024The 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 certificatesThe 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 conditionIATA'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

How much does it cost to develop a travel app? Here are the hours, module by module

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.

What moves the hours, ranked
DriverHours
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
Hours by module
ModuleHours
Discovery and channel inventory60 to 120
Inventory and availability model180 to 340
Rate plans and pricing rules160 to 300
Booking and order record200 to 380
Supplier and channel integration180 to 360
Payments, deposits and capture140 to 280
Changes, cancellations and refunds150 to 300
Reconciliation and reporting100 to 200

Phase one, added up

  • Discovery 90 plus inventory 240 plus rate plans 210 plus booking record 270 plus supplier integration 250 plus payments 190 plus refunds 200 plus reconciliation 130 equals 1,580 hours, each inside its own range above.
  • The full span is 1,170 at every minimum to 2,280 at every maximum, over three to five months, and certification moves the date without moving the hours. Outside it on purpose: loyalty, dynamic packaging, a native app, and any IATA accreditation fee, which belongs to a body rather than to us.

Delivery

How we deliver travel software development

Two artifacts bracket the build, both named rather than implied, so you can ask to see either.

  1. Phase 01

    Distribution map

    Every channel, what it accepts, what it sends back, and where availability is authoritative today. This one usually surprises the operator.

  2. Phase 02

    Channel certification

    Each connection through its own test environment and sign-off, tracked as a dependency, not folded into a ticket.

Frequently Asked Questions

What is travel software?

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.

What is the best software for the travel industry?

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.

How much does it cost to develop a travel app?

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.

What is IATA NDC, and do we need it?

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.

What happens to a booking when the schedule changes?

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.

Who owes a passenger compensation, and does our system have to work it out?

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.

Do we need our own GDS connection, or will a channel manager do?

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.

What happens next

Three steps with a shape attached to each. You then choose whether we build it, your team does, or your incumbent extends.

  1. A 30 minute technical call

    Bring your channel list, your rate plan structure, and the last time you oversold.

  2. The availability question

    We establish where availability is authoritative and how many systems hold a copy. That explains most symptoms.

  3. A written scope within a week

    The modules, the hour ranges and the arithmetic, with certification weeks shown as calendar.

Start with inventory, not the search screen

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.

Our Success Stories

Real feedback from the people we've proudly partnered with.

Brooklyn Foster profile

Brooklyn Foster

Sales Director |Cintas

United States

GoodFirms
"

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.

"
Verified Review
Rating: 5 out of 5
Krystian Chlebek profile

Krystian Chlebek

Founder & CEO |Moneteo

TechBehemoths
"

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.

"
Verified Review
Rating: 5 out of 5
Kevin Scott profile

Kevin Scott

CEO |E-Commerce Platform

Clutch
"

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.

"
Verified Review
Rating: 5 out of 5

Explore further

Go deeper

Build the system

Adjacent capabilities

Other sectors

WhatsApp
Email
Book a Meeting