Hotel Booking Platform Stabilization

Stabilizing a Multi-Supplier Hotel Booking Platform Without a Rebuild

Hotel names, images, prices, and cancellation terms were getting lost between three supplier APIs and the booking page. We traced each issue through the existing platform and fixed it where it started, without replacing the application.

Working together since
2024
Hotel supplier APIs stabilized
3
Clutch rating
5.0
SP Travels hotel search results with grouped supplier rates SP Travels hotel search results with grouped supplier rates

Client Overview

Client Story

Travel Pro Hub is a London-based travel platform where customers search and book hotels from multiple suppliers. Founder Simon McEntee has run the business for 4+ years, combining travel consultancy with online hotel booking.

Each search pulls live inventory from WebBeds, TBO, and RateHawk and merges names, images, prices, and cancellation terms into one booking flow. When a supplier returns incomplete or inconsistent data, customers see it as a broken listing, a wrong price, or an unclear refund policy.

Background

Project Background

Our work with Travel Pro Hub started with its original WordPress site, The Hotel Hub. When supplier API and booking issues held that site back, we rebuilt the platform on Lovable with React and Supabase. Once it was live, the founder flagged data issues that were eroding trust in search results. The brief:

Accurate Hotel Content
Correct hotel names, images, descriptions, and maps across every supplier.
Stable Supplier Integrations
WebBeds, TBO, and RateHawk configured correctly for production.
Reliable Rates and Policies
Refundability, cancellation, and rate details preserved all the way to booking.
Full Destination Inventory
No missing hotels and no false “Price on Request” listings.

I’m frustrated that refundable rates aren’t showing properly, and searches for Delhi and Mumbai return only 43 hotels. Some listings appear as placeholders or have no images, and the maps work for certain hotels but not others. It’s making it difficult to trust the results and help customers find the right stay.

Zakir Shaikh Simon McEntee Founder, SP Travels

Discovery

Research & Ideation

Most of the reported problems looked like display bugs. They were data problems. Each one had to be traced from the supplier response to the screen the customer saw.

  • Trace Before Fixing

    We followed each issue through the supplier adapter, data mapping, hotel listing, rate selection, and booking session before changing any code.

  • Let Supplier Data Decide

    Currency, content, and rate details should come from the supplier response, not from hardcoded defaults.

  • Fix the Platform, Keep the Platform

    The application worked. The gaps were in how supplier data moved through it, so a rebuild was not needed.

Design

Designing a Reliable Booking Data Flow

Every hotel result passes through six layers. A gap at any layer shows up later as a missing name, a wrong price, or unclear cancellation terms.

  1. Supplier APIsWebBeds, TBO, RateHawk
  2. AdaptersSupplier-specific handling
  3. Data MappingNames, currency, content
  4. Hotel ListingSearch results and maps
  5. Rate SelectionRoom, price, and policy
  6. Booking SessionExact rate carried to booking

Every fix in this project was made in one of these six layers, at the point where the data went wrong.

Challenges

Project Challenges

  1. WebBeds Hotels Showed Placeholder Names

    Some WebBeds listings displayed placeholder data instead of real hotel names, making properties hard to identify.

  2. WebBeds Currency Was Hardcoded

    The integration assumed GBP, risking prices shown in the wrong currency for international inventory.

  3. Duplicate TBO Mapper Logic

    Two overlapping mapper paths transformed the same data, so results could differ depending on the path used.

  4. Booking Page Used Fallback Rate Data

    The booking page relied on default values instead of the exact rate selected, so refundability and cancellation details were unreliable.

  5. Incomplete RateHawk Hotel Content

    Some RateHawk records were missing country and description fields.

  6. Listings Without Names or Images

    Placeholder names and missing images made search results look incomplete.

  7. Low Inventory in Delhi and Mumbai

    Searches for both cities returned only around 43 hotels, and some hotels showed “Price on Request” instead of a price.

  8. Inconsistent Hotel Maps

    Maps worked for some hotels and failed for others because location data was handled differently across supplier records.

