Running weekday and weekend meal plans from one Shopify store: what operators get wrong
You started with one plan — seven days, one menu, one cutoff. Then a Gurugram office park subscriber asked if they could skip the weekend since nobody's home Saturday-Sunday, and you built a second plan: five days, Monday to Friday. Now you're running both from the same Shopify store, and you assumed the second plan would be a smaller version of the first. It isn't — it behaves like a different business wearing the same storefront.
The single-cutoff mistake is the most common one. Most operators set one cutoff time — Saturday 10 PM — and apply it to every plan on the store, because that's how the first plan was configured and nobody revisited it. For a 7-day family plan starting Monday delivery, Saturday 10 PM works fine; there's a full day of buffer before the Monday prep run. But a 5-day weekday plan is delivering the exact same Monday, and its prep sheet needs to be finalised on the exact same Saturday-night-into-Sunday window. Both plans compete for the same kitchen prep slot, and the operator who assumed a single cutoff would keep things simple ends up with two prep sheets colliding at 6 AM Monday instead of one clean one.
The fix is per-plan cutoff configuration, not a shared one. MealDispatch lets you set cutoff per-plan, per-zone, per-day — which means the weekday office plan and the weekend family plan can each have a cutoff timed to their own delivery cadence instead of inheriting whichever one you configured first. An operator running a Noida Sector 62 office-lunch plan alongside a Dwarka residential plan doesn't need to force both into the same Saturday 10 PM slot; the office plan can close earlier in the week if that's what the kitchen's prep timeline actually needs.
Fallback rules are the second place dual-plan operators trip up. A single fallback policy applied across both plans creates weekly complaints from whichever group it doesn't fit. Office subscribers on a 5-day weekday plan are frequently on the move — client visits, off-sites, half the team in Bangalore for a sprint review — and for them, skip is usually the right default when they miss a selection window: no delivery, no charge for that day, no surprise tiffin sitting outside a locked office desk. Apply repeat-last-week to this plan instead and you get tiffins delivered to an empty desk on a day someone's in Pune for a client meeting.
Family subscribers on a 7-day plan are the opposite. They're usually home, their preferences are stable week to week, and repeat-last-week is what they expect when they forget to pick. Apply skip to this plan instead and you get a subscriber who forgot to pick on a Thursday going hungry on Friday and messaging you annoyed.
MealDispatch's fallback rules are configurable per subscriber, per plan — not a single global setting — which is what makes it possible to give the weekday plan a skip default and the weekend family plan a repeat-last-week default without touching individual subscriber records every week.
The third mistake is running one menu library for two cadences that need different food. A weekday office plan wants lunch-heavy, portable meals — dal-chawal, roti-sabzi, the kind of food that travels in a container and gets eaten at a desk in fifteen minutes. A 7-day family plan needs more variety across the week, including a weekend option that reads like a small treat rather than another workday lunch. Operators who maintain a single rotating menu for both plans end up serving their weekend family subscribers the same dal-chawal an office subscriber ate on a Tuesday — food that was designed for a desk, not a Sunday lunch table. MealDispatch's rotating weekly menu system lets you run separate menu libraries with separate tag sets per plan, so the weekday rotation and the weekend rotation draw from different pools even if they share a kitchen and a delivery fleet.
None of this shows up until you cross roughly 40-50 subscribers on the second plan. Below that, an operator can hold the differences in their head — they know which subscribers are the "no-weekend" office crowd and which are the family plan, and they manually work around a shared cutoff and a shared menu. Past that point, the manual workaround becomes the actual bottleneck: every Saturday, the operator is mentally sorting two plans' worth of selections, fallbacks, and prep quantities out of what the system treats as one undifferentiated list.
The operator dashboard needs to segment by plan, not just by zone. Even once cutoff and fallback rules are configured correctly per plan, an operator who's still looking at one combined view of orders by week, by meal, by zone will struggle to sanity-check whether the weekday plan's Thursday selection rate looks healthy compared to the family plan's Saturday rate. Segmenting the dashboard view by plan — not just zone — is what actually lets you spot that your weekday plan's selection rate quietly dropped after you switched the office menu two weeks ago, before it turns into a wave of pauses.
This complements the day-skip conversation, but it's a different problem. A per-day skip lets one subscriber miss one delivery within a plan without pausing the whole week. Running two plans is about the plan-level defaults everyone on that plan inherits before any individual override happens. Get the plan-level defaults right — cutoff, fallback, menu — and day-skips become the occasional exception instead of the thing subscribers reach for because the plan-level settings never fit them in the first place.
If you're setting up a second plan on your Shopify store and want to see how per-plan cutoffs, fallback defaults, and separate menu libraries actually get configured — without duplicating your whole storefront — book a demo and we'll walk through your specific weekday and weekend split.