Do you need a weekly menu, or one menu customers can pick from anytime?

Updated July 2026 · 6 min read

Meal subscription stores come in two fundamental shapes, and they need different menu models. Some kitchens cook fresh every week, so what's available changes by delivery week. Others sell from a stable lineup — frozen meals, baby food, snack or pantry boxes — where the selection is really a product configuration that rarely changes. Picking the wrong model means either rebuilding the same menu every week for no reason, or fighting a weekly structure your business doesn't have.

Dated menus: when the week decides the food

A dated (weekly) menu ties the available dishes to a delivery week. Customers see this week's menu and next week's menu as separate choices, and each upcoming delivery has its own selection. This fits:

• Fresh prepared meals cooked to a weekly kitchen schedule.
• Seasonal or market-driven menus that genuinely rotate.
• Stores that use menu variety itself as the retention hook — "see what's on next week".

Publishing a fresh menu weekly doesn't have to be manual work: build reusable menu templates and assign them to a repeating rotation (for example a 4-week cycle), and each upcoming week resolves to the right template automatically. One-off weeks — a holiday special — can still override the rotation for a single date.

Evergreen menus: when the selection is the product

An evergreen menu is one selection that every customer picks from, with no week tabs at all. The menu only changes when you change your catalog. This fits:

On renewal, an evergreen subscription behaves like a standing order: each new delivery repeats the customer's last saved picks until they change them. Customers who want variety edit an upcoming delivery in the customer portal; everyone else gets their usual box with zero effort. If you sell a stable lineup, this is almost always the model you want — don't simulate it by copying the same weekly menu forever.

"No menu dates" does not mean "no delivery dates"

The part that trips people up: going evergreen removes dates from the menu, not from the subscription. Every delivery still has:

• A real delivery day, shown in the customer portal per upcoming order.
• An order cutoff — the deadline for changing the box before your kitchen or warehouse commits.
• The usual self-service controls: edit selection, skip a delivery, pause the subscription.

How to choose

Ask one question first:

• Does what's available change by delivery week? Yes → dated menus (with rotation templates to save the weekly work). No → evergreen.
• Mostly stable with occasional specials? Evergreen, plus a one-off weekly menu when you run a special — dated menus take precedence for the dates they exist, then the store falls back to evergreen.
• Same menu but different plan sizes? That's not a menu question — put the size on the plan product (see plan sizes and tiers).

Setting up an evergreen menu in Servd

1. Build one menu template containing every product customers can pick from.
2. Enable evergreen mode and choose that template.
3. Confirm the menu week start day (it defaults to your delivery day) so cutoffs count back from the right weekday.
4. Save — the storefront now shows one menu with no week selector, and renewals repeat each customer's last picks automatically.

Changing the range later is just editing the template: new picks see the change immediately, and selections customers already saved keep what was stored.