The Feature Request That Never Ships

Standardisation is a feature — for chains

When a group runs ninety properties, identical process across all of them is the entire point. A regional manager should be able to walk into any property and read the same screens. Head office needs one report definition. Staff should transfer between sites without retraining.

So chain-oriented systems are built to enforce sameness, and they are good at it. The rigidity independents complain about is not a defect in that context — it is the product working exactly as designed, for a customer who is not you.

For an independent, the workflow is the differentiator

Independents do not win on scale or loyalty programmes. They win on the specific things they do that a chain cannot be bothered to do.

The guesthouse that runs airport pickups and needs the arrival time attached to the reservation. The villa with a three-hour changeover and a caretaker rather than a housekeeping department. The long-stay property splitting a folio across a company and a guest every single month. The family hotel where breakfast counts get called through at 9pm and the local tourist tax is charged per adult, per night, and has to appear correctly on a printed invoice.

Ask a chain-shaped system for those and you get a shrug, a text field, or a suggestion to change how you work. But the changeover, the pickup and the tax handling are not inefficiencies to be standardised away — for a twelve-room property they are the operation.

What "we have added it to the roadmap" means

It is rarely a lie, and it is almost never a commitment. Roadmap prioritisation at an enterprise vendor is weighted by seats, contract value, renewal risk and how many accounts asked. Your request enters that weighting with the influence of one small property.

Meanwhile the same quarter has to absorb a chain customer’s compliance requirement and an integration the sales team already promised. The request is not rejected — it simply never becomes the most important thing in any given quarter, which produces the same outcome more slowly.

The workaround tax

Nobody waits idly. They build the missing feature by hand, and pay for it in a currency that never shows up on the invoice.

A spreadsheet running alongside the PMS for the thing the PMS will not track. The notes field used as a database, unsearchable and unreportable. Double entry between systems, which is double the chance of a mistake. A process that only one long-serving employee actually understands, which becomes a genuine business risk the week they resign.

Then the annual renewal arrives for the system that caused it. The licence is the small number; the workaround is the expensive one.

How Frontdesko prioritises independents

The clearest evidence of who a product is built for is the unglamorous work it has already done. Four examples, each of which exists because an independent property needed it and a chain-shaped system would have called it an edge case.

Tourist tax that counts people, not percentages. Across much of Europe the city tax is charged per adult, per night, children are exempt, and it must appear as its own line on the invoice. A family of four in one room is not "4 × tax" — it is two adults × the number of nights, and the number changes if they extend by a day. Frontdesko treats that as a billing mode in its own right, deriving the adult count per room per night from the reservation. In a system built for flat percentage taxes, this is a manual adjustment somebody has to remember on every single folio — and the one they forget is the one the inspector finds.

Rates that price the guest, not just the room. Chains sell a room at a room rate. A guesthouse sells the same twin at one price for solo occupancy, another for two sharing, another for three — and then charges for the fourth guest and the child differently again. Frontdesko stores a rate per occupancy level, alongside how many adults and children a room type includes before extra-person pricing applies. That is a different pricing model, not a discount rule bolted onto a room rate, which is why it is so painful to fake in a system that assumes the chain approach.

A guest book the hotel writes itself, in its own languages. A chain issues a brand-standard compendium. An independent needs to tell guests that the bakery opens at seven, the beach path is behind the olive tree, and the boiler is temperamental before nine. Frontdesko stores those sections per hotel, per language, with an English fallback when a translation is missing, and serves them behind the room QR code — so the hotel edits its own house information rather than filing a request to have a field renamed.

Direct bookings in the guest's language, not just the major ones. The booking engine ships in fifteen languages — including Lithuanian, Filipino, Thai, Indonesian, Hindi and Arabic. That list is not a market-expansion slide; it is the shape of a customer base of small properties in places where "we support English, Spanish, French and German" means the guest books through an OTA instead, and the hotel pays commission for the privilege.

The same logic runs through the rest of it. The guest app handles self check-in with ID upload and signature capture, because the 11pm arrival at a twelve-room property has nobody waiting at a desk. Room-service orders post straight to the folio instead of living in a separate till. And features a property does not run can simply be switched off per hotel, rather than being navigated around forever.

And the commercial model points the same direction: the PMS is free forever with no room limit, so a ten-room property is not a rounding error to be tolerated — it is the intended customer. When independents are the whole business, their odd-shaped requirements are the roadmap rather than a distraction from it.

If a specific workflow matters to your property, the useful move is to raise it before you migrate, not after. The contact page reaches a team that has worked front desks, and — as the integrations page puts it about channel coverage — the answer you should expect is an honest yes or no about today, not a roadmap gesture.