Solutions
Meal subscription software requirements
Most requirement lists for this category describe features. The ones worth writing describe failures — because every meal subscription system can create a subscription, and they differ entirely in what happens when one changes mid-cycle.
Write the list around change, not creation
Signing up a customer is the easy path, and every product demos it well. The requirement that separates systems is what happens on the Wednesday of week three when a customer moves from ten meals to fifteen.
That single event should update the subscription, price the change for the remainder of the cycle, add meal slots to the right week, increase the production count for the specific recipes chosen, adjust the ingredient requirement, generate the additional labels, update the delivery manifest and move the revenue figure — atomically, so it either all happens or none of it does.
Ask any vendor to perform exactly that, live, and then ask to see the audit record it produced. The answer tells you more than a feature matrix will.
Requirements that are worth being strict about
Atomic mid-cycle change
One customer change updates every dependent view in a single transaction. Partial application is the defect this category exists to prevent.
Proration you can explain
When a plan changes mid-cycle the customer must be able to be told exactly what they were charged and why, from a record rather than a recalculation.
Pause and skip as first-class states
Not a cancel-and-recreate, which destroys the history you will need when the customer disputes something.
Allergens as structured data
A field that can be checked against a recipe, not free text in a notes box. This is a food-safety requirement, not a convenience one.
A full audit trail
Who changed what, when. Without attribution you cannot resolve a dispute, and in practice you will absorb the cost of every one.
Production derived from selections
The cook list and the purchase list must come from the same source. If they are separately maintained they will diverge.
Requirements specific to operating in the Gulf
These are frequently missing from products built for other markets, and retrofitting them is expensive.
Arabic and full RTL
Not a translated interface bolted on — right-to-left layout, Arabic meal names on labels, and Arabic in customer messaging.
VAT-compliant invoicing
With the record structured for ZATCA e-invoicing in Saudi Arabia, even where issuance is not yet switched on.
A delivery calendar that knows the week
Friday handling and public holidays, plus the Hijri calendar where it affects the delivery schedule.
Configurable seasonal demand
Ramadan inverts the daily pattern. A single hardcoded production profile cannot express that.
WhatsApp as a real channel
In this market it is where customers actually are. Treating it as a notification afterthought misreads the operation.
Requirements to leave off the list
Resist specifying features you will not use in year one. Multi-branch, white-labelled customer apps and marketplace listings all sound prudent and all lengthen selection while narrowing your options to larger, slower products.
Be similarly careful with integrations. An accounting or rostering integration is worth requiring only if you have already established that the manual alternative costs you real time each month — otherwise it is a requirement that eliminates good products for a problem you do not have.
The test for any line on the list is whether you can name the specific thing that goes wrong today without it. If you cannot, it is an aspiration rather than a requirement.
Common questions
- What is the single most important requirement?
- That a mid-cycle plan change updates the subscription, billing, production, purchasing, labels and delivery in one atomic transaction. Everything else in this category is comparatively easy.
- Why do allergens need to be structured rather than free text?
- Because a text note cannot be checked against a recipe. Structured allergen data lets a conflict be flagged before cooking, which is a food-safety difference rather than a convenience one.
- Should I require an accounting integration?
- Only if you can name what the manual alternative costs you each month. Otherwise it is a requirement that eliminates good products for a problem you do not currently have.
- How do I test a vendor against this list?
- Ask them to perform a mid-cycle plan change live, then show you the audit record it produced. That single exercise is more informative than any feature matrix.
Test us against your own list
The product pages show a mid-cycle change propagating through production, purchasing, labels and delivery on a demonstration kitchen.
Related reading
- GuidesHow to choose meal delivery softwareMost software evaluations start with a feature comparison, which is the wrong end. Start from where your current week breaks, because that is what you are actually buying a fix for.
- GuidesWhat meal production software actually has to doA requirements list is more useful than a feature comparison, because it is yours. These are the capabilities that determine whether the number your kitchen cooks to can be trusted.
- GuidesRequirements for allergen handling in meal softwareThis is the one area where a missing requirement has consequences beyond money. Evaluate it more carefully than anything else on your list.
- 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.
- SolutionsWhy a meal business needs a change historyAn audit trail sounds like compliance furniture until the first time a customer insists they paused, a staff member insists they applied it, and the boxes went out anyway. Then it is the only thing that resolves the question.