Manage genuine inventory
Maintain room categories and available units that reflect the hotel's actual accommodation capacity.
NEXUS / CHANNEL MANAGER SOFTWARE
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.
CENTRAL INVENTORY CONTROL
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.
Maintain room categories and available units that reflect the hotel's actual accommodation capacity.
Adjust hotel base rates, eligible rate plans, minimum stays and supported stop-sell conditions.
External systems may use different room codes, rate identifiers, restrictions and authentication methods.
Rejected changes, unavailable interfaces or incomplete mappings must be identifiable rather than silently assumed successful.
Hotel-direct, independent OTA and BM24 bookings retain their appropriate commercial relationships.
INTERACTIVE CHANNEL SYNCHRONISATION STUDIO
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.
All values are invented for this example. Applying a change updates this preview only.
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.
These represent possible separate booking sources—not verified integrations.
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
A useful hotel distribution workflow depends on the information behind each connection and on the processes that keep it reliable.
Maintain the hotel's actual units and relevant room categories in the supported management environment.
Apply eligible day-based rates while preserving the distinction between base prices and channel-specific commercial terms.
Prepare minimum stays, stop-sell conditions and rate-plan restrictions where the intended connection supports them.
Map the hotel's accommodation data to external provider IDs before sending or receiving production updates.
Identify the booking origin so confirmations, modifications and financial rules remain distinguishable.
Recognise rejected changes or unavailable channels and establish an appropriate operational response.
Support several compatible OTAs alongside approved PMS and other hotel technologies without artificial standard-OTA per-channel fees.
Include a supported direct reservation route while keeping genuine hotel-direct bookings outside BM24 network fees.
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
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.
Guests book through the hotel's own website or another eligible direct sales process.
Payment and cancellation arrangements follow the applicable hotel-direct terms.
Compatible independent booking providers can form part of the hotel's distribution mix.
External commission and provider conditions remain separately applicable.
Approved inventory may be distributed through participating BM24 channels under the agreed contract.
The internal network rate and portal selling prices have different roles.
FROM CONNECTION SETUP TO LIVE INVENTORY
A channel is not ready for real hotel guests simply because a configuration screen displays a connection name.
Confirm eligibility, authorised contacts and the relevant partnership agreements.
Match room codes, rate plans, occupancy and applicable restrictions to each provider.
Check accepted and rejected rate or availability changes, and reservation workflows.
Remove and verify previous BM24 supplier-fed listings before direct NEXUS distribution.
Enable live booking inventory only after explicit operational approval and controlled tests.
ONE CHANNEL FOUNDATION · FOUR SOFTWARE PACKAGES
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.
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
Understand how the Channel Manager is designed to work, where commercial responsibilities differ and which checks are necessary before live use.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Discover the NEXUS technology approach, understand the BM24 partnership and discuss the right setup for your property.