01Write the rate table before you open any tool
Automation repeats a decision you have already made, so the decision has to exist on paper first. Build one table. Each row is a season with a start date and an end date. Each column is a room type. Add the rules that sit on top: a weekend or holiday surcharge, a minimum stay, a price for a stay that crosses from one season into the next. If two people on your team give different answers to what a room costs on a holiday weekend, the table is not ready, and an automation would only apply the disagreement faster. Keep the table in one file with one owner. Decide who may change it and when it is reviewed, once a year, before the first season starts.
- One table: season, start date, end date, price per room type
- Rules on top: weekend or holiday surcharge, minimum stay, stays that cross two seasons
- One file, one owner, a named person who may change it
- A yearly review before the first season starts
02What the automation does, and what it checks afterwards
The job itself is small. On the date a season starts, it reads the table, writes the new prices into the system that sells your rooms and records what it changed. The step that matters comes after: it reads the live price back and compares it with the table. A price that did not change is the quiet failure, and nobody notices it until a guest books the old rate or a wrong new one. If the two disagree, it alerts a named person the same day. The same table can feed the price shown on your website, so the page and the booking tool never tell two stories. It can only write to a booking tool that has an API or an import, so ask your supplier before you plan anything.
- On each start date: read the table, write the new prices, log every change
- Read the live price back and compare it with the table
- A mismatch alerts a named person the same day
- Prices on your website come from the same table
- Check first that your booking tool has an API or an import
03Where PROOF48 is the wrong choice for seasonal pricing
We have not built a seasonal price automation, for Santorini Hotel or anyone else, and the case study does not claim one. Our automation page lists booking flows, bots, invoicing, content pipelines and monitoring, with no hotel rate management by name. If your price moves every day with occupancy, you need a revenue management tool, not a rate table, and we do not sell one. If you change prices four times a year, a calendar reminder and a checklist cost nothing and may be enough. If your booking tool has no API or import, nothing can write to it. The AUTOMATE plan is 2,997 EUR a month with two custom automations a month, which suits a business with several flows. One price flow is a standalone build, with scope and price set on request.
- No seasonal price build among our eight published builds, Santorini Hotel included
- A price that moves daily with occupancy needs a revenue management tool, which we do not sell
- A few changes a year: a calendar reminder and a checklist may be enough
- No API or import on your booking tool: nothing can write to it
- AUTOMATE is 2,997 EUR a month with two custom automations; a single standalone flow has scope and price set on request
Where a price table would attach on a hotel build we shipped
Santorini Hotel is a seafront hotel in Eforie Nord on the Romanian Black Sea coast. We built its public website, with rooms, a gallery and contact, and a booking enquiry flow, from one codebase shared with its guest app. The case study lists no seasonal pricing and we have not automated it there, so we have no result to quote. We name the build because the rooms and the enquiry flow are where a rate table would connect.
See the build: Santorini HotelQuestions, answered
Can an automation change prices on every booking site I use?
Only where that site, or your channel manager, accepts changes through an API or an import. We read no supplier documentation for this article, so ask each supplier what it accepts before you plan.
How long does a seasonal price flow take to build?
Our automation page says a single flow takes one to two weeks from mapping to production. The mapping is the main part, because the rate table is the scope.
Does PROOF48 do dynamic pricing for hotels?
No. We build rule-based flows from a table you own. Pricing that reacts to occupancy or to competitors every day is revenue management, a different kind of tool.
Where PROOF48 fits
A small hotel automates seasonal prices by writing one rate table, letting a scheduled job apply it on the dates it names, and reading the live price back to catch a change that did not happen. It needs a booking tool with an API or an import. PROOF48 builds a single flow in one to two weeks, but has not built this one yet.
Cosmin Tiu · Founder, PROOF48
Cosmin has worked in online marketing and software development since 2018, and has built with AI every day since January 2023. He still writes code from scratch daily, in Python, React, Rust and C#. PROOF48 ships business websites in 48 hours and invoices afterwards, so every opinion on this blog was paid for in real builds, not in theory.