# Hotel mapping solutions for bedbanks and wholesalers

> URL: https://hotelmapping.org/en/solutions/hotel-mapping-solutions-for-bedbanks-and-wholesalers/ · Language: English

Bedbanks and wholesalers collect hotels from many sources and sell this inventory to agencies. hotelmapping.org merges duplicate records across sources under a single HM ID, breaks room names into standard tags and delivers the result via API and daily dump. Your customers use a clean inventory directly.

## Problems you face

- **Duplicate hotels across sources:** The same hotel coming from direct contracts, sub-suppliers and other wholesalers sits in the inventory as multiple records. Duplicate records pass straight through to agencies' listings as well.
- **Customers expect clean, persistent IDs:** Agencies link the code they get from a bedbank to their own mapping. If a code changes or the same hotel arrives with two codes, the customer's mapping breaks and a support ticket is opened.
- **Room names vary by source:** The same room arrives as "Superior Double Sea View" in one source and "SUP DBL SV" in another. Without room-level grouping, customers mistake the same room for different products.

## Recommended package: Hotel + room mapping and dump; code history planned

Hotel mapping gathers the inventory under a single HM ID; room mapping breaks room names into tags. Results are delivered as daily full and delta dumps. Code change history (closed and merged hotels) is planned as a separate product.

- [Hotel mapping solutions](https://hotelmapping.org/en/products/hotel-mapping-solutions/)
- [Room mapping solutions](https://hotelmapping.org/en/products/room-mapping-solutions/)

## Sample flow

1. **Ingesting source data:** Each source's static hotel data is received via API, CSV or FTP. Raw records are stored and changes are versioned.
2. **Duplicate cleanup:** Records across sources that fall on the same hotel merge under a single HM ID. If two codes from the same source fall on the same hotel, the record goes to the conflict queue.
3. **Room grouping:** Room names are broken into type, class, view, bed and capacity tags; different names for the same room are gathered in a single group.
4. **Delivery to customers:** Your inventory is prepared as daily full and delta dumps (CSV, JSON, Parquet), with the HM ID, your supplier codes and, where available, cross-references to external hotel IDs.

## Why is mapping different for a bedbank?

A [bedbank](https://hotelmapping.org/en/glossary/bedbank/) is both a user and a source of mapping. You combine your directly contracted hotels, inventory from sub-suppliers and the records of other wholesalers in a single catalog; then you sell this catalog to agencies. Every duplicate record in the catalog passes through to your customer's listing as well. For the general framework, see the [what is hotel mapping](https://hotelmapping.org/en/guide/what-is-hotel-mapping/) guide.

[Hotel mapping](https://hotelmapping.org/en/products/hotel-mapping-solutions/) merges the records across sources under a single [HM ID](https://hotelmapping.org/en/glossary/hm-id/). [Room mapping](https://hotelmapping.org/en/products/room-mapping-solutions/) gathers the different spellings of the same room in a single group.

## Delivery formats

| Format | When it fits |
| --- | --- |
| REST API | Single hotel or single code lookup, instant check |
| Daily full dump | Rebuilding the entire catalog |
| [Delta dump](https://hotelmapping.org/en/glossary/delta-dump/) | Receiving only new and changed records |
| Webhook | Change notification (planned) |

Dump files are prepared in CSV, JSON and Parquet formats. Each row contains your [supplier code](https://hotelmapping.org/en/glossary/supplier-code/), the HM ID and, where available, cross-IDs.

## What happens to existing IDs?

You or your customers may have been working with another mapping provider's hotel IDs or your own system's IDs so far. These IDs are stored alongside the HM ID as cross-references; your customer can use the new field as an additional column without abandoning their existing mapping. Redistributing third-party IDs to your own customers may be subject to the license terms of the provider that issued the ID.

## What does it give your customers?

A clean inventory lowers the agency's own mapping cost and reduces support tickets. We cover the effect of duplicate records on the agency side in the [cost of duplicate hotels](https://hotelmapping.org/en/guide/cost-of-duplicate-hotel-listings/) article, and the distinction between static and dynamic data in the [hotel XML integration](https://hotelmapping.org/en/guide/what-is-hotel-xml-integration/) guide.

To get started, you can [request a tailored quote](https://hotelmapping.org/en/get-a-quote/).

## Frequently asked questions

### Can we distribute the HM ID to our own customers?

Distribution and redistribution terms are set in the contract. Technically, the HM ID appears in dump files as a field next to your hotel code.

### What happens to our existing hotel IDs if we switch from another mapping provider?

We store the hotel IDs from your existing mapping provider or your own system as cross-references. Your customers can use the HM ID as an additional field without losing their current mapping.

### How are closed or merged hotels managed?

An HM ID is never given to another hotel. The status of a closed hotel becomes "closed"; for a merged hotel, the old ID's status becomes "merged" and the merged_into field points to the new ID. A detailed history of these changes is planned as a separate product.

## Related articles

- [What is a bedbank? How do agencies work with bedbanks?](https://hotelmapping.org/en/guide/what-is-a-bedbank/)
- [What duplicate hotel listings cost an agency: conversion, cancellations and complaints](https://hotelmapping.org/en/guide/cost-of-duplicate-hotel-listings/)
- [What is hotel XML integration? Static vs. dynamic data](https://hotelmapping.org/en/guide/what-is-hotel-xml-integration/)
