In February 2026, as the India AI Impact Summit brought thousands of delegates to Delhi, a suite at the Taj Palace that normally listed for around ₹90,000 a night was quoted at roughly ₹25 lakh. Base rooms at The Oberoi reportedly jumped from about ₹1 lakh to ₹5.6 lakh. Within days, a LocalCircles survey of over 34,000 people found that 71% wanted a cap on hotel room rates during peak demand, and 74% wanted the government to step in.
That’s the risk end of seasonal pricing. Done badly, it looks like opportunism, invites bad reviews, and now, increasingly, invites regulatory attention. Done well, seasonal pricing is just good revenue management: you charge more when demand is genuinely high and less when it isn’t, on a schedule you can defend.
This page sets out how we recommend Indian properties build a seasonal rate calendar, clear bands for peak, shoulder and off-peak periods, grounded in your own data, and where the line sits between “smart seasonal pricing” and the kind of spike that ends up in a newspaper headline.
The three (or four) seasons, defined
Most properties don’t need a complicated model, three or four clearly defined bands cover almost every situation:
- Peak season: Demand consistently outstrips your available rooms, major festivals, wedding season, big local events, school-holiday travel windows, or a destination’s known high season (hill stations in summer, beach towns in winter).
- Shoulder season: The transition periods just before and after peak, demand is healthy but not guaranteed, and a modest rate adjustment (up or down) is usually enough to stay competitive.
- Regular / base season: Your steady-state period, the rate your business case is built around.
- Off-peak season: Demand drops well below your average, often monsoon in many regions, or the local low season for your specific destination.
Not every property needs all four. A budget city-center hotel with fairly flat demand might only need “regular” and “peak” (around one or two big events a year). A hill-station or beach resort with sharp seasonality usually needs all four.
Why seasonal pricing is worth doing properly
The point of seasonal pricing isn’t just “charge more when you can.” It’s matching your rate to demand so you protect revenue during high-demand periods and protect occupancy during low-demand ones. Two numbers matter more than the headline rate:
- RevPAR (Revenue per Available Room), occupancy × average daily rate. This is the number that actually reflects how your pricing decision performed, not the rate on its own.
- The occupancy-revenue trade-off, a lower off-peak rate that fills 80% of your rooms will often out-earn a stubbornly “regular” rate that only fills 40%. Selling a room empty earns you nothing; selling it at a discount still covers your variable cost and contributes to fixed costs.
Track ADR (average daily rate), occupancy and RevPAR from your PMS across at least the last 12–24 months before you set next year’s bands. Guessing from memory is the single biggest reason seasonal pricing underperforms.
How to map your own seasons
Start with your PMS data, then overlay the demand drivers that actually move bookings for your specific property and city:
- National and religious festivals, Diwali (8 November 2026), Christmas and New Year, Holi, Eid, Durga Puja/Navratri, and regional festivals specific to your state.
- School holidays, the summer break (roughly April–June) drives family travel to hill stations and leisure destinations nationwide.
- Wedding season, heavy in most of North India from October through February, a major driver for banquet-capable properties.
- Monsoon, typically July–September in most regions, and a genuine off-peak for many leisure destinations, though it can be a draw for a handful (hill stations marketed on monsoon greenery, for instance).
- Conferences, weddings and events booked at your own property, a single large block booking can justify treating specific dates as “peak” even outside your usual calendar.
- Long weekends and national holidays, Republic Day, Independence Day and Gandhi Jayanti long weekends often spike short-haul leisure travel.
Mark all of these on a single calendar against your last two years of occupancy data. Where a demand driver and a genuine occupancy spike line up, that’s a real peak, not just a date that sounds busy.
How Seasonal Bands Differ by Destination Type
The three-or-four-band structure above is a starting framework, not a fixed template. What actually drives peak, shoulder and off-peak for your specific property depends heavily on what kind of destination you are, and the bands worth calibrating for one type of property can look quite different for another.
Suggested rate bands
These are starting ranges to calibrate against your own market and history, not fixed rules. A well-established resort in a strong peak market can justify the higher end; a city hotel with flatter demand should stay conservative.
| Season | Typical variance from base rate | Notes |
|---|---|---|
| Peak | +30% to +50% | Cap it to a defensible multiple of rack rate, see “Where the line is,” below. |
| Shoulder | ±10% to 20% | Adjust up or down based on real-time pickup, not just the calendar. |
| Regular / base | Base rate (anchor) | Your anchor rate, the one your business case and rack rate are built on. |
| Off-peak | −20% to −50% | Never sell below your variable cost per occupied room. |
A worked example
Take a property with a base rate of ₹4,000 for a standard double. Applying the bands above across a real calendar might look like this:
| Period | Band | Variance | Rate charged |
|---|---|---|---|
| Diwali week (5–10 Nov 2026) | Peak | +40% | ₹5,600 |
| October (pre-Diwali run-up) | Shoulder | +15% | ₹4,600 |
| Rest of the year | Regular | Base (anchor) | ₹4,000 |
| Monsoon (July–August) | Off-peak | −30% | ₹2,800 |
Notice the peak rate here is 1.4× the base rate, well inside the “roughly 2x rack rate” ceiling that even survey respondents who support price caps considered acceptable (see below). That’s the kind of headroom a defensible peak band should leave you.
Why a Single Flat Rate Can’t Do What Seasonal Bands Do
It’s worth asking whether seasonal banding is worth the setup effort compared to simply picking one flat rate for the whole year. The honest answer is that a flat rate cannot avoid a trade-off that seasonal banding solves directly: any single number is either too high for your quiet months or too low for your busy ones, there is no flat rate that gets both right.
Take a 10-room property using the same numbers as the worked example above, a ₹4,000 regular rate, a ₹5,600 Diwali-week peak, and a ₹2,800 monsoon off-peak. Set a flat rate at ₹4,000 year-round, and during Diwali week, when the property would comfortably sell out even at ₹5,600, that extra ₹1,600 per room per night is given away for every room, every night of the peak period. Across a 10-room property over a 7-night peak week, that is roughly ₹1,12,000 left on the table for that single week alone.
Now set the flat rate at ₹5,600 instead, to try to capture that peak value. During the monsoon off-peak, this now-too-high rate suppresses occupancy exactly when a lower rate would fill rooms that would otherwise sit empty. Even a modest drop in bookings, losing just two or three rooms most nights because the rate no longer looks competitive for a quiet month, costs more than the extra per-night rate could ever make up, since an occupied room at a fair off-peak rate still earns far more than an empty one earns at any rate.
Seasonal banding is really just an acknowledgement that demand for the same room genuinely changes for predictable reasons, festivals, school holidays, monsoon, and weekday business travel among them, and pricing that ignores this either leaves money on the table when demand is strong or suppresses bookings when demand is weak. Setting up bands takes a few hours once a year. The trade-off it avoids runs for the full year.
Where the line is: seasonal pricing vs. surge pricing
There’s currently no blanket law capping what an Indian hotel can charge for a room, pricing your own inventory is legal. But “legal” and “safe to do” aren’t the same thing, and the direction of travel is clear:
- The February 2026 Delhi price spikes (Taj Palace suites reportedly quoted near ₹25 lakh, up from about ₹90,000; The Oberoi’s base rooms near ₹5.6 lakh, up from about ₹1 lakh) triggered national coverage and a LocalCircles survey of 34,000+ respondents.
- 71% of respondents wanted a cap on hotel rates during peak demand; 74% wanted government intervention; 39% specifically wanted a regulator under the Ministry of Tourism.
- Among those who wanted a cap, the most common answer was that peak rates shouldn’t exceed roughly twice the rack rate, a useful, if informal, benchmark.
- The Central Consumer Protection Authority (CCPA) has already shown it’s willing to intervene directly in hotel and restaurant pricing practices, it issued binding guidelines against mandatory service charges, and separately advised against hidden fuel/gas surcharges on bills. Guest-facing pricing fairness is squarely on its radar.
None of this makes a 20x spike illegal today. But it tells you what guests, the press and regulators consider defensible. Our recommendation: keep your peak-season ceiling within a clearly explainable multiple of your published rack rate, most properties should stay well under 2x, and be able to point to a real demand driver (a citywide event, a major festival, a genuine sellout) for every peak rate you charge.
Keep every channel in sync
Whatever band you’re in, apply it everywhere at once. Update your PMS, channel manager and direct-booking rate together on the same day you move to a new season, a stale rate on one OTA while others have moved is the most common cause of rate-parity disputes and OTA penalty flags. If you don’t use a channel manager, keep a simple shared checklist of every channel that needs a manual update and go down it in one sitting.
Setting Up Seasonal Rates in Your PMS and Channel Manager
Most PMS platforms and channel managers support seasonal rate plans natively, date-range-based rates that automatically apply the right band without you having to manually update prices every week, but setting this up correctly the first time avoids a few common technical mistakes.
Load your full year of bands as date ranges in one sitting, rather than updating rates week by week as each season approaches. A pre-loaded calendar removes the risk of forgetting to switch a rate on time, which is one of the most common causes of a stale price sitting on one OTA while your other channels have already moved to the new season.
Consider a minimum-stay restriction during your clearest peak periods, a two or three-night minimum around a major festival or a sold-out weekend protects you from a guest booking just the single highest-demand night and leaving the adjacent lower-demand nights harder to fill around a short gap.
If you use a channel manager to push rates across OTAs, confirm it is actually syncing your full seasonal calendar and not just today’s rate, some channel managers sync current availability and price in near real time but require the full future rate calendar to be loaded separately or on a longer sync cycle. Check a date several months out on each OTA against your own calendar before relying on it.
Finally, build in a buffer day or two at each edge of a peak band rather than a hard cutoff. A guest arriving the day before your official peak period starts, or departing the day after it ends, should usually see a shoulder rate rather than snapping straight from peak to regular, a hard cliff at the edge of a band is one of the more common sources of a guest feeling the pricing is arbitrary.
How to put this into practice
- Pull 12–24 months of ADR, occupancy and RevPAR from your PMS, broken down by month or week.
- Mark every known demand driver on a single calendar, festivals, school holidays, wedding season, local events, monsoon.
- Match drivers to real occupancy spikes and dips in your data, only treat a date as “peak” if the numbers back it up.
- Assign each period a band (peak / shoulder / regular / off-peak) and a rate, using the ranges above as a starting point.
- Load the full-year calendar into your PMS or channel manager so rates change automatically rather than relying on someone remembering to update them.
- Keep a one-line written note for every peak rate, what drove it, and how it compares to your rack rate. This is your answer if a guest complains or a platform flags the rate.
- Review quarterly against actual pickup and adjust next year’s bands, seasonal pricing is a living document, not a one-time setup.
Coordinating Seasonal Bands With Discounts and Promotions
Seasonal bands and promotional discounts serve different purposes, and it is worth keeping them separate rather than letting them stack on top of each other without noticing.
A seasonal band already reflects real demand, an off-peak rate is discounted because demand is genuinely lower, not because you are running a promotion. Layering a further percentage-off promotion, an early-bird discount, or an OTA-driven flash sale on top of an already-discounted off-peak rate can push you well below what the room actually needs to earn to cover its marginal cost, housekeeping, linen, utilities, a share of fixed costs, especially once an OTA’s own commission is deducted from whatever is left.
Before running any promotion, check what band it will land on. A discount applied during a genuine peak period usually has room to work with, you are discounting from an already-strong rate. The same discount applied during off-peak, on top of a rate that is already reduced for the season, deserves a second look before you commit to it.
If you do want to run occasional promotions, it is simpler and safer to base them on your regular or shoulder rate rather than your lowest off-peak rate, and to cap how far any single promotion can push the effective price below your calculated cost floor for that room.
Common mistakes
- Setting rates on gut feel instead of occupancy history, the biggest single cause of underperforming seasonal pricing.
- Treating seasons as strictly binary, real demand has gradients; shoulder-season nuance usually captures more revenue than a flat peak/off-peak split.
- Ignoring the occupancy-revenue trade-off, a full hotel at a fair discount usually beats a half-empty hotel at “regular” rate.
- Selling below variable cost in the off-season just to show occupancy, know your per-room variable cost before you discount.
- Uncapped peak pricing with no rack-rate anchor, the fastest way to end up in a screenshot on social media.
- Letting a peak bump silently cross a GST slab without adjusting your billing or pricing displayed to guests.
- Updating rates on your website but not your OTAs (or vice versa), creates rate-parity flags and guest confusion.
Explaining a Peak Rate to Guests Without It Feeling Like a Surprise
A guest who understands why a peak rate is what it is tends to accept it far more readily than one who feels blindsided by it. A short, consistent message at the right moment does most of the work.
Keep the same numbers and the same reasoning across your website, WhatsApp and every OTA listing message. A guest who sees a consistent explanation, rather than a rate that simply appears different depending on where they look, is far less likely to read it as unfair.
A few common scenarios
Quick checklist
- Pulled 12–24 months of ADR, occupancy and RevPAR data
- Mapped festivals, school holidays, wedding season and local events onto a calendar
- Matched demand drivers to real occupancy spikes, not assumptions
- Set peak / shoulder / regular / off-peak bands with specific rates
- Kept peak rates within a defensible multiple of rack rate
- Checked peak and off-peak rates against GST slab thresholds
- Loaded the full-year calendar into the PMS / channel manager
- Confirmed rates match across OTAs and direct booking
- Wrote a one-line justification for each peak-season rate
- Scheduled a quarterly review against actual pickup
Reviewing and Adjusting Your Bands Mid-Year
A written seasonal calendar is a plan, not a permanent commitment, and it is worth building in a deliberate way to revisit it rather than treating every band as fixed for all time.
If a band that you expected to sell out at your planned peak rate is running noticeably under-occupied a few weeks out, that is useful information, not a reason to panic and discount immediately. Check whether the shortfall is specific to this year, a weaker festival calendar, unusual weather, a competing new property nearby, before assuming your rate itself is the problem. A modest, planned adjustment is very different from an ad hoc panic discount applied the week of arrival.
The reverse also happens: an unplanned local event, a wedding, a corporate offsite, a sudden spike in a nearby city’s business travel, can create real peak-level demand outside your usual calendar. Treating a genuine, data-backed spike as a one-off peak band, priced the same defensible way as your planned peak periods, is reasonable. Treating every unusually busy week as an excuse to price opportunistically is exactly the pattern that invites the guest backlash and regulatory attention this page opened with.
Set a fixed time once a year, most properties do this shortly after their highest-demand season ends, to review actual pickup and occupancy against your planned bands and adjust next year’s calendar. This keeps your rate calendar a living document grounded in real data, rather than a one-time exercise that quietly goes stale.
How OpenStays fits in
OpenStays helps independent hotels and small chains run day-to-day operations without needing a dedicated revenue manager, from guest ID and compliance workflows to the kind of rate and calendar discipline this page recommends. If you’re building your first seasonal rate calendar or tightening up an existing one, our team can help you set it up against your own occupancy history.
- Peak / shoulder / off-peak band reference
- Month-by-month calendar grid
- A4, ready to fill in
Frequently Asked Questions
How much should I raise prices in peak season?
Most Indian properties do well with peak rates 30–50% above their base rate, calibrated to their own occupancy history. Keep the peak rate within a defensible multiple of your published rack rate, well under 2x is the safer zone.
Is surge pricing legal in India?
There’s no blanket law capping hotel room rates today, so pricing your own inventory is legal. But public sentiment and regulatory attention are building, a 2026 survey found 71% of Indians want caps on peak-demand hotel rates, and the consumer protection authority has already intervened in other hotel pricing practices. Treat “legal” and “defensible” as two different bars to clear.
Do I need to change rates on OTAs and my direct site at the same time?
Yes. Updating one channel and not another is the most common cause of rate-parity disputes and OTA penalty flags. Change every channel on the same day, ideally through a channel manager.
What counts as off-season for my property?
It depends entirely on your destination and guest mix, monsoon is off-peak for many leisure destinations but can be a selling point for others. Use your own 12–24 months of occupancy data rather than a generic calendar.
Will seasonal pricing affect my GST slab?
It can. Hotel GST in India is a two-tier structure: up to ₹7,500 a night is 5% (no ITC), and above ₹7,500 is 18% (with ITC), once you’re registered for GST at all (below the ₹20 lakh turnover threshold, ₹10 lakh in some special category states, no GST applies regardless of tariff). A seasonal rate change that crosses the ₹7,500 threshold changes the tax you charge and your input tax credit eligibility, so check it before you finalise a new band.
How often should I update my rate calendar?
Build it once a year ahead of your next cycle, then review it quarterly against actual pickup and adjust the following year’s bands based on what you learn.
Should seasonal bands differ by room type within the same property?
Yes, if occupancy patterns genuinely differ. A property with both standard and premium rooms often sees the premium rooms sell out faster in peak season, which can support a slightly wider peak variance on that room type. Keep the same underlying band structure, peak, shoulder, regular, off-peak, across all room types so the calendar stays simple to manage, and adjust the percentage rather than inventing a separate calendar per room type.
What if a festival date changes from year to year, like Diwali or Eid?
Update your calendar every year rather than reusing the previous year’s exact dates. Festivals that follow a lunar or regional calendar, Diwali, Eid, Holi among them, shift by weeks each year, and a rate calendar built on last year’s dates will misprice the actual peak. Check the confirmed date for the coming year when you build your annual calendar, not an approximate month.
Can I set a peak rate that applies only to weekends within a broader season?
Yes, and many properties do exactly this. A destination can have a genuine season, say winter for a beach property, while still seeing meaningfully higher demand on weekends within that season than on weekdays. A weekend sub-band layered on top of your seasonal bands is a reasonable refinement once your basic three or four-band structure is working well.
Does seasonal pricing apply to long-stay or corporate bookings the same way?
Not usually in the same form. Long-stay and corporate rates are typically negotiated separately and held stable for the length of an agreement, rather than fluctuating with your short-stay seasonal bands. It is still worth reviewing these negotiated rates against your seasonal calendar periodically, so a long-stay guest is not paying meaningfully more, or less, than what the same room would earn from short-stay bookings during the same period.
Should a new property with no occupancy history still use seasonal bands?
Yes, start with published tourism-board or industry data for your destination type and region as a rough guide, hill-station summer peaks, coastal winter peaks, festival calendars, then build your own bands from real bookings as soon as you have a season or two of data. An estimated calendar based on your destination type is still far better than a single flat rate for a new property, and you can tighten the bands once your own occupancy history comes in.
How do I handle a guest who booked before a rate change and now sees a different price?
Honour the rate the guest actually booked and paid at, changing it after the fact, in either direction, is a fast way to lose trust regardless of which way the change goes. If you do increase a band’s rate partway through the year, apply it only to bookings made from that point forward, and keep a note of when the change took effect so front-desk and reservations staff can answer questions about it consistently.
Is it worth paying for revenue management software to do this instead of a manual calendar?
For most independent hotels and homestays, a well-maintained manual calendar built from your own PMS data covers the large majority of the benefit, dedicated revenue management software adds the most value at larger properties with complex, fast-moving inventory across many room types and channels. Start with a manual calendar, reviewed and adjusted annually as described above, and consider dedicated software later if your property’s size and complexity genuinely outgrow what a spreadsheet and a channel manager can handle well.
Do OTA rate parity requirements limit how much I can vary my rates seasonally?
No, rate parity clauses require that the same room and dates cost the same across your direct channel and each OTA, they do not restrict how much your rate can change from one date to another. You can move freely between peak, shoulder, regular and off-peak bands as the calendar dictates, as long as every channel reflects whichever band applies on a given date at the same time, updated together rather than one channel lagging behind the others.
Summary
Seasonal pricing done right is just good revenue management: bands based on your own data, rates that stay in sync across every channel, and peak pricing you can explain. Done as ad hoc surge pricing with no ceiling, it risks the guest backlash, and increasingly, the regulatory attention, that a handful of Delhi hotels ran into in February 2026. Build your calendar once, keep it inside a defensible multiple of your rack rate, and review it every quarter.
This page reflects our recommendation on pricing strategy and general practice, not legal, tax or financial advice. GST rates, slab thresholds and regulatory attitudes toward guest pricing can change, and the right bands, rates and multiples for your property depend on your own cost structure, market and occupancy history. Please consult a qualified professional before finalising your seasonal rates or tax treatment.