Solutions
Every module an airline runs on.
18 modules on one platform, from the first schedule to the last bag tag.
Product screens shown with sample data.
Modules
The modules behind every flight.
- Sell
Reservations and PNR
Bookings with every detail an airline needs.
A booking holds passengers, segments, contacts, special service requests and remarks. Unpaid bookings are cancelled when the ticket time limit passes. A sold-out class takes a waitlist that clears in order when seats return, and queues bring time limits and schedule changes to the agent.
- SSR and OSI
- Ticket time limit with auto-cancel
- Split and merge
- Through segments
- Sell
Inventory
Seats sold and released in one atomic step.
Each departure has its cabins, booking classes and authorizations. Overbooking is set per departure. A sale takes its seat in the same step that writes the booking, so two agents never sell the last seat twice.
- Booking classes
- Authorizations
- Overbooking
- Availability 0 to 9
- Sell
Fares and taxes
Fares, rules and taxes priced into a stored quote.
One-way and round-trip fares by market, class and passenger type, with rules for combining them on open-jaw and circle trips. Taxes are set per station as a fixed amount or a percentage. The quoted price is stored with the booking.
- Advance purchase
- Minimum and maximum stay
- Change and refund fees
- Round trips
- Sell
Ticketing and EMD
E-tickets from issue to exchange.
One e-ticket per passenger and one coupon per segment, from controlled ticket stock. A same-day void reopens the booking. A refund returns unused coupons less the fees, and an exchange carries the residual value to the new ticket.
- Coupons
- Void and refund
- Exchange with residual value
- EMD-A and EMD-S
- Sell
Ancillaries
Bags, seats, meals and priority, sold with the ticket.
The airline builds its own catalogue of extras with industry codes. Staff sell an extra to one passenger on one segment, and an EMD is issued for it. The same catalogue is offered through the booking API.
- RFIC and RFISC catalogue
- Per passenger and segment
- EMD issued
- Offered on the website
- Sell
Payments
Counter tenders and online gateways in one ledger.
Offices take cash, bank transfers and wallet payments. Online gateways connect through one adapter per acquirer, and a captured payment issues the tickets. The airline sets a daily exchange rate between its currencies.
- Cash, bank transfer, wallet
- Gateway adapters, signed callbacks
- Refunds
- Daily exchange rates
- Sell
Agent portal
Travel agents book on their own account.
Each agency has its deposit, credit limit and commission. Agency staff see and change only their own bookings. Every movement is a line in a ledger that cannot be edited, with statements to download.
- Deposits
- Credit limits
- Commission
- Ledger
- Sell
Public booking API
The airline’s website and apps book directly.
The airline’s website and apps search flights, price, hold, take payment, retrieve and cancel through a documented API. Each channel has its own key and its own caps on unpaid bookings and on seats per flight.
- Key per channel, stored hashed
- Caps and rate limits
- Extras and payment
- Web check-in
- Sell
Groups, Hajj and Umrah
Large parties from request to bookings.
A group starts as a request and gets a quote. On confirmation its seats are blocked in one step. Deposits and name lists have deadlines the system follows, and a complete name list becomes ordinary bookings.
- Requests and quotes
- Held blocks
- Deposits
- Name lists
- Fly
Check-in and boarding
Departure control from counter to gate.
Open the flight, check passengers in with seats, bags and travel documents, print boarding passes and bag tags, board at the gate and close the flight. The counter keeps working without a connection and sends its work when the line returns.
- Seat map
- BCBP boarding passes
- Bags with licence-plate tags
- PAXLST D02B
- Flight close
- Fly
Web check-in
Passengers check in from their phones.
Passengers open their booking with the locator and last name, enter travel documents, choose a seat and receive the boarding pass. The airline sets the check-in window and which passengers must go to the counter.
- Retrieve by locator
- Seat choice
- Travel documents
- Boarding passes
- Fly
Load control
Weight and balance for every departure.
Weight and balance data is kept per aircraft registration. The load plan of a departure is built from checked-in passengers and bags, with cargo and mail added by hand. The system checks limits and the centre-of-gravity envelope and prints numbered editions of the load sheet.
- Load plan from check-in
- Cargo and mail
- Trim and envelope checks
- AHM 517 load sheet
- LDM and CPM
- Fly
Disruption (IROPS)
Retime, reaccommodate and tell every passenger.
One retime moves a flight with its bookings and coupons. Broken connections are listed. The bookings of a cancelled flight move to another flight in the same class, and every passenger gets a notice in Arabic and English.
- Retime
- Reaccommodation
- SMS and WhatsApp
- E-mail notices
- Control
Loyalty
A frequent flyer programme built in.
Members earn miles on flown coupons and move through tiers. Miles pay for award bookings and expire by the programme’s rule. Every movement is kept in a ledger.
- Tiers
- Accrual
- Awards
- Expiry
- Control
Revenue management
Forecasts and controls on every departure.
Booking snapshots feed a pickup forecast for each departure. The system recommends seats per class and an overbooking level from past no-shows. An analyst accepts, edits or rejects a recommendation, or lets a route apply it automatically.
- Pickup forecast
- EMSR-b
- Bid prices
- O&D control
- Control
Reports
Sales, coupons and loads, ready to export.
Sales per day and currency in UTC or the station’s time zone, coupon status per flight and seats per cabin with load factor, each with a comparison to the period before and a CSV export.
- Sales
- Coupon status
- Load factor
- CSV export
- Control
BSP and ARC settlement
Agency sales reconciled against your own tickets.
For airlines whose agencies sell through BSP or ARC: billing periods and remittance dates per plan, sales files imported and checked record by record, and differences turned into agency debit or credit memos.
- Billing periods
- HOT file import
- Discrepancies
- ADM and ACM
- Control
Audit trail
Every change to every record, kept.
Every change is recorded with the user, the time and the values before and after. The record can be added to and never edited.
- Actor and time
- Before and after
- Append only
Sales channels
Every way your airline sells, on one inventory.
A seat sold at a city office is gone from the website in the same moment. No channel keeps its own copy of the flight.
Sales offices
Staff search, price, book and ticket on one screen, and take cash, bank transfers and wallets.
Travel agencies
Agents book on their own account against a deposit or a credit limit, and see only their own bookings.
Website and apps
Your own website sells through the public booking API, with extras, payment and web check-in.
Group desk
Hajj, Umrah and other large parties, from request and quote to name list and bookings.
At the airport
Counter and gate sell extras, reissue tickets and rebook passengers on the day of the flight.
Platform
The platform underneath.
Cloud
Runs in the browser. Nothing to install at the counter or the gate.
One tenant per airline
Each airline has its own data, settings, staff and roles.
Contract first
Every feature starts as a documented OpenAPI contract, the public booking API included.
Offline at the airport
Check-in holds the passenger list and seat plan on the device and replays its work in order when the connection returns.
Three languages
Every screen in Arabic, English and German, right to left where the language asks for it.
Integrations
Speaks the industry’s formats.
- 1
Payment gateways
One adapter per acquirer, with signed callbacks and refunds.
- 2
SMS and WhatsApp
Passenger notices through Twilio, e-mail through Resend.
- 3
PAXLST and APIS
UN/EDIFACT PAXLST D02B for each flight.
- 4
SSIM
IATA schedule import and export, with a dry run.
- 5
BCBP
IATA bar-coded boarding passes as QR codes.
- 6
Ancillaries
Extras coded with RFIC and RFISC.
- 7
Load sheet
AHM 517 load sheet with LDM and CPM messages.
- 8
BSP and ARC
Sales files imported and reconciled with tickets and EMDs.
- 9
OpenAPI
Every endpoint documented, the public booking API included.
Security and hosting
Who gets in, what they may do, and where the data lives.
The questions an airline’s IT team asks first, answered before the demo.
Single sign-on only
Staff sign in through the identity provider, with multi-factor authentication set there. ZoolAir stores no staff passwords.
Permission per action
Every screen and action has its own permission. The airline builds its own roles next to the built-in ones.
Keys stored hashed
Website and device keys are shown once and kept only as a hash. A lost key is replaced, never recovered.
Limits against abuse
Rate limits per channel and per traveller, and caps on unpaid bookings and on seats held per flight.
One tenant per airline
Each airline’s data, staff, roles and settings are kept apart from every other airline on the platform.
Hosting your way
We host the platform in the cloud. It can also run in your own country or your own data centre.
Roadmap
Planned, and labelled as planned.
These are not built yet. We will not sell them as if they were.
- Roadmap NDC
- Roadmap GDS distribution
- Roadmap Interline and codeshare
- Roadmap ATPCO fare filing
- Roadmap Kiosk and CUPPS
- Roadmap Revenue accounting
See your airline on ZoolAir.
A walk-through with your stations, your schedule and your fares, in Arabic or English.