Qalandar

Choosing a tour is the start of the journey

Qalandar organises experience-led tours around the world. Travellers choose a programme and departure date, but the administration continues after they apply. Participant details need to be completed, a deposit and remaining balance paid, and the office needs to keep track of the booking throughout.

I worked on the system connecting those steps. The scope extended from the public tour pages to the office's daily work. What a visitor reads, what an applicant submits and what a member of staff handles later all need to belong to the same trip.

From a programme to an application

On the public Qalandar website, programmes, photographs and practical information help visitors choose a tour. The application is connected to the selected departure. Once someone has found the trip they want, the next step is part of the same journey.

The person making an application may be arranging travel for several people. Contact details and participant details therefore serve different purposes. The system keeps the travellers connected to the booking so that the office can continue working with the same application as preparations progress.

Customers can return to their booking

The customer account provides a place for the steps that follow an application. Travellers can return to their booking, review its information and see their payment position. That matters when there are still details to complete before departure.

We designed the account as a continuation of the booking journey, including later information and outstanding tasks. A submitted form alone would leave the rest of the process to separate conversations. Giving customers a place to return to keeps the trip understandable after the initial confirmation.

Tracking the balance as well as the payment

A trip may be paid for in stages. The system connects payments and the remaining balance to the application. Customers need to know what has been settled and what remains to be done, and the office needs to be able to give them the same answer.

Office administration brings together applications, participants and their payment position. The public website and the booking records are parts of one workflow, so a member of staff can continue handling the application as the trip approaches.

Continuing existing trips through the transition

The new Qalandar system went live on October 22, 2026. Preserving existing applications and user data was part of the transition. Preparations for an upcoming trip could not start again just because the software had changed.

If you run a travel business, use your everyday cases to assess a potential system. Who supplies participant details? Who pays? What can a customer see, and how does a colleague identify the next task? An existing booking product may cover that workflow well; custom development is not worthwhile simply to put your logo on it. Where separate records still carry essential parts of the work, our business software services can help connect the process.

For another example of continuing an existing service through a development handover, read about the Assisto marketplace.