Bayram and public holidays: planning 2027 rates and restrictions early

Bayram pricing means setting rates and restrictions by the legal holiday calendar, not by last year's dates. In 2027 Ramazan Bayramı runs 9 to 11 March and Kurban Bayramı 16 to 19 May, each starting at 13:00 on its eve (Law No. 2429; Diyanet 2027 calendar). Set period boundaries, minimum stays and contract dates on those dates now.

Every year the same thing happens: the rate sheet still carries a period called "bayram" with last year's dates inside it, and an agency contract still ends on a day that is no longer a holiday. The holidays move. The paperwork does not. This article gives you the legal durations, the 2027 dates, and a working method for holiday pricing: where to put period boundaries, how to set minimum stays without creating orphan nights, how to plan for a bridge day that may never be announced, and how to review the holiday afterwards on nights that actually compare.

What does Turkish law actually set for bayram holidays?#

Law No. 2429 sets the length of each bayram and the hour it starts: Ramazan Bayramı lasts 3.5 days and Kurban Bayramı 4.5 days, and both begin at 13:00 on the eve (arefe), according to the consolidated text of the law on the Presidency's Mevzuat Bilgi Sistemi (July 2024).

Read the half day literally. 3.5 days means 13:00 on the eve plus three full days; 4.5 days means 13:00 on the eve plus four full days. The eve is legally half a holiday but commercially a full room night, because the guest sleeps in the hotel and is usually there for dinner.

The other general holidays are fixed dates: 1 January, 23 April, 1 May, 19 May, 15 July, 30 August and 29 October, the last starting at 13:00 on 28 October. Only the two bayrams move. They move because the religious calendar is shorter than the Gregorian year, so the bayrams land roughly eleven days earlier each year. That single mechanism is why last year's period boundaries are wrong this year.

The law defines the holiday, not the commercial terms. Room rates, minimum stays, deposit rules and cancellation terms are the hotel's decisions, and the calendar only tells you which nights they apply to. In operations, treat the eve as its own named date: rota, restaurant covers, arrival staffing and the rate period should all reference 8 March and 15 May explicitly, not "the day before bayram".

When are the 2027 bayram dates?#

In 2027 Ramazan Bayramı runs from Tuesday 9 to Thursday 11 March with the eve on Monday 8 March, and Kurban Bayramı from Sunday 16 to Wednesday 19 May with the eve on Saturday 15 May, according to the Presidency of Religious Affairs' 2027 religious days calendar (Diyanet, November 2026).

The Ramazan block: the eve is Monday 8 March from 13:00, then Tuesday 9, Wednesday 10 and Thursday 11 March. Thursday 11 is the last holiday day, so the first working day after it is Friday 12 March.

The Kurban block: the eve is Saturday 15 May from 13:00, then Sunday 16, Monday 17, Tuesday 18 and Wednesday 19 May. The last day falls on 19 May, which is itself a general holiday, so the block ends on a public holiday and the first working day is Thursday 20 May.

The weekend geometry differs between the two. Ramazan's eve is a Monday, so a normal weekend sits just before it. Kurban's eve is a Saturday, so the eve itself is a weekend night and the arrival pattern will not repeat.

Count nights, not days. The Ramazam period touches the nights of 8, 9, 10 and 11 March; the Kurban period touches the nights of 15, 16, 17, 18 and 19 May. The last night of each is followed by a departure, and it is usually the weakest night of the block.

Dates from the Diyanet 2027 calendar; durations from Law No. 2429. Read the two sources together and never one alone: the Diyanet calendar gives the religious dates, Law No. 2429 gives the legal duration and the 13:00 start. A rate sheet built from only one of them will be wrong at the edges.

Where do period boundaries belong in the rate sheet?#

Boundaries belong on exact dates and on the night, not on the day: a peak period should start with the night of the eve and end with the last night you intend to sell at the peak price.

Name every period by its date range, never by a label. A period called "Bayram" survives into next year with the old dates inside it; a period called "08.03.2027 to 11.03.2027" cannot.

Decide the eve night explicitly. The law makes it half a day from 13:00, but the room is sold for a full night, often with dinner, and demand for it can be as strong as any holiday night because guests want to wake up in the hotel.

Decide the last peak night explicitly too. For Kurban, the night of Wednesday 19 May is followed by a working Thursday, so it may deserve a lower rate or a shorter minimum stay than the nights before it. Price the night before the eve as shoulder, not peak: the nights of 7 March and 14 May are ordinary nights that fill late if they fill at all, and pricing them as peak simply leaves them empty.

Make the same boundaries appear in every system that sells: the property management system, the channel manager, the hotel's own website and every agency contract. One mismatched boundary creates a cheap rate inside a peak period, and it will be found. Open every contract that refers to "bayram", "religious holiday" or "high season" in general words and replace the wording with the 2027 dates, including the release period attached to each block, as covered in detail in hotel allotment contracts: release periods and clauses to check.

How should minimum stay and orphan nights be set around a bayram?#

