Finding 01
Journey step overload
Too many decision points made the booking path feel heavy.
How customers felt it
Each screen asked for another choice before the booking could move on.
Client success story
Tunin Travel: a simpler customer journey from search to booking confirmation
An online travel brand in North Africa cleaned up the path its customers take to book, with fewer decision points, one consistent page logic and a lighter flow on phones.
- North Africa
- B2C
- Customer journey cleanup
- Launched in 2024
The brief
The Tunin Travel success story in short
Tunin Travel sells travel online, directly to travellers in North Africa. Its customers search, choose and pay on their own, so every extra step between the first search and the booking confirmation is a place where they can hesitate.
The project, launched in 2024, was a customer journey cleanup: take the booking path customers already had, remove the friction from it and make it work properly on a phone. The goal was booking completion quality, not a new look for its own sake.
The work was done on the Platform overview, the same booking core you can try in the Live demo.
Journey passLaunched
From
Search
To
Booking confirmation
- Client
- Tunin Travel
- Industry
- Online travel services
- Region
- North Africa
- Model
- B2C
- Scope
- Customer journey cleanup
Launch
2024
Stack
PHPMySQLJavaScript
What got in the way
Three points of friction in the booking journey
Tunin Travel named three problems. None of them was a missing feature; each one made booking feel harder than it needed to be.
The B2C booking path
- 01Search
- 02Results
- 03Traveller details
- 04Payment
- 05Confirmation
Finding 02
Inconsistent page logic
Different page patterns reduced user confidence during booking.
How customers felt it
Pages worked a little differently from one another, so customers had to relearn the layout as they went.
Finding 03
Weak mobile handling
Mobile users needed a clearer and lighter interaction flow.
How customers felt it
On a phone, the same path took more effort than it should have.
The path above is the general shape of a B2C booking; the findings are as Tunin Travel described them.
The cleanup
One clear step at a time, built for the phone
The cleanup followed three principles, each one answering a finding. Tap through the steps to see how they shape a mobile booking path.
Cleanup principles
- One main decision per screenFinding 01Each step asks for one thing and offers one primary action, so the path no longer feels heavy.
- The same page logic on every stepFinding 02Header, progress and the main button stay in the same place from search to confirmation.
- Touch-first controlsFinding 03Large tap targets and a main button within thumb reach make the flow lighter on a phone.
Native apps for the same booking core are covered on the Mobile apps page.
Step 1 of 4
Where are you going?
Search
Step 2 of 4
Pick one option
Selected
Choose this option
Step 3 of 4
Who is travelling?
Continue to payment
Step 4 of 4
Booking confirmed
View booking
Consistent page logic
The same pattern on every page of the journey
Inconsistent page logic cost customers confidence. The answer is a page pattern that repeats, so a customer always knows where to look next.
| Page element | Search | Results | Traveller details | Payment | Confirmation |
|---|---|---|---|---|---|
| Step indicator | Present | Present | Present | Present | Present |
| Trip summary | Not needed | Present | Present | Present | Present |
| Price shown the same way | Not needed | Present | Present | Present | Present |
| One primary button | Present | Present | Present | Present | Present |
| Way back to the previous step | Not needed | Present | Present | Present | Not needed |
- 01 Search
- 02 Results
- 03 Traveller details
- 04 Payment
- 05 Confirmation
An illustration of a consistent page pattern. PHPTRAVELS pages are built from shared Themes and can be adjusted through Customization.
The outcome
Tunin Travel results: a clearer route to confirmation
Tunin Travel reported three results, in its own words. No figures were published for this project.
The platform now gives our customers a clearer route from search to booking confirmation.
Booking confirmationProject
tunintravel · 2024Confirmed- Journey simplicityCleaner booking path
- Touch experienceBetter mobile flow
- Booking qualityStronger completion confidence
Results as reported by Tunin Travel.
Under the hood
Built on PHP, MySQL and JavaScript
The cleaned-up journey runs on the standard PHPTRAVELS stack. PHPTRAVELS is self-hosted and ships with its source code under a commercial licence, so a travel brand can keep refining its booking path after launch.
- 01
PHPServer logic and page rendering - 02
MySQLBookings, customers and content data - 03
JavaScriptInteractive steps in the browser
Simplify your booking journey
Reduce friction and improve user confidence across your funnel.
Related solutions
Questions
Tunin Travel project FAQ
Short answers about the project, what changed for customers and what it takes to run a similar cleanup.
Talk to salesIt describes how Tunin Travel, a B2C online travel brand in North Africa, cleaned up its customer journey on PHPTRAVELS to reduce friction and improve booking completion quality.
Three: too many decision points that made the booking path feel heavy, page patterns that differed from one page to the next, and a mobile flow that needed to be clearer and lighter.
Tunin Travel reported a better mobile flow. The cleanup aimed at a clearer, lighter interaction path for mobile users, with one main action per step.
A cleaner booking path, a better mobile flow and stronger completion confidence. The results were described in the client's own words; no figures were published for the project.
It launched in 2024 and runs on PHP, MySQL and JavaScript, the standard PHPTRAVELS stack. PHPTRAVELS is self-hosted and includes the source code under a commercial licence.
Yes. Book a demo to walk through your current booking path with the team, then compare the one-time plans on the pricing page: Startup, Agency and Enterprise.
Keep exploring