Protel rate management: what's built-in vs what needs an add-on
Every revenue manager who joins a Protel property asks the same question in the first week: "What is Protel already doing for rates, and what am I going to have to bolt on?" The honest answer is that Protel does a lot of the boring plumbing very well, and leaves the value-add layer for you.
Out of the box, Protel PMS handles the fundamentals cleanly: rate codes with all the standard modifiers, seasonal riders, market-segment segmentation, MinLOS and MaxLOS, CTA and CTD, package rate composition, and per-room-type derivations from a master rate. These are correct, well-tested, and rarely the source of a real-world problem.
Where Protel is deliberately silent — and where every non-trivial property ends up bolting something on — is the layer above rate codes. Three jobs recur across almost every property I have seen:
1. Nightly automated push from a revenue tool. Protel does not include a revenue engine, and it is not supposed to. Your IDeaS or Duetto or Atomize deployment (or the spreadsheet your revenue manager built by hand) is where the rate values are decided. Getting those values reliably into Protel every night — with restrictions, with retry on failure, with a paper trail — is not something Protel does. It is what our Rate Update Bridge for Protel exists for.
2. Monitoring that the push actually happened. The nastiest revenue failures I have seen are silent: the channel manager cheerfully accepted the batch, the PMS never got it, and the property sold at yesterday's price for three days. Protel does not, by design, actively monitor the interfaces sitting on top of it. Our PMS Sync Sentinel exists to close that gap — it pages you within 90 seconds if a scheduled push does not show up in Protel.
3. Contracted corporate rates that are actually contracts, not just rate codes. Corporate business needs a workspace: contracts with signed PDFs, riders, blackout dates, negotiated production commitments, quarterly performance letters. Protel represents the resulting rate code beautifully, but does not manage the contract layer. That is the space our Corporate Ledger Manager occupies.
The pattern is consistent: Protel handles the operational representation of a rate very well, and leaves the workflows that produce and monitor the rate to you. Whether those workflows live in a spreadsheet, in a Zapier flow, or in a dedicated Weareplonet module is your choice — but they will exist somewhere.