---
title: "Hotels.com: Hotel OTA and Expedia Group Retail Profile"
description: "Model Hotels.com as Expedia Group's hotel-first consumer OTA across discovery, retail and booking lifecycle."
slug: "hotels-com"
translationKey: "platform-hotels-com"
locale: "en"
type: "profile"
category: "travel-ecosystem"
tags: ["hotels-com","ota","travel-marketplace"]
platform: "Hotels.com"
domain: "hotels.com"
vertical: ["hotel"]
publishedAt: "2026-09-26"
updatedAt: "2026-09-26"
reviewedAt: "2026-09-26"
technicalVerifiedAt: "2026-09-26"
directory: {"platformType":"ota","roles":["ota","travel-marketplace"],"ecosystemLayers":["retail-discovery","booking-transaction"],"turkeyRelevance":"global-context","status":"active","reviewedAt":"2026-09-26","audiences":["b2c","b2b"],"businessModels":[],"integrationMethods":[],"company":"Expedia Group","directSupplierParticipation":"unknown","developerDocsAvailable":"unknown","sources":[{"title":"Expedia Group — Travel with us","url":"https://expediagroup.com/en-us/travel-with-us"}]}
sources:
  - title: "Expedia Group — Travel with us"
    url: "https://expediagroup.com/en-us/travel-with-us"
---
Hotels.com is a hotel-first consumer travel brand within Expedia Group. Expedia Group's official brand surface positions Hotels.com as a lodging-focused retail brand, so it should not be treated as the same technical product as Expedia or Expedia Rapid.

## Ecosystem role

Its primary role is OTA / travel marketplace. Travelers use the consumer surface for hotel discovery, offer comparison and a significant portion of the booking journey.

## Expedia Group relationship

Shared corporate ownership does not mean Expedia, Hotels.com and Rapid have identical booking contracts. Brand identity, booking owner and underlying supply source should remain separate.

## Technical modeling

Preserve property, room/rate, seller, payment timing, cancellation and source references in the canonical offer. Consumer brand identity should not replace supplier identity.

## Failure modes

Price mismatch, policy differences, stale availability and landing/booking state divergence should be tracked as separate incident classes.