Room Type Mapping
Associate NEXUS room categories with the correct accommodation identifiers used by a compatible external channel.
Bring room information, rate plans, availability and reservation workflows together through a structured approach to hotel distribution connectivity.
NEXUS is designed to help hotels prepare, verify and manage integrations with compatible external online travel agencies. Every connection requires appropriate agreements, technical testing and production approval.
The examples on this page do not represent confirmed external OTA integrations. Production connectivity is available only after implementation and activation.
Explore a sample dashboard showing room mappings, technical review stages, validation checks and the information required before activating external channels.
Fictional Property · No Live External Connections
| NEXUS Room Type | Example OTA Code | Rate Plan | Mapping Status | Production |
|---|---|---|---|---|
| Standard Double | EX-STD-01 | Flexible Rate | Draft Mapping | Not Live |
| Superior Double | EX-SUP-02 | Flexible Rate | Draft Mapping | Not Live |
| Family Room | EX-FAM-03 | Breakfast Rate | Review Required | Not Live |
Dashboard example: The interface above is a static illustration of the intended connectivity management experience. All OTA names, mapping codes, channel statuses and workflow indicators are fictional. It does not indicate an active integration with any external provider.
Connecting a hotel to an external booking channel requires more than exchanging room prices. A dependable integration must consider inventory, booking rules, reservation changes and operational safeguards.
Associate NEXUS room categories with the correct accommodation identifiers used by a compatible external channel.
Review how hotel rate plans, included services and booking conditions correspond to supported OTA offers.
Prepare valid room inventory for supported channels and verify how availability changes are transmitted.
Map supported rules such as minimum stays, stop-sell dates and other conditions according to the channel's capabilities.
Validate incoming reservation information from approved channels before creating the corresponding hotel booking record.
Handle supported booking modifications and cancellations while preserving original reservation data.
Review acknowledgements and provider responses where an integration supports confirmation of processed updates.
Detect failed updates, invalid mappings and processing problems so they can be investigated safely.
Preserve the original source of reservations for accurate booking handling, reporting and commercial treatment.
Every external provider integration needs the appropriate technical and commercial preparation before live data exchange begins.
Configure verified room categories, rate plans, room counts and availability.
Confirm that the external channel supports the required integration methods and agreements.
Match the hotel inventory and rate plans with the provider's supported identifiers.
Verify updates, booking events, error handling and relevant channel responses.
Activate the validated connection and monitor its operational performance after approval.
Preserve booking sources, event history and the commercial conditions relevant to each reservation.
Activation requirement: Preparing a room mapping or obtaining technical credentials is not the same as activating a live OTA connection. Production distribution requires the appropriate agreements, validation, testing and explicit approval.
Receiving an external reservation requires accurate matching of the property, room type, stay dates and applicable booking rules.
A reliable integration should also identify changes, duplicates and failed operations before reservation records are treated as final.
External integrations introduce operational and information-security risks. A responsible integration architecture should account for those risks before enabling live bookings.
Store provider credentials securely, restrict authorised access and avoid exposing secrets in public website content.
Validate incoming provider data and reject malformed or unsupported booking information.
Use appropriate idempotency controls so repeated events do not unintentionally create repeated bookings.
Identify unsuccessful updates and processing errors rather than assuming every request was completed.
Preserve relevant integration events, booking source data and processing outcomes for investigations.
Prevent an external channel from becoming operational until the relevant checks and permissions are complete.
No external OTA connection should be described as universally real-time without confirming its technical behaviour. Some providers may use different exchange methods, update frequencies, acknowledgements and retry procedures. The implementation must handle communication delays and failed updates safely. No Channel Manager can guarantee that every possible overbooking situation will be prevented.
NEXUS separates the original booking source from the technology used to manage reservation information. This distinction matters for commission calculations and operational responsibilities.
A reservation made through a third-party online travel agency under the applicable external agreement.
A reservation generated through the hotel's own direct booking channel.
Eligible network-generated reservations for approved hotels directly connected through NEXUS.
Separate LiteAPI supplier model: Existing LiteAPI supplier reservations remain separate from direct NEXUS hotel bookings. They retain their original supplier and commercial terms. The direct NEXUS 7% network commission must not automatically be applied to LiteAPI bookings. Existing cancellation and refund obligations must also remain protected.
A hotel already offered through LiteAPI-based BM24 portal inventory requires a verified transition before direct NEXUS network publication is approved.
Review the existing LiteAPI-based BM24 hotel publication.
Manually remove the previous supplier publication from affected BM24 portals.
Confirm complete removal across all relevant booking portals.
Authorise direct NEXUS network publication only after required checks succeed.
Removing a hotel from future LiteAPI publication must not cancel, overwrite or reclassify existing supplier bookings. Their original records, cancellation rights, refund obligations and commercial conditions must remain intact. Direct NEXUS network distribution must not be activated before the previous supplier publication has been manually removed and the removal verified.
NEXUS Core includes the intended essential Channel Manager, room inventory, rate management and direct booking tools.
External OTA connectivity is a separate technical capability requiring supported provider integrations, relevant agreements, successful testing and production activation.
Optional advanced features and third-party services may have additional costs.
Understand how supported OTA connections, room mapping, availability updates, reservations and commercial rules work together.
Hotel OTA connectivity refers to the technical integration between a hotel's systems and an external online travel agency. Depending on the supported integration, information may include room availability, rates, restrictions and reservations.
No. External OTA connectivity depends on supported integrations, provider agreements, technical compatibility, testing and activation. An external channel must not be assumed to be connected unless its integration has been verified.
Room mapping associates a hotel's accommodation categories with the corresponding identifiers used by an external booking channel. Accurate mapping helps prevent incorrect room information from being exchanged between systems.
Rate plan mapping connects the hotel's pricing and booking conditions with compatible offers supported by an external provider. Relevant restrictions and included services should also be considered.
Availability exchange is an intended capability of supported Channel Manager integrations. The actual update methods, timing and supported fields depend on the individual provider and verified connection.
No universal real-time guarantee is made for external OTA connections. Data exchange may depend on provider systems, communication methods, network conditions and successful processing. Integrations must be monitored for failures.
Reservation import can be supported by a compatible and approved integration. Incoming information must be validated and correctly matched before being recorded in the hotel's system.
Reliable integrations should use appropriate duplicate detection and idempotent processing. A repeated notification should not unintentionally create an additional hotel reservation. Such safeguards require implementation and testing.
Cancellation and reservation-change processing depend on the supported provider integration. The system must preserve applicable booking terms, original source records and relevant cancellation information.
NEXUS Core includes the intended essential Channel Manager functionality with a €0 monthly Core software fee. Actual external OTA integrations are separate technical capabilities requiring compatibility, agreements and activation. External provider charges may apply.
No additional BM24 Travel Network commission applies solely because an external OTA reservation is managed through NEXUS. The external OTA's applicable agreement and charges remain relevant. The BM24 7% model applies only to eligible BM24 network-generated bookings for approved, directly connected NEXUS hotels.
Existing LiteAPI supplier bookings retain their original supplier records, commercial conditions, cancellation procedures and refund responsibilities. They must not automatically be converted to direct NEXUS bookings or reassigned a different commission model.
A controlled transition is required. Existing LiteAPI-based publication must first be manually removed from every affected BM24 booking portal. The removal must be verified before direct NEXUS network publication is approved. Existing supplier bookings must remain protected.
No. The dashboard contains fictional external channel entries, sample mapping codes and illustrative review statuses. It does not represent an active connection to a real OTA.
Production activation depends on hotel eligibility, provider compatibility, relevant agreements, validated mapping, successful integration testing and explicit approval. The availability of each integration must be confirmed separately.
Important information: This page describes the intended NEXUS OTA connectivity architecture and hotel integration workflows. All dashboard entries, external channel examples, mapping identifiers, technical review stages and status indicators are fictional illustrations. This page does not create a live OTA connection, process reservations, modify room availability or establish provider support. Actual integrations require technical compatibility, relevant agreements, successful testing, operational readiness and explicit production approval. The free NEXUS Core package includes essential Channel Manager functions and direct booking technology within its intended €0 monthly Core scope. Eligible BM24 Travel Network bookings for approved, directly connected NEXUS hotels follow the applicable 7% network commission model. External OTA reservations, own direct website bookings and LiteAPI supplier bookings remain commercially separate. Previous LiteAPI-based BM24 hotel publication must be manually removed from all affected portals and removal verified before direct NEXUS network distribution can be approved. Existing supplier bookings, cancellations and refunds must remain protected under their original arrangements. External provider fees, payment processing costs and applicable taxes may apply. HotelConnect24 provides hotel technology and distribution infrastructure. It does not act as a tour operator.
Prepare your hotel for structured Channel Manager operations, accurate room mapping and supported distribution integrations. Start with free NEXUS Core and explore additional connectivity opportunities as approved integrations become available.