Every room.
Every channel.
A clearer picture.

Start the local EHIS application and sign in with your personal account. Open the setup checklist and enter the property identity, address, country, timezone, currency and responsible contact. Complete the legal issuer and bank fields for invoice drafts.

Confirm the actual room structure. The prepared configuration contains 350 rooms, five restaurants, five bars, five additional outlets and five event rooms, plus reception, shop and kiosk. Replace placeholder names and verify active room types.

Set staff roles and explicit function permissions before financial actions. A staff priority is not an access permission. The current local workflow is for one workstation; simultaneous multi-terminal operation still requires implementation and acceptance testing.

Import or enter the confirmed room capacity by room type and date. Capacity initialisation starts with zero rates and stop sell enabled. Set real rates and restrictions before releasing inventory.

Keep physical capacity as one shared pool. Do not duplicate the same rooms for every OTA. Check for missing calendar dates and oversold room nights before preparing an update.

The local stay ledger and channel room-night dataset are separate modules in this release. Reconcile them with the leading PMS before using the calendar for online distribution.

Choose a catalogue source or create your own channel. Enter the property, room-type and rate-plan IDs supplied for that connection, together with the agreed commission basis.

In the local server setup, configure an approved channel provider or adapter and its authorised credentials. Test capabilities first, then use a small controlled booking retrieval and inventory update.

An entry in the catalogue or a saved credential is not a successful connection. Keep channels on stop sell until mappings, acknowledgements and the OTA extranet have been checked.

For a booking, provide the reference, booking date, arrival, departure, property, source, room type, status, number of rooms, total stay revenue and commission. Departure is exclusive. Revenue and commission are allocated across nights.

Use CSV or normalised JSON for import. Review new and updated rows in the preview, then explicitly commit. A matching property, source, reference, stay date and room type updates an existing row.

Reconcile cancellations and changed stays. If a stay becomes shorter or changes room type, obsolete room-night rows need to be removed or cancelled. Importing the remaining nights alone does not remove the old ones.

Select the property, dates and target channel. Check mappings, inventory coverage, rates, minimum stay and stop sell. The prepared availability deducts active booked room nights from the physical pool.

Export a prepared ARI file for inspection, or use the configured online bridge after explicit review and confirmation. A local export is not sent automatically.

Inspect the receipt and reconcile the provider result. Accepted means the bridge received the request; it does not prove the OTA applied it. Investigate unclear results before repeating a send. Continuous automatic synchronisation is not provided.

Choose the reporting period, channel and cut-off date. Review actual revenue, confirmed future room nights, commission, net contribution and the quality indicators before drawing conclusions.

For the forecast, state the percentage of unbooked open future capacity expected to sell, the ADR and commission for that extra business. Additional planning is available on the all-channel view; it does not uplift existing bookings.

Select the previous year, an older year or custom dates. Historical same-time OTB and pickup need actual snapshots. Export the HTML report for printing / PDF, or use CSV for detailed review.

In the hotel workflow, link each guest and billing recipient to the correct stay. Local room accounts can contain overnight charges, outlet sales and separately recorded cash, externally processed card payments or confirmed bank transfers.

The channel dataset does not automatically create or synchronise every guest folio. Reconcile references and posting status with the leading PMS; do not assume that a retrieved booking has already created a complete guest account.

Select the last complete business day using the hotel timezone and closing boundary. Close and count cashier shifts before saving a management close. Review payments, outlet activity and channel commissions separately. Channel room revenue excluding VAT is not added to local gross POS sales; this avoids an unsupported combined total. The management close is not a fiscal Z-report.

Keep provider credentials in the local server configuration, never in website HTML or support screenshots. Use the supported backup and restore functions and keep backup passwords separately.

The hotel server uses an encrypted local store; the channel workspace has its own dataset and backup workflow. Do not assume a single export covers both. Validate restore procedures and permissions before operational use.

For support, contact info@volker-weber.de with DEV-18.42, the affected action and the full error message. Remove guest details, bank information, card data and API secrets. Support and product discussions are handled by Volker Weber.