Opens in a new tab
NEXUSHOTELCONNECT24

NEXUS / CHANNEL MANAGER SOFTWARE

One central workspace.
Multiple booking channels.
Greater clarity.

Your hotel should not need a different manual routine for every room rate, availability update and booking channel.

NEXUS is designed to bring core inventory management, channel connectivity and reservation workflows into one connected environment.

Transparent from the start. Core has a €0 monthly NEXUS software subscription fee. Participation in the BM24 Travel Network is required in all NEXUS packages, with separate agreed distribution terms.

Starting package Core · €0/month
Standard OTA connectivity No NEXUS per-channel software fee
Hotel price control Hotel-managed base rates
Network partnership BM24 required in every package

CENTRAL INVENTORY CONTROL

Make one clear decision.
Prepare it for every supported channel.

Hotel teams need to know what is available, at what price and under which conditions.

That begins with accurate room inventory, rate plans and restrictions.

From there, approved connections can be mapped and tested so that supported changes reach the intended channels.

The goal is simpler operation without pretending that every external provider works identically or guarantees instant confirmation.

01

Manage genuine inventory

Maintain room categories and available units that reflect the hotel's actual accommodation capacity.

02

Control rates and restrictions

Adjust hotel base rates, eligible rate plans, minimum stays and supported stop-sell conditions.

03

Map each connected channel

External systems may use different room codes, rate identifiers, restrictions and authentication methods.

04

Validate updates and acknowledgements

Rejected changes, unavailable interfaces or incomplete mappings must be identifiable rather than silently assumed successful.

05

Preserve booking-source separation

Hotel-direct, independent OTA and BM24 bookings retain their appropriate commercial relationships.

INTERACTIVE CHANNEL SYNCHRONISATION STUDIO

Change a room rate.
See the distribution logic.

Try a fictional hotel example. Select a room, adjust its rate or availability and apply the change locally.

Then simulate how four booking routes might respond—including a rejected mapping that needs investigation.

This is a browser-only educational preview, not the production NEXUS dashboard.

NEXUS / Channel Studio Fictional property · Sample prices in EUR · Local browser state
DEMO ONLY
NO LIVE API REQUESTS

Hotel source settings

All values are invented for this example. Applying a change updates this preview only.

Maximum 12 rooms

Select a room category and adjust the fictional values.

The BM24 network-price example uses 93% of the selected hotel base rate. This figure is not the public guest price, the final hotel payout or an additional automatic commission.

Illustrative channel destinations

These represent possible separate booking sources—not verified integrations.

CLASSIC DOUBLE · HOTEL SOURCE €169.00
9 rooms
Min 1 night
Hotel Direct Booking Illustrative direct rate reference
€169.00
Availability: 9 · Min stay: 1 Initial example
External OTA A Fictional external channel · sample mapping
€169.00
Availability: 9 · Min stay: 1 Initial example
External OTA B Fictional external channel · error example
€169.00
Availability: 9 · Min stay: 1 Initial example
BM24 Travel Network Internal rate illustration · 93% of base
€157.17
Availability: 9 · Min stay: 1 Initial example
Local preview activity
  1. Fictional channel model loaded.
Read the status labels carefully. “Illustrative accepted” means that the browser has simulated a response—not that a real channel acknowledged an update. In production, every supported integration requires proper mapping, authorisation, monitoring, error handling and verified delivery. External OTA rates may differ from hotel base rates according to separate rate plans and agreements. BM24 network participation is mandatory, while live network publication still requires approval.
CONTROL IS NOT THE SAME AS CONFIRMATION

Sending an update is a step.
Knowing what happened is the standard.

A responsible Channel Manager should help identify accepted changes, errors and potential inventory mismatches. Unconfirmed updates must not be treated as successful live synchronisation.

THE COMPONENTS OF CONNECTED DISTRIBUTION

More than a list of channels.

