Meal-prep and diet-catering software: orders, menus, delivery routes
A subscription meal box is not a 20-SKU shop. It is calorie variants, skipped days, allergens, tomorrow’s production and a courier with 40 stops. Niche tools (MasterLife CRM, x-catering, SOT) can work. A custom app — when your diet and logistics do not fit the template.
Poland’s meal-prep market is dense and still growing: national brands and hundreds of local kitchens. The customer is not buying “a lunch set”. They want “keto 1800 kcal, no Tuesdays, no dairy, pause for a long weekend”. You need to know at 4:30 tomorrow how many vegan boxes go to one district, which lunches were swapped, and in what order the courier must run to finish before 8:00. Diet-catering software is not a webshop with a size variant. It is a diet builder, a production cutoff, an allergen label and a route in one flow.
Owners who started on Facebook and a spreadsheet usually break between 30 and 80 diets a day: a subscription was not extended, an address changed after cutoff, the kitchen under-cooked the gluten-free lunch, the courier returns with three “not home” bags. Polish operators say the same thing — past a certain volume you run out of hours, not hands. Automation is not a pretty storefront. It is how kitchen, dietitian and driver look at the same numbers.
Why a normal webshop breaks
WooCommerce and friends understand SKUs and colour variants. A meal box sells a time window and a dish matrix, not a shelf item. The customer prepays 20–30 days, then changes something every day. A shop does not know that production locks the list at 2 pm, or that the courier has 40 pins, not a parcel locker.
- A diet is a subscription with a pause, a mid-week kcal change and “skip 3–5 March”, not a one-off basket.
- Allergens and exclusions are a week-long rule and a label on every box, not a SKU attribute.
- Production counts tomorrow’s boxes today at 2 pm, not at the “buy” click. After cutoff, the order lands on the day after.
- The courier has a stop order, stairwells without intercoms and a 6:00–9:00 window, not InPost.
- Diet marketplaces (Dietly and similar) take a cut and keep the customer — the same tax as delivery aggregators.
- B2B (offices, gyms, clinics) wants one invoice, many addresses and a different price list than retail from a comparison site.
What a meal-prep day actually looks like
Morning: couriers leave with cold bags. The kitchen is already producing for tomorrow or the day after, depending on the model. The dietitian signed off the week’s menu, but overnight three kcal changes and one “holiday from Thursday” arrived. Stores must know how much chicken, how much tofu, how much lactose-free yogurt. Labels: diet name, kcal, allergens (EU 1169/2011), date, barcode / QR. If the label lies, the complaint is expensive and loud in Facebook groups.
Afternoon: cutoff. The production panel dumps counts: 42× keto 1800 breakfast A, 18× veg 2000 lunch B with a swap, 7× bariatric. Packers scan; the system knows which bag is complete. Evening: routes. Inner city vs suburbs — a different order depending on traffic and “please after 7:00, the child is asleep”. The customer sees the menu and may (or may not) swap a dish until hour X. This is not a shop. It is light APS + WMS + TMS under one brand.
Cutoff, pause, address change — three rules that kill Excel
Cutoff is sacred: “changes for tomorrow until 2 pm, otherwise the old variant ships”. Pause: the customer goes on holiday; you do not want to cook into a void or calculate a refund by hand. A two-day address change: another route, another zone, sometimes a surcharge. A spreadsheet holds this at 15 clients. At 80 — someone eats a dish with a nut they excluded, or the courier stands under the old block.
What meal-prep software must do
A real diet-catering programme joins sales, production nutrition and logistics. In Poland the names that circulate are MasterLife CRM (shop + client panel + kitchen reports, Dietly integration), x-catering, SOT-Catering and other “box” CRMs. They work when you fit their menu model. You still need the list below — in a package or in your own app.
- A configurator: goal (cut, bulk, keto, veg, low GI — as you sell it), kcal in 200 steps (typically 1200–3000), meal count (3–5), start day, usually Monday.
- A delivery calendar: skipped days, holiday, address change with lead time, a surcharge outside the base zone.
- Recurring payment (card / BLIK / transfer) and extra-day top-ups; credit or refund for undelivered days per your terms.
- A production panel: how many of which dish tomorrow, food cost, purchasing list, labels, allergens on the box and the bag.
- Routes: zones, pin order, time windows, a courier app with delivered / not-home / left with neighbour (if you work that way).
- A customer panel: week menu, a swap if you allow it (with a limit and cutoff), invoice, pause, a meal rating.
- Exclusions: nut, gluten, lactose, fish — a rule for the whole period, not a checkbox on one SKU.
- An end-of-diet reminder (SMS/mail), promo codes, referrals — because marketplace acquisition is dearer than a renewal.
Dietly and comparison sites: a channel, not your customer warehouse
Dietly is the default acquisition layer in Poland: hundreds of offers, kcal and diet filters, a consumer app, sometimes Smart Meal. MasterLife advertises a direct integration — the comparison order lands in the CRM. Convenient. It is also a tax on the basket, like Glovo: the customer learns the platform’s brand, not yours, and the cut eats a margin that is already thin on food cost. A sane strategy: the comparison site for start and peaks, your own checkout for regulars in your zone. An API integration only when volume justifies it — otherwise dispatch retypes ten orders a day and lives.
Do not confuse 1:1 dietitian tools with batch production. Aliant, Kcalmar, Mapi and DietetykPro are fine for a single patient plan. A kitchen of 200 boxes needs a recipe with yield, heat treatment and an allergen label, not a PDF for a consult. The catering dietitian should put recipes into the same system the kitchen prints from — otherwise office sheets and the kettle diverge.
A mobile app — for whom
The customer can start on a site that behaves like an app (PWA): menu, pause, address change, payment. The courier needs Android: day list, navigation, a call button and a door photo when nobody opens. Same pattern as field service: offline in a stairwell, sync on LTE. We do not ship an app-store listing before repeat routes and a fleet you control. The kitchen works on a tablet / scanner, not a decorative dashboard.
Vertical SaaS or your own engine
Pick a package (MasterLife, x-catering, SOT and kin) when you are starting, have one kitchen, standard kcal variants and fit their shop and reports. Cheaper than writing a configurator from zero and faster than teaching the kitchen two tools. Custom — or a layer on top — when any of the conditions below show up. Wider frame: SaaS or custom.
- Several kitchens / dark kitchens and one brand — stock and routes do not fit a single-site CRM.
- B2B: offices, gyms, clinics, athletes — other prices, invoices, one basket for 15 people.
- Your own marketplace or a franchise with per-site settlement.
- Unusual diets (clinical, hospital, elite sport) and rules the template does not know — without pretending to be a medical device.
- A platform cut eating regulars in your district; you want your own checkout plus SEO for “meal prep [city]”.
- A bridge: keep MasterLife for production, build sales and the courier app yourself.
An MVP the kitchen will survive on Monday
A rollout that starts with “AI suggests the menu and a drone delivers” dies at the first cutoff. The order that works for local catering:
- Checkout: diet, kcal, days, address, payment, pause and refund rules.
- Cutoff and tomorrow’s production report — a PDF / tablet a cook understands without ERP training.
- A label (allergens, kcal, code) and bag status.
- A route: ordered list, phone, status. Algorithmic VRP only when pins overflow the dispatcher’s head.
- Customer panel and an end-of-diet reminder. A native courier app when the fleet is yours, not one contractor with a private phone.
If you already have a shop and a CRM, we do not throw them out for sport. We add the missing piece: a checkout without the marketplace cut, a courier app, B2B or a second site. Cheaper than migrating 2,000 live diets in the New Year resolution spike.
What to connect, what to leave alone
Payments: Przelewy24 / PayU / Stripe + BLIK, card recurrence. Invoicing: from the panel and KSeF for B2B. The fiscal till stays a till — we do not fake a printer. A clinic dietitian who works with your kitchen can get a kcal bridge instead of retyping from dietitian software. Courier logistics is a cousin of restaurant ordering, only a cold chain and a morning window, not pizza at 9 pm.
Describe daily diet count, delivery zone, whether you sit on Dietly/MasterLife and whether orders, production or the courier hurt. We will say whether a bridge to a catering CRM is enough or you need your own checkout to leave the marketplace cut and not lose an allergen on Friday.
Allergen labels, food cost and the 2 pm report
EU 1169/2011 wants allergens on the pack. In meal prep the label hits every box and the bag: diet name, kcal, date, code, allergen list. MasterLife CRM and kin print it from the recipe, not from Word. Food cost is counted on a recipe with yield (raw vs cooked chicken), not on “last month’s average”. The production report at cutoff (typically 1–3 pm) is the only number the kitchen trusts — the rest is noise from late address changes.
- The 14 EU allergens on the label plus your exclusions (histamine, FODMAP) as a client rule, not a SKU.
- Food cost per dish and per diet — you see which keto 1800 eats the margin.
- A shared cutoff for kitchen, courier and client panel: after hour X a change lands the day after tomorrow.
- A QR on the label to a claim status when the box comes back “wrong order”.
Zones, 6:00–9:00 windows and Dietly as a tax
Warsaw, Krakow, the Tri-City: zones with a surcharge and a morning window. The courier has 30–50 pins, stairwells without intercoms, “leave with a neighbour” only if the client ticked it. Dietly and comparison sites give volume; the cut and “ownership” of the customer stay on the platform — same mechanism as Glovo. Your own checkout plus SEO “meal prep [district]” pays back on regulars in your zone. A MasterLife↔Dietly integration is convenient; it does not replace your cutoff or route.
B2B (an office of 15, a gym, a clinic) wants one invoice, many addresses and another price list. That is not a retail variant. A separate path in the configurator, KSeF when invoices leave the panel. Do not mix it with a comparison-site basket.
HACCP, the cold chain and a “warm breakfast” claim
A meal-prep kitchen runs under mass-catering hygiene: HACCP, temperatures, batch, due time. The system does not replace the HACCP book or the sanitary inspector — it watches which diet left in which wave and when the courier scanned “delivered”. A “breakfast was warm at 9:30” claim has a trail: cutoff, departure, pin, status. Without that you get a Facebook group. An insulated bag and pin order (furthest / most fragile first) are route rules, not dashboard décor. January/September floods production; July can be hollow — an LTV report Dietly vs Google says whether to buy another van.
Frequently asked questions
- Can you connect a diet marketplace?
- Yes, as an acquisition channel — like Glovo. MasterLife has a ready integration; others — if there is an API and volume. Your own checkout stays for regulars in your zone, because commission and “ownership” of the customer sit with the platform.
- How many kcal variants?
- Typically 1200–3000 in 200 kcal steps plus 4–8 diet types. That is a dish and label matrix, not eight SKUs. The more exceptions (lunch swap, exclusions), the earlier a spreadsheet lies.
- Pay a week in advance?
- Yes — plus pause and credit or refund for undelivered days. You write the rules; the system enforces them at cutoff. Manual “please recalc this on email” does not scale at 100 diets.
- Is a customer app required?
- Not at the start. A site / PWA is enough for pause and menu. A courier app — yes if you have your own fleet. Native for the customer when “change address by 2 pm” push is used every week.
- Is MasterLife / x-catering enough instead of custom?
- Often yes, for one kitchen and standard diets. Custom when you have several sites, B2B, your own marketplace, a courier app for your process, or you want off the comparison-site cut. We do not replace a working CRM for ideology.
- Allergens and medical diets — is this a medical device?
- We do not build a medical device or certified “diet as treatment” automation. The system watches labels, exclusions and production. Meal-plan responsibility stays with your dietitian. Hospital / clinical diets are a separate regime and a separate conversation.
- How do you plan routes with 40+ morning addresses?
- At the start: zones + a manual order + status in the app. VRP and minute windows when the dispatcher can no longer cope and pins repeat. We do not optimise “for toys” at 12 drops.
- How long is an MVP?
- Configurator + payment + production report + a simple route: usually weeks, not quarters, if menu and cutoff are clear. Dietly, WMS and B2B — the next iteration after numbers from the first month of regulars.
Describe your project