Opens in a new tab
NEXUSHOTELCONNECT24
NEXUS · HOTEL OTA CONNECTIVITY

Connect Your Hotel. Manage Supported Booking Channels.

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.

✓ OTA Connectivity ✓ Room & Rate Mapping ✓ Availability Updates ✓ Booking Source Integrity

The examples on this page do not represent confirmed external OTA integrations. Production connectivity is available only after implementation and activation.

Structured Connections Prepare supported integration routes.
Room Mapping Match hotel inventory to channel requirements.
Validated Data Exchange Test supported update workflows.
Controlled Activation Review every connection before production use.
NEXUS CONNECTIVITY CONTROL CENTRE

One Overview. Clear Connection Status. Better Integration Control.

Explore a sample dashboard showing room mappings, technical review stages, validation checks and the information required before activating external channels.

Illustrative Dashboard
HC24 · NEXUS OTA Connectivity Management
EXAMPLE DATA

Example Hotel · Integration Overview

Fictional Property · No Live External Connections

Pre-Activation View
3 Sample Room Types
2 Sample Rate Plans
1 Example Pending Review
0 Live Channels in Demo

External Channel Integration Examples

No real providers connected
Sample OTA Connection A Fictional External Channel
Mapping Review
Pending · Demo
Sample OTA Connection B Fictional External Channel
Not Configured
Inactive · Demo
Sample OTA Connection C Fictional External Channel
Not Authorised
Disabled · Demo

Room & Rate Mapping Preview

Illustrative Property Mapping
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
Room mapping: Hotels and external providers may use different identifiers for the same accommodation category. A validated mapping associates the relevant hotel room and rate plan with the correct external channel values. The codes above are fictional and are not issued by any real OTA.

Integration Workflow Preview

Example review activities, not real system logs.
Validate Hotel Inventory Check room types, counts and rate plan data.
Review Room Mapping Confirm room and rate identifiers before integration testing.
Test Data Exchange Verify supported update and acknowledgement methods.
Approve Production Activate only after required checks succeed.

Production Readiness Checks

Essential conditions to review before enabling real connectivity.
Hotel Verification Required
Channel Agreement Required
Room & Rate Mapping Required
Booking Validation Required
Error Handling Tests Required
Production Approval Required
NEXUS OTA Connectivity Dashboard Concept No Live External Provider Connection

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.

HOTEL OTA INTEGRATION FEATURES

The Essential Building Blocks of Reliable OTA Connectivity.

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.

Room Type Mapping

Associate NEXUS room categories with the correct accommodation identifiers used by a compatible external channel.

Rate Plan Mapping

Review how hotel rate plans, included services and booking conditions correspond to supported OTA offers.

Availability Updates

Prepare valid room inventory for supported channels and verify how availability changes are transmitted.

Booking Restrictions

Map supported rules such as minimum stays, stop-sell dates and other conditions according to the channel's capabilities.

Reservation Import

Validate incoming reservation information from approved channels before creating the corresponding hotel booking record.

Reservation Changes

Handle supported booking modifications and cancellations while preserving original reservation data.

Delivery Confirmation

Review acknowledgements and provider responses where an integration supports confirmation of processed updates.

Error Monitoring

Detect failed updates, invalid mappings and processing problems so they can be investigated safely.

Booking Source Integrity

Preserve the original source of reservations for accurate booking handling, reporting and commercial treatment.

CONTROLLED OTA CONNECTION PROCESS

Five Steps From Hotel Preparation to Approved Connectivity.

Every external provider integration needs the appropriate technical and commercial preparation before live data exchange begins.

01

Prepare the Hotel

Configure verified room categories, rate plans, room counts and availability.

02

Review Compatibility

Confirm that the external channel supports the required integration methods and agreements.

03

Map Rooms & Rates

Match the hotel inventory and rate plans with the provider's supported identifiers.

04

Test Data Exchange

Verify updates, booking events, error handling and relevant channel responses.

05

Approve & Monitor

Activate the validated connection and monitor its operational performance after approval.

✓

Keep Records Accurate

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.

RESERVATION PROCESSING

