Solutions
Meal delivery scheduling, cut-offs and the calendar problem
Scheduling looks like the simplest part of a meal-plan operation and is quietly one of the hardest, because the calendar a Gulf kitchen runs on is not the one most software assumes.
Four calendars, one operation
These rarely line up, and every mismatch is a box that arrives on the wrong day.
The delivery week
Which weekdays a given customer receives on. Configurable per customer, not per business.
The kitchen week
Which days the kitchen cooks and packs, which can differ from every customer’s delivery pattern.
The local weekend
In much of the Gulf the non-delivery day is Friday rather than Saturday and Sunday. Software that hardcodes a Western weekend produces a week of wrong dates.
The Hijri calendar
Ramadan and Eid move by roughly eleven days each Gregorian year, so they cannot be a fixed annual block in a configuration file.
The cut-off is the most important number in the business
Everything upstream of the cut-off is flexible and free. Everything downstream is committed food, committed labour and committed money. It is the single rule that determines whether a customer request is absorbed or becomes waste.
It should also be visible to the customer. A plan screen that shows which days are still editable and which are locked prevents most of the requests that would otherwise arrive as messages after the fact.
Ramadan is a demand shape, not a holiday
Treating Ramadan as a closure is the wrong model for most Gulf kitchens. Demand does not disappear; it moves. Mornings collapse, evenings surge, and the delivery windows customers actually want shift by hours rather than days.
That means daily demand profiles have to be configurable by season rather than assumed from a single weekly pattern — and it means the schedule, not just the menu, needs to change for a month each year.
Common questions
- How far ahead should delivery days be generated?
- Far enough that customers can see and plan around their upcoming deliveries, and never past the end of the paid term. Generating beyond the term is how kitchens end up cooking for customers who have already finished paying.
- Should the weekend be a global setting?
- It should be configurable per kitchen rather than hardcoded. A business serving the UAE and one serving a different market do not share a non-delivery day, and a hardcoded assumption is invisible until it produces a week of wrong dates.
- What happens to a delivery that falls on a public holiday?
- The calendar should treat it as a blocked day and move or skip the delivery according to a stated rule, so the kitchen is not manually rebuilding a week each time a holiday is announced.
See it running against a real kitchen
The product pages show the actual admin, loaded with a demonstration kitchen — production, packing, routes and the dashboard, exactly as an operator sees them.
Related reading
- SolutionsRoute planning and driver manifests for meal deliveryA meal-plan round is not a set of ad-hoc jobs appearing through the day. It is a known list, knowable the night before — which makes it a planning problem rather than a dispatch problem.
- SolutionsMeal plan software for businesses that sell plans, not mealsA plan is a contract with a shape: a number of meals, a set of delivery days, a term, and a set of rules about what the customer may change and when. Software that does not model that shape will be fought with.
- SolutionsMeal delivery management software for the daily operating rhythmEvery meal-plan business runs the same loop every single day — cook, pack, drive, confirm. Management software earns its place by making the current position of that loop visible without anyone compiling it.
- SolutionsManaging mid-cycle subscription changes without re-typing themSelling the subscription is the easy part. The work is everything that happens after, when a customer changes something and five downstream systems need to hear about it before Tuesday.
- GuidesPlanning a meal-plan operation around RamadanFor a Gulf meal-plan kitchen, Ramadan is the largest single operational event of the year, and the most commonly mishandled — usually because it is planned as a quiet month rather than a different one.
- GuidesManual scheduling versus scheduled by softwareA delivery calendar kept by hand is perfectly workable while everyone receives on the same days. It breaks on variation, and variation arrives with your twentieth customer.