Travel & hospitality
Nusukway — the whole pilgrimage journey in one booking flow
Nusukway is a travel platform for pilgrims heading to Makkah and Madinah. It brings together the four things that make up the trip — hotel, Umrah package, transport and flight — in one search, one checkout and one itinerary, in Arabic, English or French, priced in SAR, EUR or USD.
The challenge
A pilgrimage is not one booking — it is four
A pilgrim leaving Damascus or Casablanca for Makkah is not making one booking. They are making four: a hotel near the Haram, an Umrah service package, transport from Jeddah, and a return flight. Each of those bookings usually happens on a different site, in a different language, in a currency that may or may not be theirs — and none of them talk to each other about the dates.
The pilgrim's real problem is not finding a hotel or a flight. It is agreeing on dates that work for all four at once.
What we built
One search bar, four verticals, one itinerary
The platform's search is service-specific — hotel search, package search, car search, flight search all have their own fields — but the itinerary that ties them together is shared. A change of dates in one propagates a warning to the others; a checkout that includes multiple verticals produces one confirmation and one printable itinerary. Prices are converted at read time to the pilgrim's chosen currency; every string, holiday date and prayer time reference is localised at the same layer.
Four booking verticals
Hotels, Umrah packages, transport and flights — separate flows, one itinerary.
Trilingual UI
Full Arabic, English and French — with RTL and LTR both first-class citizens in the layout.
Multi-currency
Prices displayed in SAR, EUR or USD; the source of truth stays a single currency behind the scenes.
Editorial content
A news & guides section on Hajj, Umrah and Saudi visa updates lives inside the same CMS as inventory.
Discovery-first landing
Featured destinations, hotels near the Haramain, and seasonal offers guide first-time visitors into the funnel.
Auth for booking history
Google sign-in and email/password, so a returning pilgrim finds last year's trip already in their account.
Under the hood
A platform architecture designed for many small services
- Server-rendered web
- REST APIs
- multi-currency conversion
- trilingual i18n
- CMS-driven content
Because each vertical is independent (a hotel supplier connects differently to a flight GDS), the platform is stitched together at the layer that matters — the itinerary and the checkout — while each vertical keeps its own inventory shape underneath.
Outcome
One evening's worth of tabs, replaced by one confirmation
A pilgrim can now start with a date range and a rough budget and leave with a single confirmed itinerary. The four bookings that used to require four sites, four accounts and four payment attempts are now one flow that speaks their language and their currency.
4 → 1
sites replaced by one search and one checkout
3 langs
EN, AR, FR — each a first-class citizen
3 currencies
SAR, EUR, USD priced at read time
Multi-vertical marketplace with a real i18n story?
The hard part isn't a language toggle. It's the money, the dates and the tone. We plan all three.