Dirs21 best practices: getting more from your hotel management system

Why configuration matters as much as the system itself

Dirs21 is a capable hotel management platform used by thousands of properties across Europe. Yet hotels using the same version of Dirs21 often achieve dramatically different operational outcomes — not because of the software's capabilities, but because of how it is configured and how its data is connected to the rest of the hotel's technology stack. This guide covers the configuration and integration practices that consistently differentiate high-performing Dirs21 implementations from average ones.

Rate plan structure

One of the most common configuration mistakes in Dirs21 is an overly complex rate plan hierarchy. Properties accumulate rate plans over time — BAR, advance purchase, non-refundable, corporate base, corporate negotiated tier 1, corporate negotiated tier 2, long stay — without pruning rates that are no longer commercially active. This creates maintenance overhead, increases the likelihood of rate parity errors across channels and makes revenue management reporting harder to interpret.

Best practice is to maintain a lean core rate structure: a base BAR rate for each room type, derived rates applied as percentage adjustments for standard variations, and explicitly named corporate rates for specific accounts. Derived rates are the key — they allow a single rate change to flow through to all relevant categories automatically, reducing the risk of inconsistency.

Channel configuration

Dirs21's channel manager provides strong connectivity to major OTAs. The configuration decision that most affects revenue performance is which rate plans are exposed to which channels. Not all rate plans should be distributed to all channels. Non-refundable rates should typically be excluded from channels with high cancellation rates. Advance purchase rates with long booking windows should not be exposed to last-minute booking channels. Deliberately mapping rate availability to channel characteristics requires an upfront mapping exercise but pays off in reduced cancellation exposure and better margin by channel.

Reservation workflow and notifications

Dirs21's notification system is powerful but often underused. Configure automated notifications for: new reservation creation (to front desk and revenue manager); modification to high-value reservations; cancellations within 48 hours of arrival; and no-shows at the property's standard check-in cutoff time. These notifications, sent to the right staff via email or the Dirs21 mobile app, eliminate the need for manual monitoring of the reservations list and ensure that exceptions are escalated immediately rather than discovered at end of day.

Reporting cadence

Dirs21's reporting function covers occupancy, revenue, channel mix and booking lead time. The properties that use these reports most effectively run them on a fixed cadence — daily flash report at 08:00, weekly production report on Monday, monthly management report on the 5th working day — and act on them with defined decision rules. A daily flash showing occupancy running 12% below pace for the following weekend should trigger a rate or promotion decision that day, not a discussion two weeks later.

API and integrations

Dirs21's API is the key enabler for extending the platform's native capabilities. Enable API access in your account settings as soon as your subscription supports it, even if you have no immediate integration plans. When you are ready to connect add-ons — for upselling, review management, loyalty programmes or custom reporting — the API access will already be configured and validated.

When using the Dirs21 API, always work with the documented endpoint versions and subscribe to the Dirs21 API changelog. API changes without proper versioning can break integrations; the CockpitMod API Gateway module provides a stable versioned interface over the top of the Dirs21 API to protect custom integrations from upstream changes.

Data quality practices

The quality of data in Dirs21 directly affects the quality of outputs from any add-on module. The most common data quality issues are: duplicate guest profiles, inconsistent company names for corporate accounts, and rate categories applied to reservations that should be in a different category. Deduplicate guest profiles monthly, standardise corporate account naming with a fixed convention, and audit rate category assignment in the monthly production report.