Back to home

Designing a tour management backoffice for a luxury travel agency

Designing a tour management backoffice for a luxury travel agency

Project Name

Interworld Backoffice

Year

2025

Industry

Tourism

Role

Product Designer

Project Overview

Interworld is an İzmir-based luxury travel agency specializing in cruise, river, and land tours — including ultra-luxury 6-star cruise experiences. The backoffice system I designed serves as the content and operations management platform behind the public-facing website: every tour listing, itinerary, cabin configuration, pricing structure, and booking option visible to customers is created and managed through this system.

THE PROBLEM

Travel agency backoffice systems are notoriously complex. A single cruise tour contains dozens of interdependent data points — departure dates, cabin types, pricing tiers, itinerary stops, port information, gallery images, included and excluded services, and booking options with their own guest and payment configurations. Managing this through spreadsheets or disconnected tools creates errors, inconsistencies, and slow publishing workflows.


Interworld needed a centralized backoffice that allowed their team to create, edit, and publish tour content directly — with the confidence that what they entered would appear correctly on the customer-facing website. The backoffice and the public site share the same data model, so the design of content management screens had to mirror the information architecture of the public tour detail pages.

USERS

Travel agency staff

Travel agency staff

Non-technical users responsible for entering and maintaining tour content. They think in terms of tours, departures, and cabins — not database records or content management conventions. The interface needed to match their mental model of how a tour is structured.

Operations team

Operations team

Operations team

Managing booking options, guest configurations, and payment schedules. They need to see the full picture of a booking — who is coming, when, at what price, and under what conditions — without switching between systems.

Key Insights

Content structure mirrors the public product

The backoffice was designed with the public tour detail page as a direct reference. Every section in the backoffice — tour info, itinerary, images, cabin details, pricing maps to a corresponding section on the customer-facing page. This alignment meant staff could intuitively understand what each field controlled and what it would look like to the end customer.

Multi-section forms need clear navigation

A tour detail page in the backoffice spans five major sections: tour information, itinerary, images, cabin & pricing, and additional details. Rather than presenting everything on a single scrolling page, tab-based navigation between sections reduces overwhelm and allows staff to focus on one content area at a time.

Itinerary management requires spatial thinking

Cruise itineraries are sequential — each stop has a port, a country, arrival and departure times, and optional description. The itinerary section needed to feel like building a route, not filling in a form. Each stop is a discrete editable item within an ordered list, making the sequence visually obvious.

Booking options are operationally complex

Each tour can have multiple booking options, each with its own guest count, cabin type, pricing, and payment schedule. The option detail screen needed to surface all of this in a structured, readable format not a flat form so the operations team could review and manage bookings confidently.

Tour List

The tour list is a standard table view with search, filtering, and pagination. Each row shows tour name, type, date range, and status. A context menu on each row provides quick actions edit, duplicate, archive without requiring navigation to the detail page for simple operations.

Tour List

The tour list is a standard table view with search, filtering, and pagination. Each row shows tour name, type, date range, and status. A context menu on each row provides quick actions edit, duplicate, archive without requiring navigation to the detail page for simple operations.

Tour List

The tour list is a standard table view with search, filtering, and pagination. Each row shows tour name, type, date range, and status. A context menu on each row provides quick actions edit, duplicate, archive without requiring navigation to the detail page for simple operations.

Creating a New Tour

Adding a new tour follows a two-stage flow designed to let staff create a tour record quickly without requiring all content to be ready upfront.

The first stage collects the essential identifying information: tour code, tour name, vessel, start and end dates, concept tags, and a rich text field for important notes. Submitting this form creates the tour in the system but it remains unpublished. The decision to separate creation from publishing was deliberate: staff can open a tour record, begin filling in content across multiple sessions, and only push it live when it's complete.

Once created, the tour moves into its detail view where remaining content is managed across five tabs Tour Info, Itinerary, Capacity & Pricing, Images, and Details. Each tab addresses a distinct content domain, preventing the interface from becoming a single overwhelming form. A "Publish Tour" button in the page header becomes the final action once all content is ready, making the publishing step explicit and intentional rather than automatic.

Creating a New Tour

Adding a new tour follows a two-stage flow designed to let staff create a tour record quickly without requiring all content to be ready upfront.

The first stage collects the essential identifying information: tour code, tour name, vessel, start and end dates, concept tags, and a rich text field for important notes. Submitting this form creates the tour in the system but it remains unpublished. The decision to separate creation from publishing was deliberate: staff can open a tour record, begin filling in content across multiple sessions, and only push it live when it's complete.

