Cutoff is 2 hours before Breakfast and Lunch, and 4 PM for Dinner (set per batch). Finalize locks a batch so customers can no longer skip; kitchen and delivery then work from the locked list.
Add-ons and their price. These appear as options on every customer's plan.
Prices for plans, dish types and other items. Stored as data, editable anytime. Tip: add an item labelled Customized to set the per-unit charge that pre-fills when you create a Customized plan.
Loading…
Each slot has a delivery window and a cutoff (minutes before the window starts). A meal can be cancelled only before its cutoff for that day; after that, cancellation is closed. Slots appear as batches in Kitchen, Delivery and plan setup.
Mark a day off and every delivery scheduled for it is carried forward, so customers keep their meals (nothing is lost) and future schedules skip the date automatically.
Every Sunday (2:30 AM), paused plans whose last delivery was this many months ago have their pending meals removed: the balance goes to 0, the plan becomes Expired, and an entry is added to the log below and to the customer's History. Active plans are never touched. A plan counts as used when it has a delivery, starts, or gets a top-up. Set 0 to switch the clean-up off.
A line at the top of every customer's app, for whatever is going on: heavy rain, a late batch, a festival offer. Holidays need no notice here — the app builds those itself from the Holidays tab, and only shows them to customers who order on that weekday. Leave both dates empty and the notice stays up until you switch it off; set a window and it comes and goes on its own. A customer can dismiss it once, on their own phone.
Shown on the customer app's Home screen — only when that customer has no active plan (fills the empty space with a promo, plan info, or tips). Swipeable if you add more than one. Size guide: 1200×600px (2:1 ratio), JPG/PNG/WebP, under 1MB.
Shown next to each plan on the customer app's meal-plan cards. Size guide: 400×400px square, JPG/PNG, under 500KB.
Distance fee used by the customer order page (start.nosh7.in). Free up to the free distance, then ₹ per started km beyond it, with a grace/leeway so a few extra metres don't bump the charge a whole km. E.g. free 5 km, leeway 0.1, ₹10/km: 6 km → ₹10, 8.0 km → ₹30, 8.15 km → ₹40 (per delivery). The road factor turns the map's straight-line distance into real driving distance; the preview below uses the actual distance you type. Live, these drive both the order page and the payment charge.
Create discount codes for the order page. Flat ₹ or percentage off, limited to chosen plans, with optional validity dates and a usage cap.
Which AI answers Biba's questions, its key, and the rules she always follows.
Upload your Subscriptions export (the CSV from the old platform — the file with columns Name, Phone, Product, Quantity, Delivery Slot, Plan quota, Remaining quota, Status…). Customers, plans and the delivery schedule are all built automatically. Active plans with units left generate deliveries; the rest load as history. Re-uploading is safe — matched by phone, it updates instead of duplicating. Tip: tick "wipe first" for a clean reload.
Paste your orders Sheet link. It must be set to "Anyone with the link can view" for this to work. Paid rows import as active, pending as pending, junk/failed rows are skipped. Matched by Order No, so re-importing updates instead of duplicating.
In the Sheet: File > Download > Comma-separated values (.csv). Open the file and paste everything below, including the header row.
Export your customer list from Excel as CSV (File > Save As > CSV), then upload or paste it below. Columns are auto-detected by header (needs a Name and Phone column; Email optional). This is a read-only check - nothing is changed. It flags customers missing on either side, duplicate phones, mismatched details and rows with missing info.
Choose which batches to download.