Solutions
Software for family meal subscription businesses
A family subscription looks like one customer and behaves like four. One address, one payer, one delivery slot — and four sets of portion sizes, dislikes and allergens that all have to reach the right box.
Why families break a per-customer model
Most meal-plan software models a subscription as one person eating one plan. Families violate that on day one. The account holder pays, but the meals belong to several people, and the constraints that matter at the packing bench belong to individuals rather than to the household.
Operators usually paper over this by creating one subscription per family member, which fixes packing and breaks everything else: four delivery records for one doorstep, four invoices for one payer, and a pause that has to be applied four times and is applied three times.
The alternative — one subscription with a free-text note saying "no nuts for the youngest" — puts a food-safety constraint in a field nothing checks. That is the arrangement that eventually produces the phone call nobody wants.
What a family plan actually needs to hold
Each of these is a field or a rule, not a note somebody has to remember to read.
Several eaters under one billing account
The payer and the eaters are different records. One pause, one address change and one invoice, applied once, covering everybody.
Per-eater portion size
A child portion and an adult portion of the same recipe are different quantities of the same ingredients, and purchasing has to see both.
Per-eater allergens
Allergens belong to the person, not the household. A conflict must be flagged against the specific box, not the account.
A single delivery stop
Four eaters are one address, one driver stop and one handover — not four stops sharing a postcode.
Labels that name the eater
When four boxes land on one doorstep, the name on the label is what stops the wrong person eating the wrong meal.
How Mealroh models it
A household is one subscription with several meal recipients. Portion size and dietary constraints sit on the recipient; billing, delivery day, address and pause state sit on the subscription. That split is the whole trick — it means a pause is one action and an allergen check is per box.
Because production and purchasing derive from the same selections, a household ordering three adult and two child portions of a recipe produces one cook-list line with the correct total and an ingredient requirement that reflects both portion sizes. Nobody reconciles the two.
The allergen check runs against each recipient rather than the account. If the youngest reacts to dairy and a selected meal contains it, that specific box is flagged before it is cooked, with the recipient named.
Where this matters commercially
Household plans are usually a meal business’s highest-value subscriptions and its most fragile ones. The revenue per stop is several times a single plan, and the churn trigger is often not price but a single mishandled constraint — the child’s box arriving with the thing the child cannot eat.
They are also where manual propagation fails first. A family changes something roughly as often as its members do, and each change touches four downstream documents rather than one.
If you are running households on a per-person subscription model today, the migration question is not whether the data can move but whether your current system has ever recorded which eater a constraint belongs to. Frequently it has not, and that is worth discovering before a cutover rather than after.
Common questions
- Can one family account hold different portion sizes?
- Yes. Portion size sits on the individual recipient rather than the subscription, so a household can mix adult and child portions of the same recipe and purchasing sees the correct total for each.
- How are allergens handled when several people share an account?
- Allergens belong to the recipient, not the account. The conflict check runs per box and names the person, so a constraint that applies to one family member cannot be lost behind a household-level note.
- Does a family generate several delivery stops?
- No. Several recipients at one address are one stop with the correct item count, so the driver sees one handover rather than four records sharing a postcode.
- What happens when a family pauses?
- One pause applies to the whole household in a single transaction, and production, purchasing, packing, delivery and the billing record all move with it. There is no per-member pause to forget.
See how a household subscription behaves
The product pages show the model running against a demonstration kitchen, including an allergen conflict caught before cooking.
Related reading
- SolutionsMeal subscription software and the lifecycle it has to modelSubscription software for digital products only has to keep charging a card. A meal subscription also has to keep a kitchen, a packing bench and a van in step with whatever state it is in today.
- SolutionsAllergen management software for meal businessesEvery other field in a meal-plan system can be wrong and cost you money. This one can be wrong and cost someone a hospital visit, which is why it deserves different treatment from the rest of the customer record.
- SolutionsCustomer self-service for meal plansEvery routine change a customer cannot make themselves becomes a message someone has to read, interpret and apply correctly before a cut-off. That workload grows with your customer count, not with your feature list.
- GuidesWhen a customer changes their dietary requirements mid-planA dietary change arriving mid-term is unlike any other amendment, because it retroactively invalidates choices that have already been made — including meals that are already frozen for production.
- SolutionsMeal label software for prep kitchensThe label is the last line of defence in a meal-prep operation and the only artefact the customer actually reads. Everything about how it is produced matters more than it appears to.