Approach

Our Solutions

We treated Travel Pro Hub as a stabilization project. Instead of replacing the application, we fixed each issue in the layer where it started.

  • Accurate WebBeds Hotel Names

    Corrected data mapping shows real hotel names whenever the supplier provides them.

  • Supplier-Driven Currency

    Prices now follow the supplier’s currency instead of a fixed GBP value.

  • Complete RateHawk Listings

    The adapter now fills in country and description for more consistent hotel pages.

  • Consistent Images and Content

    Supplier hotel content is handled the same way across results, removing placeholder listings.

  • Delhi and Mumbai Search Fixes

    The Delhi availability issue was fixed, and Mumbai hotels with missing names now display with a clear identifier.

  • Reliable Hotel Maps

    Location data is now handled consistently, so maps work across hotel records.

Implementation Timeline

  1. Issue Analysis
  2. Supplier Integration Review
  3. Data Mapping Improvements
  4. Booking Flow Validation
  5. Destination & Pricing Testing
  6. Code Cleanup

Custom Features

Custom Functionalities

Under the hood, these changes make the supplier integrations predictable and easier to maintain.

  • Structured Name Fallback

    When a WebBeds hotel name is missing, the system shows Hotel WB-{hotelCode} instead of a bare numeric ID, which also avoids conflicts with numeric-name validation.

  • Consolidated TBO Mapper

    Two overlapping mapper paths became one: less duplicated code, predictable data transformation, and easier maintenance.

  • Rate-Level Booking Session

    The session now keeps refundable, cancellation_deadline, and pay_later_eligible for the exact rate the customer selected.

  • Production Supplier Review

    A dedicated review phase checked that each supplier API was configured correctly for production.

Support

On Going Support

Travel Pro Hub has worked with iCommuneTech since May 2024, from the original WordPress site to the platform it runs today.

  • One Team, Every Stage

    We built The Hotel Hub, rebuilt the platform, and stabilized it, so every fix starts with full context.

  • 19 Five-Star Repeat Projects

    The founder has rated every completed project 5.0, across API integrations and platform work.

  • Fast Issue Resolution

    Reported issues are investigated, fixed, and followed with suggested improvements.

It has been great working with you which is evident by my continued work with iCommuneTech.

Zakir Shaikh Simon McEntee Founder, SP Travels

Impact

Project Outcome

Reported issues resolved across search and booking
8
Hotel supplier APIs stabilized
3
TBO mapper paths consolidated
2 → 1
Rate details now carried to booking
3

The client also rated error reduction, processing time, and customer satisfaction as significantly improved in post-project feedback.

Search results now show real hotel names, images, descriptions, and working maps across WebBeds, TBO, and RateHawk. Prices follow the supplier’s currency, and the booking page carries the exact rate the customer chose, including refundability and cancellation deadline.

The Delhi inventory issue is resolved, and one TBO mapper replaces two, so the integration is easier to maintain and no longer returns different results by code path.

Driver safety compliance ecosystem Driver safety compliance ecosystem

How iCommuneTech Works

Understand first. Build exactly what’s needed. Stay for the long run.

We deliver the exact solution to a business problem with the least investment and time, then stay to keep it working.

  1. We understand before we quote

    We start by understanding how the work actually gets done, before we propose anything.

  2. The exact solution, not the biggest one

    We recommend the smallest solution that fully solves the problem, and use what already works.

  3. A team that stays

    Every launch includes a 90-day warranty, then an optional long-term delivery plan with the same team.

Problem Slowing Business Growth? Let’s Find the Exact Fix.

Tell us how the work gets done today. We’ll map it before we propose anything.

Connect on WhatsApp+91 97256 00878

Share your requirementsenquiry@icommunetech.com

India (Head Office)A-1108, Sun Westbank, Ashram Road, Ahmedabad-09.
USA8939 S Sepulveda Blvd, Los Angeles, CA 90045, USA.