Ecommerce development in Mumbai
Mumbai's beauty and fashion brands sell in bursts. A creator posts, a collaboration drops, a sale starts, and the traffic of a month arrives in an hour. The store that coped yesterday times out at checkout, the same stock is sold through the website and two marketplaces at once, and cash-on-delivery orders come back undelivered, having cost shipping both ways.
We build for those days. Custom Shopify apps or a headless storefront when the theme cannot keep up, stock sync that treats the warehouse as the source of truth and reconciles every channel, and payment handling that makes a duplicated Razorpay webhook harmless. We can also build the rules that decide which orders to confirm before shipping on cash on delivery, from your own history of returns. The checkout is load tested before the drop, not during it.
Mumbai is India's financial capital. Both major stock exchanges are here, and so are many of the country's banks, NBFCs, brokers, wealth managers, insurers and fintechs. For these companies software is judged first on whether the money is right. A loan ledger that drifts from the bank statement, a payout released twice because a partner timed out, a portfolio screen showing yesterday's price: each one lands on an operations desk the next morning. What they need built is rarely a new product from nothing. It is a lending or payments backend that reconciles, a platform where each role sees exactly what it should, and approvals that need two people before money moves. Engineers who have built those systems are in demand across the city, so the work often waits for a hire.
The city's second industry is attention. The Hindi film industry, most of the country's television networks and many of its large publishers are based here, and their software problems are specific: traffic that arrives all at once on a release or a match day, rights and metadata that decide what can be shown where, and archives that are valuable only if someone can search them. A slow page on a publisher's site is lost revenue, because the readers came from search and will go straight back to it.
The third is consumer business in every size. Mumbai has D2C brands selling beauty, fashion and food through their own stores and every marketplace at once, and it is home to large family-owned groups and conglomerates whose older divisions still run on spreadsheets and exports from their accounting software. In the bigger groups the buyer is usually a digital team with a mandate, a budget and a procurement process, and the work has to survive that process as well as production.
We are in Bengaluru and share your time zone, so the working day is the same on both sides and a question asked in the morning is answered the same morning. You talk directly to the engineer who writes the code. The work happens in your repository and a shared chat channel, where every decision is written down, and the runbooks and architecture notes are written as we go rather than at the end.
We are the right fit when a Mumbai team has a defined piece of work and wants a senior engineer on it within days: a ledger that has to reconcile, a migration with an end date, or extra capacity while you hire. Start with a fixed-price two-week piece, or bring us in white-label for your agency's clients under your name.
Four ways this arrives.
The ERP updates overnight, the store sells all day, and by morning the two do not match. We build the sync as a queue with retries and reconciliation, decide which system wins for each field, and alert on drift before a customer buys stock you do not have.
Or checkout slows until people give up. We cache what can be cached at the edge, keep live stock checks off the browsing path, load-test the shape of a real launch rather than a steady trickle, and queue anything that cannot scale.
Bundles, B2B price lists, subscriptions, delivery rules by postcode. We build it as a custom Shopify app or with Shopify Functions and checkout extensions so it survives platform updates, or tell you when you have outgrown the theme altogether.
Payment webhooks can arrive twice, late or out of order, and the handler trusts every one. We make order state follow the provider's record, process Stripe and Razorpay events idempotently, and reconcile daily so a mismatch is a report, not a complaint.
An hourly sync with a third-party system reachable only through its API, with values normalised at the boundary so unchanged records stop looking changed.
Read the write-up →Asked by Mumbai teams.
How do you work with teams in Mumbai?+
We are in Bengaluru and share your time zone, so calls, reviews and releases fit inside your normal working day. We work in your tools, Slack, GitHub and Linear or whatever your team already uses, and every decision is written down in the repository or the channel. You talk directly to the engineer writing the code, from the first 30-minute call through to handover, with runbooks and architecture notes written as we go.
Do you build for Mumbai lenders, brokers and fintechs?+
Yes. We build the parts where the money has to be right: loan and payment ledgers that reconcile against the bank's records every day, retries that cannot turn a timeout into a double payout, maker-checker approvals where a second person signs off before money moves, and a full history of every change of state. We work inside the system you already run, in Node, Python and Next.js, and ship in increments.
How does your rate compare to hiring in Mumbai?+
PayScale puts a mid-career software engineer in Mumbai at about ₹15 lakh a year. Our published rate is $35 an hour, with a $5,000 minimum. That buys a senior engineer who writes the code, works in your Slack, GitHub and Linear, and starts within days, with no recruiting round, notice period or employment overhead. Start with a fixed-price two-week piece at $2,800 and judge us on the output before committing to more.
Can you work white-label for our Mumbai agency?+
Yes. Mumbai's digital and media agencies bring us in when a client needs a backend, a mobile app or a data pipeline alongside the design and campaign work. We work under your name, in your client's repositories and your channels, and sign an NDA before specifics. The code belongs to the client from the first commit. You keep the relationship, we write the code and the runbooks, and your team presents the work.
Have you built a store like ours?+
We build stores from the parts of commerce that usually go wrong, and those are what we work on every day: syncing with a third-party system that only speaks through its API, handling webhooks that arrive twice, and background jobs that must not lose or repeat work. On a call we will walk you through how that applies to your store.
Shopify, headless, or fully custom?+
Start with Shopify if a theme and a few apps cover you; that is cheaper than anything we would build. Go headless when the storefront must do things a theme cannot, or share a front end with other products. Build on Medusa or commercetools when the catalogue, pricing or order flow is genuinely unusual. Most stores never need the third option, and we will say so.
Can you connect our ERP or warehouse system?+
Usually, if it has an API or can export files on a schedule. We start by agreeing which system owns each field, such as stock, price and order status, because most sync bugs come from two systems both believing they are the source of truth. Then we build the sync with retries, a log of every change, and a daily reconciliation report.
Which payment providers do you work with?+
Stripe, Razorpay, and Shopify Payments when the store runs on Shopify. Choose the one that suits your markets and fees; we earn nothing from any of them. The work that matters is the same for all three: treat the provider as the record of what was paid, handle every webhook idempotently, and test refunds and partial captures, not only the happy path.
How do you prepare for a sale or a launch?+
We load-test the whole journey, from landing page to paid order, at the traffic you expect and beyond it. We find what breaks first, which is usually a third-party script, an uncached page or the stock check, and fix it before the day. During the sale itself, the engineer who did that work is watching the dashboards with you.