Once created, the tour moves into its detail view where remaining content is managed across five tabs Tour Info, Itinerary, Capacity & Pricing, Images, and Details. Each tab addresses a distinct content domain, preventing the interface from becoming a single overwhelming form. A "Publish Tour" button in the page header becomes the final action once all content is ready, making the publishing step explicit and intentional rather than automatic.

Creating a New Tour

Adding a new tour follows a two-stage flow designed to let staff create a tour record quickly without requiring all content to be ready upfront.

The first stage collects the essential identifying information: tour code, tour name, vessel, start and end dates, concept tags, and a rich text field for important notes. Submitting this form creates the tour in the system but it remains unpublished. The decision to separate creation from publishing was deliberate: staff can open a tour record, begin filling in content across multiple sessions, and only push it live when it's complete.

Once created, the tour moves into its detail view where remaining content is managed across five tabs Tour Info, Itinerary, Capacity & Pricing, Images, and Details. Each tab addresses a distinct content domain, preventing the interface from becoming a single overwhelming form. A "Publish Tour" button in the page header becomes the final action once all content is ready, making the publishing step explicit and intentional rather than automatic.

Tour Detail

The tour detail page is the primary content management surface for an existing tour. The page header shows the tour name, a "Publish Tour" primary action, and a secondary overflow menu for additional operations. Tab navigation below the header keeps the user oriented within the content structure at all times.

The Tour Info tab displays all core tour data tour code, name, vessel, dates, and concept tags in a clean label-value list format. An inline "Edit" button opens the same form used during creation, allowing updates without navigating away from the overview. A notes panel on the right side of the layout gives the operations team a space to attach internal context to a tour record — separate from the customer-facing content.

The tab structure Güzergah, Kapasite ve Fiyat, Görseller, Detaylar maps directly to the sections visible on the public-facing tour detail page. This relationship between backoffice and frontend is intentional: staff can understand what each tab controls by referencing the live website, reducing the need for internal documentation or training.

Tour Detail

The tour detail page is the primary content management surface for an existing tour. The page header shows the tour name, a "Publish Tour" primary action, and a secondary overflow menu for additional operations. Tab navigation below the header keeps the user oriented within the content structure at all times.

The Tour Info tab displays all core tour data tour code, name, vessel, dates, and concept tags in a clean label-value list format. An inline "Edit" button opens the same form used during creation, allowing updates without navigating away from the overview. A notes panel on the right side of the layout gives the operations team a space to attach internal context to a tour record — separate from the customer-facing content.

The tab structure Güzergah, Kapasite ve Fiyat, Görseller, Detaylar maps directly to the sections visible on the public-facing tour detail page. This relationship between backoffice and frontend is intentional: staff can understand what each tab controls by referencing the live website, reducing the need for internal documentation or training.

Tour Detail

The tour detail page is the primary content management surface for an existing tour. The page header shows the tour name, a "Publish Tour" primary action, and a secondary overflow menu for additional operations. Tab navigation below the header keeps the user oriented within the content structure at all times.

The Tour Info tab displays all core tour data tour code, name, vessel, dates, and concept tags in a clean label-value list format. An inline "Edit" button opens the same form used during creation, allowing updates without navigating away from the overview. A notes panel on the right side of the layout gives the operations team a space to attach internal context to a tour record — separate from the customer-facing content.

The tab structure Güzergah, Kapasite ve Fiyat, Görseller, Detaylar maps directly to the sections visible on the public-facing tour detail page. This relationship between backoffice and frontend is intentional: staff can understand what each tab controls by referencing the live website, reducing the need for internal documentation or training.

Option List & Option Detail

Tour options represent individual bookable configurations a specific cabin type, guest count, and pricing structure. The option list gives a high-level overview of all available configurations for a tour. The option detail page surfaces the full booking picture: tour summary, guest information (up to 3 guests), cabin details, and a payment schedule all in a structured, readable layout that serves the operations team during booking management.

Option List & Option Detail

Tour options represent individual bookable configurations a specific cabin type, guest count, and pricing structure. The option list gives a high-level overview of all available configurations for a tour. The option detail page surfaces the full booking picture: tour summary, guest information (up to 3 guests), cabin details, and a payment schedule all in a structured, readable layout that serves the operations team during booking management.

Option List & Option Detail

Tour options represent individual bookable configurations a specific cabin type, guest count, and pricing structure. The option list gives a high-level overview of all available configurations for a tour. The option detail page surfaces the full booking picture: tour summary, guest information (up to 3 guests), cabin details, and a payment schedule all in a structured, readable layout that serves the operations team during booking management.

Outcomes

The backoffice system is live and actively used by the Interworld team to manage their full tour catalog — cruise, river, and land tours — across the Turkish market. Content entered through the backoffice populates the public-facing website directly, eliminating the need for manual data transfer or developer involvement in content updates. The system supports the full content lifecycle from tour creation through booking option management.