
Written by Alpha Digital Agency· · Updated
Hotel Internet Booking Engine: Match Room Code, Two-Language Name, and Rate Package
Mapping guide for room type and rate testing from the hotel website to the internet booking engine when the English and Indonesian room naming versions are not the same, complete with source mapping table, testing steps, and handover process to the hotel team.
Why Room Name Mapping Becomes a System Weak Point in Direct Reservation
When a hotel runs a direct reservation through its official website, the hotel internet booking engine becomes a machine that displays availability, rates, and room types to prospective guests. Behind the simple-looking interface, there is a long data flow: the property management system (PMS) stores room types and rates, the booking engine pulls that data, and the hotel website page displays it with names that are often already translated.
The issue arises when the English and Indonesian room names are not the same. The hotel website may display 'Deluxe Ocean View', while the booking engine or PMS uses 'Kamar Deluxe Pemandangan Laut'. If the mapping between these two labels is not rigorously tested, guests may book one room type but receive another, the rate displayed on the page may differ from the rate stored in the system, or a specific room type may not appear in the booking engine at all. All these scenarios erode guest trust and burden the front office with manual clarification.
This article discusses how to systematically test room type and rate mapping from the site to the booking engine, using the source mapping table as a single reference document, and how to deliver the results to the hotel with clear accountability.
Risks When the Bilingual Room Name Is Not Identical
The difference in naming between the two languages is not merely a cosmetic issue. Here are the patterns of issues that need to be watched out for during integration testing:
- Inconsistent literal translation. If "Superior Twin" is translated as "Superior 2 Tempat Tidur" on one page, but "Kamar Superior Twin" on another page, there is a risk the system will consider them two different products. Check whether all translation variations point to the same PMS room type.
- Names are nearly identical for different types. "Family Suite" and "Family Room" sound similar, and when one is mapped to the wrong type, the Suite rate can appear for the Family room.
- Space, hyphen, and capital letters. When creating a mapping table, copy each room name character by character exactly as written in the system, including spaces, hyphens, and capital letters, then ensure the spelling on the website and PMS uses the identical form before testing is considered complete.
- Name with number or floor. "Room 201 Type" in the PMS does not always match "Standard Room" on the site.
- New room types are not yet mapped. If revenue adds a room type in the PMS without a mapping row for its Indonesian name, there is a risk that the room will not appear in the booking engine. During testing, compare the room type list in the PMS with the mapping table rows to find any unmapped types.
Every risk can only be captured if testing is performed with an explicit mapping list, not by guessing from the final view.
We tested the sample pairing of JRS-S and BAR-FLEX against a practice list containing only JRS-S/BAR-ROOM. The exact-match lookup returned ‘pair not found’. These fictional codes illustrate how to test a match. Hotel staff can repeat the test with the property's approved mapping list.
Building Source Mapping Tables Before Testing Begins
Before opening the booking engine, the team needs to prepare a single document that serves as the 'source of truth': the source mapping table. This document compares room type names at three points — site (English version), site (Indonesian version), and room type in the PMS/booking engine — plus the applicable rate codes.
Here is an example of the source mapping table in the simulation scenario:
| No. | Website name (EN) | Website name (ID) | PMS room type | Rate code | Mapping status |
|---|---|---|---|---|---|
| 1 | Superior Room | Kamar Superior | SUPSTD | BAR-FLEX | Mapped |
| 2 | Deluxe Garden View | Deluxe Pemandangan Taman | DLXGRD | BAR-FLEX | Mapped |
| 3 | Deluxe Ocean View | Deluxe Pemandangan Laut | DLXOCE | BAR-FLEX | Indonesian name not yet mapped |
| 4 | Family Suite | Suite Keluarga | FAMSUI | FAM-PKG | Indonesian name not yet mapped |
| 5 | Junior Suite | Suite Junior | JRS-S | BAR-FLEX | Test input: check the BAR-FLEX mapping on the practice rate sheet |
(The table above is a simulation for the purposes of illustrating the testing process, not specific property data.)
This table is compiled by three parties: the revenue manager who understands room type structure and rates, the front office staff who understand the physical rooms and operational naming, and the digital team that manages the site content. Without all three, the table will be incomplete.
End-to-End Testing Steps from Site to Booking Engine
With the mapping table in hand, testing proceeds in the following order:
- Take a sample per table row. Do not test randomly. Each mapping table row is one test case, including rows with the status "not mapped" — those rows are the most important to check.
- Open the site in English, select room type, and enter the booking engine. Note whether the room name displayed in the reservation engine is consistent with the name on the site page, and whether the initial rate shown matches the rate code set by revenue.
- Change language to Indonesian, repeat the same room selection. Check if the Indonesian version appears with the name matching the table, rather than reverting to English or displaying a mixed name.
- Two-way test. Some guests enter directly into the booking engine page from the campaign link, bypassing the site page. Test this path as well so that mapping is correct not only from one entry point.
- Special rate and package. If there is a rate code such as a family package or rate with breakfast, ensure that rate is attached to the correct room type. Common error: family breakfast package appears in the single room type.
- Check the date limit and availability. A full room type should not display selectable rates, and an available room type should actually be able to be taken to the payment step.
- Document findings per line. Use the "mapping status" column in the table as a place to record results: correct, incorrect connection, not displayed, or tariff attached to the wrong type.
In one internal integration audit, the reservation page loaded successfully but the supporting file referenced by the page was not found, so the release was held [source: internal integration audit, August 29, 2026]. The same pattern applies here: do not conclude that mapping succeeded just because the page opened; success is only proven when the entire table row passes inspection up to the payment step.
Verifying Data in the Analytics Side: Room Types Arriving in the Report
Testing does not stop at the view. If a hotel installs e-commerce tracking on its site, the room type name sent to analytics must also be checked. Google provides official e-commerce measurement documentation that explains events such as view_item, add_to_cart, begin_checkout, and purchase, as well as item parameters such as item_id, item_name, and price — the details can be read on the Google Analytics e-commerce measurement documentation at developers.google.com/analytics/devguides/collection/ga4/ecommerce.
Regarding mapping testing:
- Check whether the
item_namesent to analytics is consistent with the room type name in the mapping table, or at least itsitem_idrefers to the correct PMS type. When testing, verify that each room type sends the sameitem_idin both languages and matches the value with the mapping table so that each type remains identified as a single consistent item. - Use debug mode or the validation tool recommended by the official documentation to view events in real-time, instead of guessing from the daily report.
- Test events in both site languages. If the English and Indonesian versions send different item structures, note as a finding to be fixed before handover.
This verification is important for the revenue manager, as pricing and distribution decisions are made from room type data. The messy mapping at the analytics layer makes the direct sales report untrustworthy by room type.
Handover to Hotel: Who Does What
After testing is complete, the results are handed over to the hotel with a clear structure, not just an oral summary. The handover document contains a final mapping table with the status of each row, a list of findings and their corrections, as well as task allocation:
- Revenue manager receives the final mapping table and is responsible for the accuracy of room type and rate code. He/she signs that each type has been mapped according to the price structure.
- Front office manager or duty manager receives the bilingual room name summary and is tasked with disseminating it to front desk staff, including how to explain the difference in room types to guests if questions arise during check-in.
- Digital team/site receives the final display name list and ensures the site page uses the exact name as the table, without unilateral adjustments.
- Designated process owners (typically revenue or e-commerce staff) keep the mapping table as a living document. Whenever a new room type, renaming, or new rate is introduced, the table must be updated before the change is published.
A good handover process also includes instructions on how to retest: who opens the site in both languages, who verifies the rates in PMS, and where the discrepancy reports are sent.
Decision-Making Steps: When Mapping Is Declared Ready
Use the following concrete check before stating the mapping is complete:
- All table rows are marked as "mapped" — there are no remaining rows with status "unmapped" or "needs verification".
- Each room type appears in the booking engine in both languages with the name according to the table.
- Tariff displayed according to tariff code for the selected test date, directly compared with PMS data by revenue.
- The room type selected by the guest reaches the payment step with a consistent name and price, without changing in the middle of the flow.
- Analytical data recognizes each type as a single whole, not fragmented due to differences in the names of two languages.
- The front office has received and understood the final mapping table, evidenced by written confirmation on the handover document.
If any single check fails, it remaps to the repair cycle and retesting per failed row. The 'ready' decision is taken based on evidence, not the release deadline.
Maintaining Accurate Mapping After Go-Live
Testing is not a one-time activation. Schedule regular inspections: whenever a room type is added, naming changes are made for marketing needs, or tariff structures are adjusted, the mapping table is opened first. The front office is trained to report when a guest mentions an unknown room name at the reception — this is often the earliest signal that the site mapping and operational reality are no longer synchronized.
With a single source mapping document, concrete checks at each flow point, and handovers specifying who is responsible for what, the hotel can run its internet booking engine with confidence that the room type and rate seen by the guest is the actual room type and rate available.
Alpha Digital Hospitality Practice
Need a Google Ads and Direct Booking Audit for Your Property?
We audit OTA commission leakage, GA4 conversion tracking, and Google Ads connections to real hotel or villa reservations.
Related Alpha Digital Pages
Continue withBooking Engine
Explore all articles aboutBooking EngineMore from Alpha Digital