On this page · 12 sections
Summary. India's online retail market reached roughly $80 billion in FY26, growing 21% year over year, against a total e-commerce sector that IBEF values at $125 billion in 2024 and projects at $345 billion by 2030. The payment layer underneath it is now the largest in the world: UPI carried 24,161.69 crore transactions worth ₹314 lakh crore across FY2025-26, up 30% by volume, with 703 banks live as of March 2026. For a brand commissioning an ecommerce app in 2026, three things set the schedule and none of them are design. Google Play requires new apps and updates to target Android 16 (API level 36) from 31 August 2026. Apple has required builds made with Xcode 26 and the iOS 26 SDK since 28 April 2026. And the Digital Personal Data Protection Rules, notified on 14 November 2025, run an 18-month phased compliance timeline that lands in 2027. eCorpIT builds ecommerce apps against those constraints from Gurugram, and this page sets out honestly what the work involves.
Who this is for
You already sell online, through a website, a marketplace listing, or both, and the app is the next step. Or you are a D2C brand whose repeat-purchase rate justifies owning the customer relationship rather than renting it from a marketplace. IBEF puts the D2C segment on a path to $60 billion by 2030 at a 40% CAGR, and the reason is retention economics rather than acquisition.
If you are pre-revenue and looking for an app to create demand that does not exist yet, an app is the wrong first investment. We will say so on the call.
What an ecommerce app actually contains in 2026
The catalogue and checkout are the visible part. The work is underneath.
Catalogue and search. Product data modelling, variant handling, inventory sync against your ERP or Shopify backend, and search that survives Indian spelling variance. Most catalogue problems are data problems, not app problems, and they surface in week two.
Payments. UPI is not optional. It carried 85% of India's digital payment volume in FY2025-26, and March 2026 alone saw 2,264 crore transactions worth ₹29.53 lakh crore. A build that treats UPI as one option in a list rather than the default path is a build that will convert badly. Cards, netbanking, wallets and pay-later sit behind it.
Card storage, which you cannot do. Under the RBI's card-on-file tokenisation directions, since 1 January 2022 no entity in the payment chain other than card issuers and card networks may store actual card data. A merchant may retain only the last four digits and the issuer name for reconciliation. For a marketplace, the RBI defines the e-commerce entity itself as the merchant. Tokenisation is therefore a build requirement, not an optimisation.
Subscriptions and recurring payments. If you run a subscription box, a loyalty plan, or any auto-debit, the RBI's consolidated Digital Payments E-mandate Framework, 2026, issued 21 April 2026 and effective immediately, governs it. Registration and any modification or withdrawal need additional factor authentication. You must send a pre-transaction notification at least 24 hours before each debit, naming the merchant, amount, debit date and time, the e-mandate reference and the reason, and the customer must be able to opt out of a single debit or the whole mandate. Recurring transactions run without AFA up to ₹15,000, rising to ₹1,00,000 for insurance premiums, mutual fund subscriptions and credit card bill payments. You may not charge the customer for the e-mandate facility.
Logistics and returns. Serviceability checks, courier allocation, tracking, and a returns flow that does not generate support tickets. Returns are where Indian ecommerce apps lose their rating.
Analytics and consent. Event instrumentation that survives the consent requirements below, rather than a tag manager bolted on afterwards.
The three deadlines that set your launch date
| Requirement | Effective date | What it means for your build |
|---|---|---|
| Google Play target API 36 | 31 August 2026 (extension available to 1 November 2026) | New apps and updates must target Android 16 to be accepted. Any late-2026 launch ships on API 36 |
| Apple Xcode 26 and iOS 26 SDK | Since 28 April 2026 | Uploads to App Store Connect must be built with Xcode 26 or later |
| Apple age rating questionnaire | Since 31 January 2026 | Ratings were auto-migrated to the new system; unanswered questions interrupt update submissions |
| DPDP Rules, 2025 | Notified 14 November 2025, 18-month phased timeline | Consent notices, breach notification, data principal request handling within 90 days |
| RBI e-mandate framework 2026 | 21 April 2026, immediate | 24-hour pre-debit notice and AFA rules for any recurring charge |
Pull those dates forward into the plan and they cost nothing. Discover them at submission and they cost a release cycle.
What the app stores actually take
The commission question comes up on every call, and the answer for a physical-goods ecommerce app is usually reassuring.
Apple charges 30% on paid apps and in-app purchases, reduced to 15% under the App Store Small Business Program for developers with up to $1 million in proceeds in the prior calendar year. Google states that 99% of developers who are subject to a service fee qualify for 15% or less, and that only 3% of developers pay a fee at all, because the fee attaches to digital goods and services rather than physical ones.
Two India-specific points matter. Following the Competition Commission of India order, developers may offer an alternative billing system alongside Google Play's for users in India, and where a user pays through it the Play service fee is reduced by 4%, so 15% becomes 11%. It requires PCI DSS certification, Play Console enrolment, and transaction reporting through the alternative billing APIs within 24 hours.
And on Google's new fee model announced in March 2026, India sits in the Rest of World rollout group with an effective date of 30 September 2027. India stays on the current model through the whole of 2026 and most of 2027, so do not budget against the new rates yet.
Where ONDC fits, and where it does not
ONDC had over 1.16 lakh retail sellers live across more than 630 cities and towns as of 9 December 2025, per the Ministry of Commerce and Industry. For a seller whose economics are broken by marketplace take rates, network participation is worth modelling. For a brand whose problem is retention rather than reach, it is a distraction from the app.
We build for both, and the honest test is whether your unit economics currently fail because of commission or because of repeat rate. Our ONDC playbook for D2C brands and sellers works through that, and the wider stack question sits in the D2C quick-commerce tech stack for India.
Quick commerce is the other pull. IBEF sizes it at $7 billion to $8 billion in FY25, growing at a 110% to 130% CAGR since 2021 and projected at $65 billion to $70 billion by 2030. If your category is genuinely 10-minute, the app architecture changes: serviceability, dark-store inventory and slot logic move to the centre.
How we build
1. Discovery, 1 to 2 weeks. Catalogue audit, payment and logistics partner review, compliance mapping against DPDP and the RBI rules above, and a written scope with the things we are deliberately not building in version one.
2. Architecture, 1 to 2 weeks. Data model, API contract against your existing commerce backend, offline behaviour, and the analytics event schema. We write the event schema before the screens, because retrofitting instrumentation is what makes launch analytics useless.
3. Build, 8 to 16 weeks. Two-week increments with a working build at the end of each. Native Swift and Kotlin where the app is performance-critical, Flutter or React Native where a shared codebase genuinely pays. We will argue for the boring option; the framework comparison is in our React Native versus Flutter hiring decision framework.
4. Test, 2 to 3 weeks, overlapping. Device matrix weighted to what your analytics actually show, payment failure paths, and a returns flow walked end to end rather than demoed.
5. Launch and stabilise, 2 to 4 weeks. Store submission against the current API and SDK requirements, staged rollout, and a defect budget reserved for the first three weeks after launch, because there will be defects.
A first production release for a focused catalogue typically lands in the 12 to 20 week range. Anyone quoting six weeks is quoting a template.
The stack
Mobile. Swift and SwiftUI, Kotlin and Jetpack Compose, Flutter, React Native.
Backend and cloud. India-region AWS, Azure or Google Cloud, with data residency decided at architecture stage rather than after the DPDP conversation.
Commerce. Shopify, headless commerce backends, or your existing ERP through a stable API contract. eCorpIT is a Shopify partner alongside AWS, Microsoft and Google.
Payments and identity. UPI-first checkout, tokenised cards, e-mandate flows built to the 2026 framework, and Aadhaar-based or OTP identity where the category requires it.
AI. Recommendation and search ranking where you have the data volume to justify it, and not where you do not. Agentic shopping is arriving, and the buyer-side view is in our note on AI shopping agents and D2C agentic commerce.
Why eCorpIT
We are a senior-led engineering organisation founded in 2021, headquartered in Gurugram, assessed at CMMI Level 5 and certified to ISO 27001:2022, and an MSME registered company. We are partners with AWS, Microsoft, Google and Shopify.
You get full IP and code ownership from day one. The people who scope your build are the people who write it. And we design applications aligned with DPDP requirements rather than claiming a compliance certification we do not hold.
What we will not do is quote a fixed price before understanding your catalogue and your payment mix, because the honest range between a 400-SKU single-warehouse build and a multi-marketplace inventory sync is wide enough that any number quoted in advance is marketing. Our cost benchmarking against offshore alternatives is in India versus US app development cost, and if you are running a formal process, our mobile app development RFP template will save you a round.
Related work
We build across the mobile portfolio, and the neighbouring pages are enterprise mobile app development, D2C mobile app development, and our mobile app development company in Gurgaon page for buyers who want a partner they can visit. If you are still shortlisting, how to choose a mobile app development company sets out the questions worth asking.
How eCorpIT can help
eCorpIT builds ecommerce and D2C apps for Indian brands, covering catalogue and inventory integration, UPI-first checkout, tokenised card flows, e-mandate compliant subscriptions, and store submission against the current Google Play and Apple requirements. Our senior engineering teams work to CMMI Level 5 process discipline and ISO 27001:2022 controls, and we design applications aligned with DPDP requirements. For a scoped estimate against your catalogue and payment mix, contact us.
FAQ
References
Last updated: 14 August 2026.
