Loading next season's rates: the order that avoids selling old prices on new dates
Follow a strict sequence to load next season's rates without errors. Close dates first, load new prices, and verify each channel before opening to protect revenue.
Contents
Key takeaways
- Rates and availability are separate records: a date left open keeps selling at whatever price is still attached to it.
- Close first, load second, open last; closing a date is reversible in a minute, a booking taken at the wrong price is not.
- Check each channel the way a guest sees it, on the first night, a mid-season night and the last night, before opening the rest.
- A test booking proves the whole path: the price, the terms, the confirmation and the rate code that arrives in the hotel's system.
- A channel that shows no change after an upload is a signal to check, not proof that nothing happened.
Close the new dates on every channel first, then load the season's rates in the hotel's own system, check each channel as a guest would see it, open a small slice, make a test booking, and review on day two. A stop sell is a closed date: no channel can sell it at any price.
The season's rates are typed, saved and sent. Two days later a booking arrives for a date in the new season at last year's price, because that date stayed open the whole time the new rate was on its way. The order of a hotel season rates upload across channels is what decides whether this happens. After reading, you will have a step-by-step sequence, the checks to run per channel, and a day-two review that catches what slipped through.
Why does the order of a season rate upload matter?
Because a rate and a date are stored as two separate records. Opening a date before its new price arrives leaves the date selling at whatever price is still attached to it.
Availability is an open or closed flag on a date; the price is a value attached to a room type and rate plan. Changing one does not change the other. The dangerous window is the gap between typing the new rate and that rate reaching each channel: every booking that arrives inside the gap is priced by the old record. And each channel receives and displays updates on its own schedule, so the gap is not one moment but several, one per channel.
A wrong-price booking is not only a refund question. It holds a room, may carry a cancellation term, and reaches the guest as a confirmation the hotel has to stand behind or renegotiate. The two mistakes are not equal: a date closed a day too long costs some pickup; a date sold at last season's price costs the room and a conversation with the guest.
The price itself is decided before any of this, in a separate exercise about costs, contracts and currency, starting with setting next season's price rise before the rates are loaded. The upload only carries a decision that is already made. Order is the one part of the process the hotel fully controls, because the timing of the channels is not.
Watch outThe old rate does not delete itself
Typing a new rate does not delete the old one. The old price stays live on every date that is still open until the new rate actually reaches that channel.
Should you close the dates before loading new rates?
Yes. Close the date range first, load the rates second, open last. Closing is the only step that can be undone in a minute without a guest noticing.
First decide what you are closing. A stop sell closes the date for sale on that room type, whatever the rate plan; closing a single rate plan leaves the other plans on that date selling normally. Match the closure to the change: if the whole season's pricing changes, close the dates; if one plan changes, close that plan and leave the rest. This is the same logic that governs closing dates for winter without losing next season.
Close in the hotel's own system, not channel by channel in each extranet. One action in the source reaches every channel through the channel manager, and one list of what was closed stays in one place. Do not close more than the change needs: every extra closed night is pickup the hotel cannot get back.
Write the closure down: the exact first and last night, who closed it, at what time, and which channels confirmed it. That note becomes the reopening plan. Confirm the closure the way a guest would, with a search on the channel, not by reading a status field in the extranet. Closing is also the correct first move when a mistake is found later: close, correct, then reopen.
ChecklistBefore you type a single new rate
- List the exact date range the new rates cover, first night and last night included
- Decide whether you are closing the whole date or one rate plan, and write the choice down
- Close the range in the hotel's own system so the channel manager carries it to every channel
- Confirm the closure on each channel with a guest search
- Note who closed it, at what time, and which channels confirmed
- Keep the list as the reopening plan
How do you load and check rates one channel at a time?
Type the season's rates once in the hotel's own system, let the channel manager distribute them, then verify each channel separately by looking at what a guest sees there.
One source of truth: the hotel's own system holds the rate, and the channel manager copies it outward. Rates typed directly into a channel's extranet become a second source that will disagree later. Mapping comes before loading: every room type and rate plan must be matched to the channel's own codes, and an unmatched plan either keeps its old price or stops selling, with neither showing up as an error. The mechanics of this are covered in mapping room types and rate plans before a rate upload.
Check three dates per channel: the first night of the season, a mid-season night, and the last night. Season boundaries are where date ranges are most often off by one. Check the parts that change the total: taxes and fees, board type, cancellation terms, and whether the channel displays a per-night or a per-stay figure. Check the currency the guest will be charged in, not only the currency the hotel typed.
Log every check with the date, the channel, the room and plan, the price seen and the person who looked. A check nobody recorded cannot be repeated or trusted. Do this for every channel you intend to open, slowest channel included.
For example, a check log might look like this (illustrative rows only):
| Date checked | Channel | Room and plan | Price seen | Matches | Checked by |
|---|---|---|---|---|---|
| 01.03.2027 | Channel A | Double, BB | 145 | Yes | A.Y. |
| 15.07.2027 | Channel A | Double, BB | 190 | Yes | A.Y. |
| 31.10.2027 | Channel A | Double, BB | 160 | No, old price | A.Y. |
How should you open dates in steps?
Open a small slice first, confirm it on every channel, then open the rest. A staged opening limits what one mistake can cost to a few nights instead of a season.
Choose the slice by risk: the nearest dates, or one short block inside each month, so a wrong price is caught on a handful of nights. Keep the rest closed until the slice is confirmed everywhere; the closed dates are the safety net, not a loss. Open in the same order you closed: the hotel's own system first, then confirm the change reached each channel.
Open the slowest channel last and check it before the full opening, because a channel that lags is the one that will still show the old price after everything else has moved. Coordinate with contracts and campaigns: opening dates before tour operator contracts or early-bird offers go out avoids a published price with no rate behind it. Name who is allowed to open the full season; a staged opening only works if the last step is a decision, not an accident. The same staging applies to reopening a seasonal hotel in the last four weeks, where the first sellable dates carry the most scrutiny.
TipOpen a slice, not the season
One short block per month gives you the same information as a full opening and a fraction of the exposure.
What does a test booking prove?
It proves the whole path works: the price the guest is charged, the terms shown, the confirmation sent, and the reservation arriving in the hotel's system with the right rate code.
Book on the channel itself, as a guest would, not through a preview screen or an admin view. The admin view shows what the hotel set; the guest view shows what the channel sells. Use a date inside the newly opened slice, a real room type, and the occupancy and board type you sell most.
Check four things, not one: the amount charged, the cancellation terms shown, the content of the confirmation, and whether the reservation appears in the hotel system under the correct rate code. The rate code matters as much as the number: a booking that shows the right price under the wrong code will misreport in every later report. Cancel inside the free window and confirm the room returned to inventory; a test booking that never releases its room is a real loss. Repeat on every channel you opened, starting with the one that updates slowest.
ChecklistFour checks on every test booking
- The amount charged matches the loaded rate
- The cancellation terms shown match the plan
- The confirmation carries the right dates, room and board
- The reservation lands in the hotel's system with the correct rate code, and the room returns to inventory after cancellation
What should the day-two review check?
Compare what sold with what should have sold, and look hardest at the channels that appear not to have changed at all.
Pull every booking taken since the opening and check its rate against the source, one line per booking, with the channel and the rate code. Look specifically for bookings priced at last season's figure: same room type, new dates, old price. These are the ones to resolve first.
Treat silence as a signal. A channel that shows no change after an upload may not have received the update, and no bookings there is not the same as no demand. Compare the closed and open lists against the plan: dates still closed that should be open, and dates open that should never have been.
Correct in the same order as before: close, fix, confirm, reopen. Editing a live price on an open date in the middle of the day is how a second wrong-price sale happens. Write down where in the order the failure occurred, because that is the step to change next season.
Key pointSilence is a question, not a result
No change on a channel is a question, not a result. Check it before you conclude the season opened correctly.
What to do next
Write the order down for your own hotel before the next season's rates are due: one page naming the date range, who closes, who loads, who checks each channel, who makes the test booking, who opens the full season and who runs the day-two review. The order is what protects the price; the price itself is a separate decision, and the check is what proves the order was followed.
If you are evaluating whether your systems support this sequence, a hotel operating system that holds rates and availability as one source, and a distribution setup that carries changes outward from it, are the two pieces to look at.
Frequently asked questions
What is the difference between a stop sell and closing a rate plan?
A stop sell closes the date for sale on that room type whatever the rate plan, while closing a rate plan leaves the other plans on that date selling. Choose by what actually changed: a whole-season price change needs the dates closed, a single plan change needs only that plan. Confirm the effect on each channel with a guest search rather than a status field.
Can next season's rates be loaded to all channels at once?
The hotel types the rates once in its own system and the channel manager distributes them, so the loading can be one action. What cannot be one action is the checking: each channel receives and displays the update on its own schedule, so verification stays per channel. Loading at once is fine; assuming it arrived everywhere is not.
What should a hotel do if a guest books at last year's price?
The hotel's own written rule should already say who may approve honoring a mispriced booking, how the guest is told, and what the channel contract says about mispriced reservations. Decide this before the season, not during the conversation. Read the channel contract terms and take the hotel's own case to its adviser.
How far ahead should next season's rates be loaded?
Early enough that no contract, campaign or early-bird offer for that season goes out before the rate behind it exists. A published offer with no loaded rate is what forces a rushed upload later. The hotel sets its own calendar against its own sales cycle; there is no single figure that fits every property.


