Price suggestions your staff approve, never automatic

There is a kind of pricing software that watches the market and quietly moves your rates while you sleep. It is popular with large chains, and it works for them, because a hotel with three hundred rooms and a revenue team is a different animal from a twelve-room lodge outside San Ignacio.

We decided early that Direct Belize would not do that. The system looks at the market, forms a view, and then stops. It shows you a suggestion with the reason behind it. A person approves it or dismisses it. Only then does the new rate go out to your own site and to the booking sites.

This post explains why, and how to think about the suggestions when they land.

The data doesn't know about the wedding

Market data is good at a narrow job. It can see what comparable properties in Placencia are asking for the second weekend in March. It can see that four of them have moved up since last Tuesday. It can see that your rate has not moved since January.

What it cannot see is everything else.

It does not know that eleven of your rooms are already spoken for by a wedding party and the mother of the bride has asked you to hold the twelfth. It does not know that the carpenter is finally coming to redo the decking on cabanas three and four. It does not know that the couple booked in for that week have come every year since their honeymoon and would notice, and mind, if the rate jumped.

It does not know that the road is being worked on, that your cook is away, that you promised a tour operator in Hopkins a quiet rate for their group, or that you simply do not want to be full that week because you are tired.

The system can tell you what the market is doing. It cannot tell you what you know about your own property.

That is not a flaw in the data. It is the normal gap between a spreadsheet and a business run by people who live on the premises. The sensible response is not to pretend the gap isn't there. It is to put a human decision in the middle.

How a suggestion travels

The flow is deliberately short and deliberately interrupted.

• The system compares your rates for upcoming dates against Belize market and competitor rates, shown in BZ$.
• Where it sees a gap worth acting on, it writes a suggestion: the date or date range, the proposed rate, and the reason it is proposing it.
• The suggestion sits in your dashboard. Nothing has changed yet. No guest sees anything different.
• You, or whoever you have given permission to, reads the reason and either approves or dismisses it.
• If approved, the new rate publishes to your own booking engine and syncs out to the booking sites from the same calendar.

The reason matters as much as the number. A suggestion that just says "raise to X" is a demand for trust you have no basis to give. A suggestion that says "comparable properties in your set have moved up for this weekend and you are now the lowest" is something you can argue with.

You can see how the market view and the sync work together on our market intel feature page.

Three suggestions and how to think about each

One: the market has moved up and you haven't.

Four comparable properties have raised their rates for a weekend in the dry season. You are sitting where you were in May. The suggestion is to come up toward the middle of the set.

Think about: how full are you already for that weekend? If you are nearly full, the suggestion is probably right and possibly timid. If you are empty, ask whether the others know something you don't, or whether they are simply more aggressive. And check your own bookings first. If a repeat guest or a group has a verbal hold, you may want to raise the rate only on the room types they are not taking.

Two: a soft stretch midweek.

Three Tuesdays and Wednesdays in September with very little on the books and no particular demand showing in the market. The suggestion is to come down.

Think about: what does cutting actually buy you? If your costs barely move whether two rooms or six are occupied, a lower rate that fills them is sensible. But a discount is not the only lever. You might hold the rate and add something instead — a transfer, a late checkout, a tour — through the pre-arrival messages. A guest who pays your normal rate and gets more is a better long-term customer than one who learns that September is cheap.

Three: you are the cheapest in your set for no reason you can remember.

Sometimes a rate was dropped for a reason that expired. A renovation finished. A soft-opening price for a new cabana became permanent by accident. The suggestion flags it.

Think about: is the reason genuinely gone? If the rooms above the kitchen are still noisy, stay where you are and dismiss it. If the reason has gone, move up — but consider doing it for dates far enough out that nobody with a confirmed booking feels hard done by.

Why approval is not just a safety catch

There is a revenue argument for all this too. Hotels that adjust rates to demand report RevPAR 15–20% higher than those that don't, and static pricing is estimated to leave 15–25% of revenue on the table. Those are reported figures from the wider industry, not a promise about your property — but they point in a clear direction. Rates that never move cost money.

The approval step is what makes moving them possible for a small team. It lets you act on the market without handing over judgement. It also builds a record: over a season you start to see which kinds of suggestions you approve and which you always dismiss, and that is useful knowledge about your own property.

Give the job to whoever actually knows the diary. With staff logins and page-level permissions, that might be your front desk manager rather than you. The decision should sit with the person who knows about the wedding.

If you want to see how this would look against your own rates and your own comparable set, get in touch. Setup is typically done within a couple of weeks, and there is no long-term contract — the site, the domain and the data are yours.