How to set up your first Shopify tiffin store in 5 days: the launch checklist Delhi operators use
Three weeks after deciding to move off WhatsApp, a Noida tiffin operator named Meena had a beautifully designed Shopify storefront, a custom logo, two banner images she'd had made, and zero live subscribers. She had spent the three weeks on brand identity and had not yet created a subscription product. Her first order came in six weeks after she signed up for Shopify. Three of her original customers had already moved to a competitor.
This is not a rare story. It is the most common one we see.
The founders who go live in 5 days make a different set of decisions on Day 1. They do not open the theme editor. They do not install five apps to see which one they like. They create the subscription product first, configure pincodes second, and connect payments third. The store looks basic at launch. It works on Day 5. Meena's does not.
Here is the sequence that gets operators live in five days.
Day 1: Install MealDispatch and create your subscription product. Open Shopify, install MealDispatch, and your first task is creating a single tiffin subscription product — not a one-time purchase, a subscription. This distinction matters more than it sounds. If you create it as a one-time product and try to attach subscription logic later, the cutoff and menu functionality does not attach cleanly. The subscription product is the thing every other part of your setup depends on. Name it clearly: "Weekly Tiffin Plan — Delhi NCR" or "5-Day Meal Subscription." Add a price. Publish it. That is Day 1 done. Do not touch the theme.
Day 2: Pincodes and zones. This is the step that saves you 30+ failed deliveries in month one. MealDispatch comes pre-loaded with 117 Delhi NCR pincodes mapped to zones — South Delhi, Gurugram, Noida, Dwarka, West Delhi, Faridabad, Ghaziabad, Central Delhi. On Day 2, you open the zone settings, import the pre-loaded pincodes for your actual delivery area, and block out-of-zone customers at checkout. If you serve Noida Sector 62 and 137 but not Sector 15, you set that now. The checkout will refuse orders from pincodes you haven't enabled. This is not a nice-to-have. Operators who skip Day 2 spend their first month refunding customers in zones they cannot actually serve. Do Day 2 properly and you never have that conversation.
Day 3: The meal library. Add 10 to 15 meals with photos and dietary tags. The tags matter from the start: vegetarian, Jain, low-spice, vegan. When your first Jain subscriber signs up — and in Delhi NCR there will be Jain subscribers — the tag library is what lets you mark their preference once and have it carry through every week's selection page. Also set two fallback rules: one for subscribers who don't pick by cutoff (repeat-last-week is the safe default for most operators starting out) and one for subscribers who are new and have no previous week to repeat (chef's pick). MealDispatch lets you configure the fallback rule per subscriber later, but setting the plan-level defaults on Day 3 means you will not be debugging a silent-subscriber problem in week two.
Day 4: Payments. Connect Shopify Payments and enable UPI auto-debit. Test a subscription purchase end-to-end — pull out your own phone, go to your storefront, add the tiffin plan to cart, complete checkout with a test payment. This sounds obvious and is skipped more often than you would think. You want to find out on Day 4 that your UPI mandate prompt is showing the wrong amount, not on the first Monday when a real subscriber's bank declines the transaction. If you have tier-2 customers who will pay cash on the first delivery, add COD as a payment option now. Shopify Subscriptions supports it. Your delivery partner collects cash on Week 1, the subscriber sets up UPI auto-debit before Week 2. That is the standard tier-2 onboarding sequence for Delhi NCR operators.
Day 5: The WhatsApp selection link. Generate your storefront link from MealDispatch — the link that takes a subscriber directly to the weekly meal-selection page. Send it to five existing subscribers you already know, ideally people who have been asking you when you are going live. These are your dry-run testers. Ask them to click the link, pick their meals, and complete checkout. Watch what breaks. The most common Day 5 problems are: the link goes to the wrong page, the payment page shows the wrong currency formatting, and one pincode that should be enabled is blocked. Fix those five things before your broader launch. Do not send the link to everyone on Day 5. Send it to five people, fix what breaks, then send to everyone on Day 6 or 7.
The two mistakes that turn 5 days into 5 weeks. The first is treating the theme as a pre-launch task. Your Shopify theme can be improved after you have 30 subscribers. It cannot help you get those 30 subscribers. The second is trying to migrate everyone at once. Operators who send "we're moving to a new platform" to their full WhatsApp group on Day 1 spend the next two weeks managing confusion. The smarter move is to bring five trusted subscribers over in the dry run, fix what breaks, and then migrate the full list once the flow is confirmed. Most kitchens complete the full WhatsApp-to-Shopify migration in under 7 days from the first dry-run customer.
What you are building in 5 days is a working loop, not a polished storefront. A working loop means: subscriber receives a link, opens the selection page, picks meals, pays, and you receive a confirmed order that flows into your prep sheet. That loop, working correctly for even five subscribers, is worth more than three weeks of theme adjustments. MealDispatch auto-generates prep sheets by meal and pick-lists by route from Day 1 — so the operations side is already covered the moment your first real order comes in.
MealDispatch's setup time of 5 days to a live cutoff is the "Set up in under a week" promise on the homepage. It is not a marketing figure — it is what the checklist above produces when you follow it in sequence. If you want a walkthrough of the setup flow before committing, a 20-minute demo covers everything from subscription product to first live cutoff.