Home › Writing › Planning for Ramadan
Planning for Ramadan: the peak that breaks annual forecasts
Ramadan is the largest demand event of the year for a great many businesses in Saudi Arabia, and it is the one most reliably forecast badly. Not because the peak is a surprise — everybody knows it is coming — but because the tools most planners use are built on a calendar that does not describe it.
Last year's numbers are in the wrong place
The Hijri calendar is lunar, so Ramadan moves roughly ten to eleven days earlier against the Gregorian calendar each year. Over a decade it travels through every season.
This breaks the single most common forecasting method in use, which is to compare a period against the same period last year. Compare March to last March and, depending on the year, you are comparing a Ramadan month to a normal one, a pre-Ramadan build to a post-Eid trough, or two entirely unrelated states of the market. The system reports a variance, someone explains it as a market shift, and a decision gets made on a comparison that never made sense.
Statistical forecasting engines have the same problem. Most seasonality models assume the pattern repeats at a fixed interval in the calendar they were given. Feed one three years of Gregorian history containing a peak that moves eleven days each year, and it will either smear the peak across a wide window or discard it as noise.
Before you forecast anything, realign your history to the Hijri calendar. Index each day by its offset from the start of Ramadan rather than by its Gregorian date, and the pattern that looked like noise resolves into a shape you can plan against.
That realignment is a spreadsheet exercise, not a systems project, and it is the highest-value hour anyone will spend on the annual forecast.
It is three events, not one
Planning Ramadan as a single peak is the second common error. The demand behaves as three distinct phases with different products, different channels and different timing.
| Phase | What happens | Planning implication |
|---|---|---|
| The build | Households and trade stock up in the two to three weeks before Ramadan begins. Staples, pantry goods, bulk formats. | The real demand spike lands before the month starts. Stock has to be in position earlier than the intuitive date. |
| The month | Consumption shifts rather than simply increasing — different categories, different pack sizes, and buying concentrated in the evening. Retail and delivery traffic patterns change completely. | Warehouse and delivery windows have to move with it. Working hours change, so throughput per day falls even as volume rises. |
| Eid and after | A sharp final peak on gifting and celebration categories, then a pronounced trough as demand and much of the workforce disappear at once. | The trough is as important as the peak. Stock left standing after Eid on seasonal lines becomes markdown or write-off. |
The buy happens months before anyone is thinking about it
This is where the calendar problem becomes a supply problem. If a meaningful share of the range is imported, the lead time from supplier commitment to available stock can be sixty to a hundred days once sailing, discharge, customs and conformity are counted.
Work backwards from the build phase rather than from the start of Ramadan and the commitment date lands four to five months ahead — at a point in the year when the commercial team has not yet thought seriously about the campaign, and when asking them to commit to volumes feels premature.
It is not premature. It is the actual decision point, and treating it as one is most of what separates businesses that handle the season well from those that spend it expediting.
What good looks like
- A dated backward plan built from Eid, through the month, to the build, to the in-stock date, to the order commitment date, to the forecast freeze. Published, with owners, before the commitment date rather than after.
- A frozen promotional calendar by an agreed cut-off. Campaigns added after the freeze get supplied from whatever is already committed, and that rule needs to be agreed in a calm month rather than argued during a busy one.
- Allocation rules set in advance. Demand will exceed supply somewhere. Deciding who gets what while it is happening produces decisions driven by whoever escalates loudest.
- Separate treatment for seasonal and staple lines. A staple that overshoots sells through in the following weeks. A seasonal line that overshoots is a write-off, so it deserves a lower service target and a tighter buy.
- An explicit exit plan for the post-Eid trough: what gets marked down, when, and who signs it off. Written before the season, not discovered after it.
- Labour and capacity planned against changed working hours, at the warehouse and with the 3PL. Peak volume against reduced daily throughput is the constraint that quietly breaks the plan.
The measure that matters afterwards
Judge the season on two numbers rather than on revenue alone: service level through the build and the first half of the month, and residual seasonal stock two weeks after Eid. Strong revenue with a large residual is not a good season. It is next year's markdown, booked early.
Record both, alongside what the forecast actually said, while it is fresh. That record is the only real input to next year's plan — and next year, the whole thing arrives eleven days sooner.
Planning the next season?
Send where your dates and commitments currently sit. The first call is thirty minutes and costs nothing.
Start a conversation