Set the minimum stay on the nights the holiday actually creates, and check what it does to the nights on either side, because a minimum longer than the remaining holiday nights strands a night nobody can book alone.

An orphan night is a night trapped between two minimum-stay blocks, or left over at the end of one, that no guest can book on its own. It is created by the restriction, not by the market.

For example, a hotel sets a three-night minimum from 15 to 18 May. A guest who wants only the night of 19 May can still book it, but a guest who wants 18 and 19 May cannot, because 18 May sits inside the block. Shortening the minimum on the last night releases that pair.

Know the three tools and what each does: closed to arrival blocks a check-in on that date; closed to departure blocks a check-out on that date; minimum stay through requires every booking that touches the period to cover a set number of nights. Each one solves a different problem and creates a different orphan. The mechanics are covered in hotel rate restrictions explained: minimum stay, CTA and CTD.

Protect the eve arrival. Many domestic guests leave work at midday on the eve and drive; a closed-to-arrival flag on the eve night blocks exactly the arrival the holiday generates. Watch the departure side when the holiday ends on a public holiday: with Kurban ending on Wednesday 19 May, departures concentrate on 19 and 20 May, and a closed-to-departure flag on 19 May pushes guests to leave a night early and costs a room night.

Review restrictions during the period, not only before it. A minimum stay set in February can be wrong by April, and the cost of a wrong restriction is invisible unless someone looks at arrivals turned away.

Do domestic and foreign demand land on the same dates?#

Not necessarily: bayram is a domestic travel calendar, while foreign demand follows its own school holidays and booking windows, so the same week can be peak for one segment and shoulder for the other.

Domestic bayram demand has a short booking window, travels in families and groups, arrives on the eve and leaves on the last day. It is price-sensitive on the edges and much less so on the core nights. Foreign demand is booked earlier and often arrives through contracts and agencies with their own fixed periods, which may sit in July and August or around the source market's own holidays rather than in March or May.

The risk is a single rate period applied to every channel: it can price foreign business out of a week that is not its peak, or sell rooms cheaply to a segment that would have paid more on the core nights. Segment by market and channel while keeping the same date boundaries. Different rate codes and different conditions on the same nights are normal; different date boundaries across channels are not.

Check whether each agency contract defines its own high season that overlaps, misses or partly covers the bayram dates, and whether its release period still makes sense once the dates move. Refuse the assumption that a holiday fills a hotel. The pattern differs by destination type, and the only evidence that counts is your own booking pace on your own dates. How early to commit inventory is a separate question, covered in early booking and non-refundable rates: when do they pay off?.

What changes if a bridge day is announced?#

Nothing in the system should have to change, because no 2027 bridge-day or administrative-leave decision is verified: build the rate sheet so that both cases can be sold without rewriting it.

A bridge day is administrative leave (idari izin) that joins a holiday to a weekend. It is a decision, not a calendar fact, and it can be announced late, sometimes close to the date.

Split the calendar into core nights, which the law fixes, and candidate nights, which only exist if a bridge is announced. For example, the nights of 7 March, 12 March, 14 May and 20 May are candidates, not certainties. Keep candidate nights on flexible rates and flexible restrictions: a non-refundable-only inventory on a night that may or may not become a holiday either scares demand away or locks you into a price you would not have chosen. Keep allotments on candidate nights short, with release periods that let rooms come back to you if demand spikes after an announcement.

Do not pre-price a bridge day. Pricing a holiday that does not exist yet either discourages the ordinary demand that would have filled the night or gives rooms away before the demand appears. Decide in advance who checks for an announcement, who edits the rate sheet and how quickly it can be done, so the answer is a procedure rather than a scramble.

How do you review the holiday afterwards?#

Compare on aligned holiday nights, not on calendar dates: because the bayrams move, last year's 9 March was not a holiday, so a date-to-date comparison measures the calendar rather than your pricing.

Align by position in the holiday: eve night, first holiday night, middle nights, last holiday night, first working night after. Compare night for night, not date for date. Read booking pace, not only rooms sold at the end; the method is described in the hotel pickup report: how to read booking pace day by day. The useful question is when the rooms came in, and whether a restriction was still blocking arrivals at the moment demand peaked.

Look at the edges first, because that is where the money sits: the night before the eve, the last holiday night and the first working night after. Core nights usually sell themselves; edges do not. Pull the restrictions log for the period and price what each minimum stay and each closed-to-arrival flag cost in arrivals turned away. Write the finding next to the rate period itself, so next year's planner starts from evidence instead of from memory.

What to do next#

Open the 2027 rate sheet, replace every label such as "bayram" with the 2027 date ranges from the Diyanet calendar and Law No. 2429, then open the agency contracts and do the same. Everything else in this article follows from that one correction: minimum stays and orphan nights can only be judged against correct boundaries, segment pricing only works when the dates are right, bridge days can only be handled as two scenarios once the core nights are fixed, and the post-holiday review only means something when last year's nights are aligned by holiday position rather than by date.