A useful hotel distribution workflow depends on the information behind each connection and on the processes that keep it reliable.

01 / INVENTORY

Central room availability

Maintain the hotel's actual units and relevant room categories in the supported management environment.

02 / PRICING

Hotel-controlled base rates

Apply eligible day-based rates while preserving the distinction between base prices and channel-specific commercial terms.

03 / RESTRICTIONS

Booking rules

Prepare minimum stays, stop-sell conditions and rate-plan restrictions where the intended connection supports them.

04 / MAPPING

Room and rate identifiers

Map the hotel's accommodation data to external provider IDs before sending or receiving production updates.

05 / RESERVATIONS

Source-aware reservation handling

Identify the booking origin so confirmations, modifications and financial rules remain distinguishable.

06 / RELIABILITY

Error visibility

Recognise rejected changes or unavailable channels and establish an appropriate operational response.

07 / CONNECTIONS

Open multi-connection approach

Support several compatible OTAs alongside approved PMS and other hotel technologies without artificial standard-OTA per-channel fees.

08 / DIRECT SALES

Hotel Booking Engine

Include a supported direct reservation route while keeping genuine hotel-direct bookings outside BM24 network fees.

09 / BM24

Network rate relationship

Derive the internal BM24 rate at 93% of the agreed hotel base rate, separately from guest retail prices and final settlement.

ONE WORKSPACE · DISTINCT COMMERCIAL RELATIONSHIPS

A booking source must never get lost in the system.

NEXUS can be used to organise information from different booking routes. It does not turn a genuine direct booking or independent OTA booking into a BM24 transaction simply because it appears in the same management environment.

01 / HOTEL DIRECT

Your own booking channel

Guests book through the hotel's own website or another eligible direct sales process.

Payment and cancellation arrangements follow the applicable hotel-direct terms.

No additional BM24 network-booking fee merely for using NEXUS.
02 / INDEPENDENT PROVIDERS

External OTA reservations

Compatible independent booking providers can form part of the hotel's distribution mix.

External commission and provider conditions remain separately applicable.

NEXUS does not add a per-channel software fee for standard supported OTA connections.
03 / BM24 NETWORK

Our own distribution relationship

Approved inventory may be distributed through participating BM24 channels under the agreed contract.

The internal network rate and portal selling prices have different roles.

BM24 partnership required in every NEXUS package.

FROM CONNECTION SETUP TO LIVE INVENTORY

Five checks before a hotel relies on the connection.

A channel is not ready for real hotel guests simply because a configuration screen displays a connection name.

01 / VERIFY

Approve the hotel

Confirm eligibility, authorised contacts and the relevant partnership agreements.

02 / MAP

Map inventory

Match room codes, rate plans, occupancy and applicable restrictions to each provider.

03 / TEST

Validate updates

Check accepted and rejected rate or availability changes, and reservation workflows.

04 / RECONCILE

Resolve supplier conflicts

Remove and verify previous BM24 supplier-fed listings before direct NEXUS distribution.

05 / AUTHORISE

Release deliberately

Enable live booking inventory only after explicit operational approval and controlled tests.

Critical supplier-transition rule: If a property is already listed in the BM24 Travel Network via LiteAPI, its supplier-fed publication must be manually removed and verified across the relevant portals before direct NEXUS network publication is approved. Existing LiteAPI reservations, refunds and cancellations remain under their original arrangements. Initial real-booking tests require specific authorisation and refundable or cancellable rates.

ONE CHANNEL FOUNDATION · FOUR SOFTWARE PACKAGES

Core connectivity without a per-standard-channel NEXUS fee.

The package you choose determines additional hotel-management functions.

Standard supported OTA connectivity is not artificially capped by the software tier. Actual supported integrations and release readiness must still be verified.

FOUNDATION

Core

€0 per month

Essential Channel Manager, inventory, rates, reservations and Direct Booking Engine.

