Live demo

Client success story

Tazkira success story: B2B flight operations refined for faster agency work

Tazkira distributes flights to travel agencies in the Middle East. The project tightened three things its agency teams use every day: the ticketing path, the wallet and the fare rules.

  • Middle East
  • B2B flights
  • Agency platform optimisation
  • Launched in 2024

In brief

The Tazkira success story in one page

Tazkira works in B2B flight distribution: travel agencies book flights through its platform, and its own teams look after ticketing, agency credit and pricing behind the scenes.

The project was not a new build. It was an agency platform optimisation with a clear aim: cleaner fare control, clearer wallet operations and a faster booking path for the agencies and the staff who support them.

The work sits on the same Flights that powers every PHPTRAVELS install, run as a B2B travel portal for agency partners.

Project ticketLaunched
ClientTazkiraLaunch2024
Industry
B2B flight distribution
Region
Middle East
Model
B2B flights
Scope
Agency platform optimisation
Websitetazkira.ae
StackREST APIPHP 8.xMySQL

The operations console

Three workstreams behind every agency booking

Pick a workstream to see the challenge Tazkira named, what the project changed and the result the team reported.

Challenge

Slow agency booking cycles

Approval-heavy steps delayed regular ticketing operations.

What changed

The booking path was shortened so routine agency bookings move from search to ticket in fewer, clearer steps, with the pricing and credit checks run by the platform as part of the path.

Agency throughputQuicker ticketing
Agency booking pathIllustrative
  1. 01Search and choose a fareThe agent searches and picks the flight.Agent
  2. 02Apply agency pricingMarkup and policy rules are applied.Platform
  3. 03Pay from the agency walletAvailable credit is checked and held.Platform
  4. 04Issue the ticketThe booking is ticketed and confirmed.Agent

Challenge

Wallet process complexity

Credit handling needed clearer controls for daily use.

What changed

Credit handling was reorganised around the B2B agent wallet, so every top-up, hold, deduction and refund follows one visible flow that the finance desk and the agency read the same way.

Credit operationsClearer wallet flow
Agency wallet flowIllustrative
  1. Top-upCredit inThe agency adds funds or receives credit.
  2. Available creditHeldOne balance the agency and finance both see.
  3. Booking holdHeldCredit is reserved while a booking is in progress.
  4. Deducted at ticketingCredit outThe hold becomes a charge when the ticket is issued.
  5. RefundCredit inCancelled or refunded tickets return credit to the wallet.

Challenge

Fare rule visibility gaps

Teams required cleaner markup and policy management views.

What changed

Markups and pricing policies were brought into one rule view, so the team can see which rule applies, at what scope, and whether it is live before a fare reaches an agency.

Pricing governanceBetter rule control
Fare rule viewIllustrative
ScopeRuleState
AirlinePercentage markupLive
RouteFixed markupLive
Agency groupPricing policyLive
Booking channelService feeIn review

The screens are illustrative views of each workstream on PHPTRAVELS, not Tazkira's live data or settings.

Results

What changed for Tazkira's agency teams

Three outcomes, in the words the client used. No invented percentages, only what the team reported.

Operations status boardLive since 2024
  • TZ-01Agency throughputQuicker ticketingReported
  • TZ-02Credit operationsClearer wallet flowReported
  • TZ-03Pricing governanceBetter rule controlReported

Client note

Our teams now handle agency bookings with less friction and better operational visibility.

Tazkira Management, Leadership Team, Tazkira

Results are the client's own description of the change, as shared with PHPTRAVELS.

The screen

An agency-first flight search

The main screen of the project: flight search built around the agent at the desk rather than a traveller browsing.

Agency staff search all day, so the screen keeps the fields they need in one place and puts the business context next to the trip: which agency is booking, how it pays and which price the agent is looking at. It is the same search core described on the Flight booking software page.

  • A focused search form with the trip, travellers and booking agency together.
  • Payment from the agency wallet sits in the flow, not on a separate screen.
  • A net and gross view, so agents see their cost and the price they quote.
Agency flight searchIllustrative
From
City or airport
To
City or airport
Departure
Choose a date
Travellers
Adults, children, infants
Booking agency
Signed-in agency
Pay with
Agency wallet

Fare view

The supplier fare before the agency's markup, visible to the agent only.

The price the agency quotes to its traveller, with its markup rules applied.

Under the hood

Built on PHP 8.x, MySQL and a REST API

The stack listed in the project file, from the request an agency sends down to where its bookings and balances are stored.

  1. REST APILayer 1The interface agency tools and the booking screens talk to, so searches, bookings and wallet actions go through one documented door.
  2. PHP 8.xLayer 2The application layer where booking steps, wallet movements and fare rules run.
  3. MySQLLayer 3The database that keeps bookings, agency accounts, wallet entries and rules in one place.

Discuss your flight platform

Run B2B flight distribution or an agency network? We can help you streamline ticketing, credit and pricing on a platform you host and own.

Book a strategy callSee pricing

Related pages for B2B flight teams

FAQ

Questions about the Tazkira project

Short answers on what changed, what it ran on and how a similar project starts.

Talk to sales

It is the story of Tazkira, a B2B flight distributor in the Middle East, optimising the agency platform its teams and partner agencies use. The project, launched in 2024, focused on a faster booking path, clearer wallet operations and cleaner fare control.

Three: slow agency booking cycles caused by approval-heavy steps, wallet processes that needed clearer controls for daily credit handling, and gaps in how teams could see and manage markups and pricing policies.

The team reported quicker ticketing for agency throughput, a clearer wallet flow for credit operations and better rule control for pricing governance. In the client's words, teams now handle agency bookings with less friction and better operational visibility.

Each agency has a balance it tops up or receives as credit. When an agent books, the platform holds the amount, deducts it when the ticket is issued and returns it on a refund, so finance and the agency read the same entries.

The project file lists PHP 8.x, MySQL and a REST API. PHPTRAVELS is sold with its source code under a commercial licence and is self-hosted, so the client runs it on its own servers.

Yes. Most projects start with a demo and a strategy call about your booking path, credit rules and pricing. Plans and the one-time licence are explained on the pricing page.

Keep exploring

More from the platform