From Razorpay to Shopify Subscriptions: what Indian meal operators gain (and what to watch out for)
Every Indian meal operator we talk to has the same origin story. They started billing on Razorpay because it was the fastest way to collect UPI payments in 2022. They built a Google Sheet to track who paid for which week. At 40 subscribers it worked fine. At 60 it was manageable. At 90, the Sunday reconciliation started taking three hours and they were still missing renewals on Monday morning.
Shopify Subscriptions is the cleaner path forward. It handles UPI auto-debits, lets customers pause and swap without calling you, and integrates the billing directly into your order and fulfillment flow. MealDispatch is built on top of it specifically for Indian tiffin and cloud kitchen operators.
But the migration is not just "export your Razorpay list and import into Shopify." There are four India-specific gotchas that nobody tells you about until you're mid-migration and one of them bites you.
Gotcha one: you cannot carry UPI mandates across platforms. A UPI autopay mandate is tied to the merchant VPA and the specific payment gateway that issued it. When you migrate to Shopify Subscriptions, your existing Razorpay mandates cannot be transferred. Every subscriber who was on UPI auto-debit needs to set up a new mandate with Shopify Payments. This means you need a migration window — typically 2 to 3 weeks — where you are running parallel billing, reminding subscribers via WhatsApp to click the new mandate link, and manually reconciling who has completed the switch.
Gotcha two: COD customers need a grace period. In Delhi NCR, a meaningful slice of tier-2 subscribers — families in Ghaziabad, Faridabad, parts of Dwarka — pay cash to the delivery rider on the first delivery and then switch to digital for renewals. These customers have never set up a UPI mandate at all. If you cut them over to Shopify on migration day with no accommodation, they get a failed payment notification and you lose them. The right approach is to move UPI customers first, keep COD customers on their existing flow for one billing cycle, and then send a personal WhatsApp asking them to set up the mandate. MealDispatch supports UPI + COD simultaneously — Shopify Subscriptions handles cards and UPI auto-debits while you offer cash-on-first-delivery for new subscribers who need the on-ramp.
Gotcha three: the tiffin product must be created as a subscription product, not a one-time purchase. This sounds obvious, but the Shopify product setup screen does not make it clear. If you create your tiffin product as a standard one-time purchase and then try to attach subscription rules to it later, the cutoff logic and menu selection flow does not attach correctly. You end up with orders that appear in Shopify but don't surface in the MealDispatch order manifest. The fix is to start from scratch with the product created as a subscription product from day one — which means a short downtime for setup, not a patch job after the fact.
Gotcha four: announce the migration over WhatsApp, not email. Indian meal subscription customers have very low email engagement — operators we work with see email notifications go largely unread on migration day. WhatsApp broadcast messages get seen. When you tell subscribers "we are moving to a new ordering system next Monday, click here to reactivate your subscription," the difference between sending that over email versus WhatsApp is not marginal — it is the difference between a fraction of your subscribers completing the switch in the first 48 hours versus nearly all of them. Write the message in Hindi and English. Keep it short. Emphasise that their food and schedule stay exactly the same — only the order-placement experience improves.
The migration itself typically takes a weekend of setup and one billing cycle of parallel operation. Operators we work with move from WhatsApp + Sheets + Razorpay in under 7 days — the FreshKitchen team in Noida completed the transition in five. The operational payoff is immediate: no more Sunday reconciliation, no more chasing failed payment messages on Monday, and subscribers who manage their own pauses instead of texting you to skip a week.
One thing to budget honestly: you will lose a small number of subscribers in the transition. Customers who were borderline-engaged — picking meals every other week, sometimes paying late — are unlikely to complete the mandate migration. This is not a loss. These are customers who were already churning slowly. The migration accelerates their exit and cleans up your active subscriber count so your unit economics reflect reality.
The operators who hesitate on this migration usually do so because they are worried about breaking something that works. At 80 subscribers, Razorpay + a Sheet does work. At 140 subscribers, it does not — and by the time you feel that pain clearly, you have already spent months patching around it.
If you are approaching 80–100 subscribers and Sunday billing is already taking more than an hour, the migration window is now. Book a demo and we will walk you through the four gotchas in the context of your specific subscriber list and payment mix.