BM24 distribution partnership required
GUEST OPERATIONS

Smart

€19.90 per month

Core plus guest communication, check-in and staff workflow capabilities.

BM24 distribution partnership required
COMMERCIAL INSIGHT

Growth

€39.90 per month

Smart plus revenue analytics, pricing recommendations and commercial tools.

BM24 distribution partnership required
ADVANCED MANAGEMENT

Complete

€59.90 per month

Growth plus advanced automation, portfolio oversight and expanded APIs.

BM24 distribution partnership required

Prices indicate monthly NEXUS software subscriptions in EUR, excluding applicable taxes. Independent OTA commissions, payment-provider charges and BM24 network commercial terms are separate. Package features and individual integrations are subject to confirmed release availability.

FREQUENTLY ASKED QUESTIONS

Connected channels.
Clear answers.

Understand how the Channel Manager is designed to work, where commercial responsibilities differ and which checks are necessary before live use.

What does a hotel Channel Manager do?

A Channel Manager helps a hotel organise inventory, rates and reservations across supported booking channels. Actual capabilities depend on the connected provider, approved rate mapping and deployed product version.

Is the NEXUS Channel Manager free?

NEXUS Core has a €0 monthly software subscription fee. However, BM24 Travel Network participation is mandatory in all four packages, and eligible network bookings follow separate agreed commercial terms. Independent provider charges may also apply.

How many OTAs can a hotel connect?

NEXUS does not impose an artificial package-based limit or per-channel NEXUS software fee on standard supported OTA connections. The number of usable connections depends on supported integrations, provider authorisation, technical compatibility and successful testing.

Does NEXUS automatically support every OTA or PMS?

No. An external system must have a compatible and approved integration. Neither the demonstration nor an integration category implies that any particular third-party connection is already live or certified.

Do rate changes reach every channel instantly?

No instantaneous or universal delivery guarantee is made. Channel APIs may reject changes, impose restrictions or be temporarily unavailable. Production integrations require mapping, delivery checks, error handling and ongoing monitoring.

What happens if a channel rejects a rate update?

The relevant update should be treated as an exception to investigate. It must not be presented as successfully delivered simply because a request was generated. The interactive demonstration includes a fictional rejection example to illustrate the distinction.

Can I control prices and stop-sell restrictions?

Hotels control their applicable base rates and genuine availability. Supported minimum stays, stop-sell conditions and other rules depend on the specific rate plans and connected systems. Changes to existing confirmed booking prices do not happen automatically.

How is the BM24 internal network rate calculated?

Under the standard agreed relationship, the internal BM24 network rate is 93% of the applicable hotel base rate. An example €200 base rate corresponds to an internal €186 network rate. The public guest price, hotel payout and settlement treatment depend on separate agreed terms.

Is BM24 participation optional?

No. Participation in the BM24 Travel Network is mandatory in Core, Smart, Growth and Complete. Actual hotel inventory publication remains subject to partner approval, accepted contracts and technical readiness.

Does BM24 charge for independent OTA or hotel-direct reservations?

A genuine independent OTA booking or hotel-direct reservation does not incur an additional BM24 network-booking fee merely because NEXUS manages it. External OTA commissions and payment-provider charges may still apply under separate contracts.

Can I switch from existing LiteAPI inventory to direct NEXUS distribution?

Yes, but only through a controlled supplier transition. Previous LiteAPI-fed BM24 listings must be manually removed and the removal verified before direct NEXUS network publication. Existing LiteAPI bookings remain associated with their original terms, cancellation and refund responsibilities.

Can I try the software without creating real bookings?

The interactive studio on this page is a fully local, fictional demonstration. It creates no accounts, reservations or payments; it makes no API requests and does not change live hotel inventory.

Less channel confusion.
More control over your hotel's workflow.

Discover the NEXUS technology approach, understand the BM24 partnership and discuss the right setup for your property.

Book a NEXUS demonstration