What Can You Actually Do With a PMS? The Detailed Guide, Limits Included

A short-let PMS is four things stacked: a channel manager (your listings and calendar pushed to Airbnb, Booking, Vrbo), an automation engine (guest messages that go out without you), an operations layer (cleaning, tasks, locks), and owner accounting.

What it doesn't do: find your properties, negotiate your mandates, or — we'll come back to this — solve your local compliance. A PMS doesn't replace the job; it stops the job collapsing when you go from 5 units to 50.

We use Hostaway as the thread here because it's what we run across close to 70 apartments, and because its documentation is public — therefore checkable. Everything below is readable in their knowledge base.

This is what most comparisons miss. "Connected to Booking" means nothing until you know how:

• API — real time; pushes availability, rates and content. This is what you want.
• XML — the PMS prepares a daily file, the channel imports it on its schedule. Not instant.
• iCal — availability only. No rates. Refreshed every 10 to 45 minutes. On a high-demand night, 45 minutes is enough to create a double booking.

One rule follows: once a channel is connected, the PMS becomes the master calendar. And the asymmetry nobody mentions: block dates in the PMS and they propagate; block dates in a channel and they may not come back. That's the leading cause of double bookings in practice.

Connecting a channel isn't neutral. On the Airbnb connection, Hostaway's documentation states that the following are reset: length-of-stay discounts (other than weekly/monthly), early bird, last-minute, guest notes and calendar rules. A month of tuning inside Airbnb — gone.

• Booking.com — content is exported once. After that everything is edited by hand in the Extranet. Promotions and restrictions can't be driven from the PMS.
• Expedia — the PMS pushes a 27-night cap regardless of your calendar, and syncs only the total guest payment, not the financial breakdown.
• Booking.com — 90-night maximum stay.
• Vrbo — the brutal one: any listing not matched during integration is permanently archived on Vrbo and cannot be recovered. Don't connect Vrbo on a Friday night.
• Airbnb — 100 photo deletions per listing per week, an API limit. We hit it.

None of these is a flaw in the PMS: they're the channels' APIs. But a comparison that omits them is selling you a fantasy.

Hostaway exposes 15 triggers: reservation, check-in, check-out, inquiry, pending reservation, cancellation, payment success, payment fail, day of week, message received, door code created, online check-in submitted, guest review submitted, pre-auth success, check-in available.

Each fires N minutes/hours/days before or after — 60-day ceiling. Around 80 variables are injectable: first name, dates, Wi-Fi code, door code, guest portal link, balance due.

The limits that matter when you write your messages:

• Booking.com doesn't render clickable links. Your online check-in link arrives as dead text.
• On Airbnb, a message containing a URL or contact details fails before confirmation.
• The door-code message goes out with a 15-minute delay, waiting on the lock. It's deliberate — and it explains a lot of "I never got my code".
• Once an automation is created with conditions, the conditions can't be changed. You recreate it.
• Two-way SMS is only guaranteed for US, Canada and UK numbers. For a European operator that's a real constraint.
• WhatsApp: the docs say automations are "planned for 2026". Not shipped today.

Native dynamic pricing updates every 24 hours and never touches a booked date. Override a rate on the calendar and the tool remembers, and stops touching those nights.

We run PriceLabs on top. The docs are blunt on two points worth knowing first: PriceLabs pushes rates every 24 hours, and "avoid clicking Sync Now in PriceLabs — it may cause Hostaway to block PriceLabs updates". PriceLabs never controls availability, only price.

The golden rule, documented in black and white: never have the same listing active in two pricing tools at once.

If you manage for third parties, this is where your credibility lives. The module runs on formulas — calculations over reservation fields, nestable 7 levels deep, defined at account level then propagated to listings.

Concretely: ownerPayout = subTotalPrice - pmCommission. A 20% commission is subTotalPrice * 0.2. And the smartest part: time-based formulas, versioned on the check-in or check-out event — which is how you change a commission rate without rewriting history.

• channelCommission is only populated for channels that pass it by API. Airbnb passes it; Booking.com typically doesn't — the docs suggest estimating totalPrice * 0.15. An estimate, inside an owner statement. Worth knowing.
• Financials only go back 2 years of check-in dates.

We run 30 auto-statements, 8 on scheduled send. We haven't found this depth elsewhere.

Hostaway ships a booking website. Two things to know before you build your direct strategy on it:

• There's a 1.8% guest service fee on Booking Engine reservations — but it applies to US listings on Stripe only. Outside that, it doesn't hit you.
• The booking website cannot be embedded in an iframe, and custom scripts are disabled on the checkout page for PCI DSS compliance. Which means: no conversion pixel, no chat, no A/B test at the exact moment of purchase. If your acquisition depends on measuring checkout, that's decisive.

Their own docs offer the way out, verbatim: "you can use any booking engine with Hostaway or even build your own through our integrations." That's what we did — our site is our own, on their API.

Our public site runs on the Hostaway API. Real parameters: OAuth2, token valid 24 months, and a rate limit around 15 requests / 10 seconds — a figure we measured in production and found in the API reference; the knowledge base never states it, which is a genuine gap when you're sizing an integration.

Webhooks cover 5 events: reservation.created, reservation.updated, message.received, task.created, task.updated. Two catches: they fire only on guest messages, not yours; and a webhook failing for more than 5 days may be disabled automatically.

Our own limits, which we sent to their product team: GET /v1/listings/{id} returns an empty image list (use the bulk endpoint), you can't mark a direct reservation paid via the public API, and owner statement detail isn't exposed. None of it stopped us — but if your project rests on one of those three, check first.

Starting out: pick a PMS with an API connection (not iCal) to Airbnb and Booking, an automation engine, and owner statements if you manage for others. The rest can wait.

👉 Try Hostaway (free demo via our partner link) — it's what we run in production. It isn't perfect: we keep our own list of limits, several are quoted above, and we send them to their product team rather than stay quiet. None has changed our mind.

We cover the choice itself in our PMS comparison, and the whole job in the concierge guide.