Skip to content

Booking software

Ticketing and booking software development

Booking should take a passenger seconds, while operators keep full control of inventory and fares. I design ticketing systems across mobile, agent counters, kiosks and ticket checkers.

Sannan Malik designs ticketing and booking software for transport and events: journey search, availability, seat selection, booking workflows, passenger management, ticket administration, agent counters, kiosks and ticket checking, across mobile and web. He led product design and the mobile experience for a railway ticketing platform. Each system is quoted individually after scoping.

Prefer email? Send a message

Why work with me on Ticketing & Booking Software

01

Seat-level inventory

Availability and seat selection kept consistent across every channel.

02

Every touchpoint

Passenger app, agent counter, kiosk and checker interfaces from one system.

03

Operator reporting

Sales, occupancy and agent performance at a glance.

One seat inventory, many sales channels

The hard part of ticketing is not the booking screen. It is making sure a seat sold on the app cannot also be sold at a counter or kiosk a second later. Every channel has to read and lock the same inventory, and a seat held during checkout has to be released cleanly if payment fails or the passenger walks away.

That inventory model is designed first. Fares, seat classes, quotas for agents and cancellation rules sit on top of it.

The same model works whether the inventory is a train seat, a bus seat, a ferry place or a numbered seat at a venue. What changes is the shape of the journey: a train has many stops, so one seat can be sold several times on different legs of the same trip, while an event seat is sold once.

The interfaces a ticketing system needs

Most operators need more than a passenger app. These are the touchpoints I scope, each built around a different user:

  • Passenger app on Android and iOS: search, availability, seat selection, booking and tickets.
  • Agent interface for counters and resellers, with sales tracked per agent.
  • Kiosk interface for self-service sales in stations or venues.
  • Ticket checking for staff on board or at the gate.
  • Ticket administration and passenger management for the operator.
  • Administrative reporting on sales, occupancy and channels.

Design work on a railway ticketing platform

On the Railway Ticketing Platform my role was product design and the mobile experience. The platform covers Android and iOS app design, journey search, train availability, seat selection, booking workflows, passenger management, ticket administration, agent interfaces, ticket checking, kiosk interfaces and reporting. Designing the passenger journey and the staff workflows together is what keeps the channels consistent.

Payments, peaks and getting started

Payment gateways, refunds and the providers you are allowed to use differ by country, so they are confirmed during scoping. Peak days such as holidays are planned for in the inventory locking and tested against the traffic you expect.

A first phase is often the passenger booking flow and operator administration, with agents, kiosks and checking added after. Each phase is quoted at a fixed price with a written scope.

What's included

Everything from scope to launch.

  • Journey search
  • Seat selection
  • Booking & payments
  • Agent interfaces
  • Kiosk UI
  • Ticket checking

Technology

  • Flutter
  • Next.js
  • Node.js
  • PostgreSQL

Pricing

A fixed quote, agreed before work starts.

Every ticketing & booking software project is different, so I quote it individually after a short scoping conversation. You get a written scope, a timeline and one price.

How it works

How it works: Ticketing & Booking Software

  1. 01

    Scope

    We agree goals, users, screens and the riskiest unknowns, written down with a fixed price.

  2. 02

    Design

    Flows and high-fidelity screens, reviewed with you in short loops before development.

  3. 03

    Build

    Regular working builds you can try on your own devices, not just screenshots.

  4. 04

    Launch

    Deployment, store submission help and a handover so your team owns what was built.

Senior from start to finish

You work directly with a senior architect and certified product owner, not a junior after the sales call.

Design and engineering together

The person who designs your product also architects it, so nothing is lost in handoff.

The price is agreed first

Scope and price are written down before work starts. Changes are agreed before they're built.

FAQ

Ticketing & Booking Software: your questions

Ask me directly
Can it handle peak demand?

Inventory locking and capacity planning are designed for peaks and load-tested for your expected traffic.

Does it work for buses and events too?

The same patterns apply to buses, ferries and event seating.

Can tickets be checked offline?

Offline-capable checking can be designed for areas with poor connectivity.

Guides

Further reading: Ticketing & Booking Software

Let's build it

Got an idea? Let's talk.

The fastest way to reach me is WhatsApp. Tell me what you're building and I'll reply with how I'd approach it, which package fits, or what a custom scope would look like.

Message me on WhatsApp