A Booking Is More Than a Message From an OTA.

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.

  • Verify the Original Channel
  • Match the Correct Hotel and Room
  • Validate Booking Dates and Details
  • Handle Duplicate Event Delivery
  • Preserve Cancellation Information
  • Record the Processing Outcome
  • Investigate Booking Conflicts
OTA Reservation Processing Conceptual Integration Workflow
Reservation Received From an approved external channel
01
Source & Payload Validation Verify authenticity and required fields
02
Room & Date Matching Map the correct inventory and stay period
03
Duplicate & Conflict Checks Process repeated events safely
04
Reservation Record Updated Only after successful validation
05
This illustration represents intended processing safeguards. It does not confirm that a particular external OTA booking workflow is already implemented.
OTA INTEGRATION SAFETY

Built Around Validation, Monitoring and Controlled Access.

External integrations introduce operational and information-security risks. A responsible integration architecture should account for those risks before enabling live bookings.

Protected Credentials

Store provider credentials securely, restrict authorised access and avoid exposing secrets in public website content.

Input Validation

Validate incoming provider data and reject malformed or unsupported booking information.

Duplicate Protection

Use appropriate idempotency controls so repeated events do not unintentionally create repeated bookings.

Failure Detection

Identify unsuccessful updates and processing errors rather than assuming every request was completed.

Audit Records

Preserve relevant integration events, booking source data and processing outcomes for investigations.

Production Approval

Prevent an external channel from becoming operational until the relevant checks and permissions are complete.

Synchronisation Timing and Availability

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.

BOOKING SOURCE TRANSPARENCY

OTA Connectivity Does Not Change the Origin of a Reservation.

NEXUS separates the original booking source from the technology used to manage reservation information. This distinction matters for commission calculations and operational responsibilities.

External OTA Booking

A reservation made through a third-party online travel agency under the applicable external agreement.

External OTA fees apply. No additional BM24 network commission solely because the booking enters NEXUS.

Own Website Booking

A reservation generated through the hotel's own direct booking channel.

0% additional BM24 Travel Network commission on own direct website bookings.

BM24 Travel Network

Eligible network-generated reservations for approved hotels directly connected through NEXUS.

7% commission on eligible BM24 network-generated bookings, under the applicable agreement.

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.

CONTROLLED HOTEL TRANSITION

Avoid Duplicate Distribution When Moving Hotels to Direct NEXUS Connectivity.

A hotel already offered through LiteAPI-based BM24 portal inventory requires a verified transition before direct NEXUS network publication is approved.

01

Identify

Review the existing LiteAPI-based BM24 hotel publication.

02

Remove

Manually remove the previous supplier publication from affected BM24 portals.

03

Verify

Confirm complete removal across all relevant booking portals.

04

Approve

Authorise direct NEXUS network publication only after required checks succeed.

Historical Supplier Reservations Must Be Preserved

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.

FREE NEXUS CORE

Start With Free Hotel Technology. Add Approved Connections When Ready.

NEXUS Core · €0/month

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.

Channel Manager Included in intended free Core scope.
Room Inventory Essential room configuration.
Rate Plans Basic prices and booking rules.
Availability Essential date and inventory control.
Reservations Basic reservation management scope.
Direct Booking Engine Included in intended Core package.
HOTEL OTA CONNECTIVITY FAQ

Frequently Asked Questions About Hotel OTA Integrations.

Understand how supported OTA connections, room mapping, availability updates, reservations and commercial rules work together.

What is hotel OTA connectivity?

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.

Does NEXUS connect to every online travel agency?

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.

What is room mapping?

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.

What is rate plan mapping?

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.

Can NEXUS update room availability on external OTAs?

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.

Does NEXUS guarantee real-time OTA synchronisation?

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.

Can an OTA booking be transferred into NEXUS?

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.

How should duplicate booking events be handled?

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.

Can OTA cancellations be synchronised?

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.

Is OTA connectivity included in free NEXUS Core?

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.

Does NEXUS charge 7% on external OTA bookings?

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.

What happens to existing LiteAPI reservations?

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.

Can a LiteAPI hotel move to direct NEXUS network distribution?

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.

Are the OTA integrations shown in the dashboard live?

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.

When can my hotel activate an external channel?

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.

HOTELCONNECT24 · NEXUS

Build a More Connected Hotel Distribution Strategy.

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.