Solo, couple, or family: why one tiffin price for everyone is leaving money on the table
A newly married couple in Rajouri Garden signs up for your weekly tiffin plan. They don't want two of everything — they want one slightly bigger tiffin they can split over dinner, the way they'd split a thali at a dhaba. Your storefront doesn't have that option, so they do one of two things. Either they both subscribe to the solo plan and pay for two full portions when they only wanted one-and-a-half worth of food, or one of them subscribes and the other quietly orders from Zomato on the side because the single portion isn't enough for two.
Neither outcome shows up as a complaint. It shows up as a slightly odd order pattern you never trace back to its cause, or as one extra subscriber on your books who churns in month two because the maths never made sense to them.
Most tiffin operators price per person because that's how the plan started, not because it's how households actually eat. A solo professional in Dwarka, a couple in Rajouri Garden, and a family of four in Vasant Kunj all get offered the same per-person weekly rate, multiplied by however many people are eating. It's the simplest thing to build and the easiest thing to explain on a WhatsApp broadcast. It's also the reason your two-person households are the segment most likely to either over-pay and grumble or under-order and drift away.
Portion size deserves the same treatment you already give dietary type and spice level — a tag on the meal, not a separate product. If you're already running a Jain plan or a low-spice plan through MealDispatch's meal library, you've seen how a tag on the dish routes the right version to the right subscriber without the kitchen building a second menu from scratch. Portion size — solo, couple, family — is the same kind of tag on the same object. A couple's tiffin isn't a different dish; it's the same Rajma Chawal with a portion multiplier and a slightly different container.
A starting framework worth testing, not a rule to copy exactly: solo at 1x, couple at roughly 1.6–1.8x, family at roughly 2.5–3x for four. The couple and family multipliers come in under a straight per-head multiple because shared sides, one shared container, and one delivery stop all cost less than the equivalent number of individual tiffins. Treat these ranges as a place to start pricing from your own food cost, not a benchmark to copy — every kitchen's packaging cost and portion discipline is different enough that the right number for you might sit outside this range entirely.
Price a family tiffin at a flat 3x per-head rate and you leave margin on the table on packaging and delivery you're not actually spending three times over. Price it too low and you invite a four-person household to route their whole week's meals through what was meant to be a one-doorbell-ring convenience, quietly increasing your food cost per order without a matching increase in revenue. Getting the couple and family multiplier right is a food-cost exercise specific to your kitchen — how much of a typical meal is shared sides versus individually-plated protein — not a number a blog post can hand you.
This is also a diagnostic tool for the under-ordering you can't currently see. If you've read the piece on reading meal-performance data or the one on tracking quality complaints and credits, you know that unexplained skip patterns and vague dissatisfaction are usually a signal worth chasing rather than a subscriber being difficult. A two-person household stuck on a solo plan is a classic source of exactly that kind of unexplained pattern — quiet supplementing with outside food that looks, from your dashboard, like ordinary variability rather than a mispriced plan.
The billing side rides the same mechanism you'd already use for an add-on. Because MealDispatch runs on Shopify Subscriptions, a portion tier is a line-item variant on the existing subscription product — the same underlying pattern that lets an operator sell an extra roti or a protein add-on without opening a second invoice or a second payment mandate. A couple selecting the "couple portion" toggle on the storefront is choosing a variant of the same weekly plan, billed on the same cycle, at the same cutoff. There's no second product to build and no second subscription to reconcile against the first.
Keeping it on the same cutoff and the same fallback rule matters more than it sounds like it should. A portion tier that needs its own cutoff time or its own fallback logic stops being a pricing tweak and starts being a parallel plan the kitchen has to run twice. MealDispatch's configurable, per-plan cutoff already handles one deadline per subscriber; a portion variant should sit inside that deadline, not create a second one. The same goes for fallback — a couple on repeat-last-week fallback should get last week's couple-portion order, not a solo portion by default because the fallback logic never learned there was a variant involved.
Which pricing tier this affects depends on how much of your base is currently mispriced this way. An operator on the Kitchen plan with 200 subscribers in one zone might find this is a handful of households worth fixing manually before it's worth building a whole tier for. An operator approaching the Brand plan's 1,500-subscriber, multi-zone range — where average order value starts to matter for how the business is priced and reported — is the kitchen where getting solo, couple, and family portions right as a standing tag, not a one-off favour, actually moves the number that matters.
None of this requires new infrastructure — it requires extending the tag library you're already using for dietary type and spice level one dimension further, and pricing what households were already asking for informally. If you're running a tiffin service in Delhi NCR and want to see how a portion tier sits as a variant on your existing subscription product, billed on the same cycle, at the same cutoff, a MealDispatch demo walks through the setup in about 20 minutes.