When Traction Isn't Enough: PMF, Shutdown, and the Path to ONDC

By Sanghamitra Nayak, Founder | Nirmal Chandra Nayak, Cofounder January 26, 2026

We had traction. We had customers. We had revenue.

At one point, CenterShops was delivering up to 2,000 orders per month. Customers were using the platform. Merchants were getting orders. Delivery partners were earning income.

But traction alone does not guarantee success.

This is the story of what we learned about product-market fit, operational sustainability, and when to pivot—and how those lessons now inform our path forward with ONDC and ChittaTaxis.

The Traction We Had

By month 12, CenterShops had achieved meaningful traction:

• 500+ active customers ordering regularly
• 15+ local merchants partnered with the platform
• 10+ delivery partners fulfilling orders
• 2,000 orders per month at peak
• 65% repeat customer rate indicating product stickiness
• 30-45 minute average delivery time meeting customer expectations

These were not vanity metrics. They represented real demand, real transactions, and real value delivered.

But beneath the surface, we were facing deeper challenges.

The Constraints We Hit

Constraint 1: Unit Economics

Every order generated revenue (commission from merchants, delivery fees from customers). But the cost to fulfill each order was higher than we anticipated:

Costs per order:

• Delivery partner payout: ₹30-50
• Payment gateway fees: 2-3% of order value
• SMS/notification costs: ₹2-5
• Customer support overhead: ₹5-10 (averaged across all orders)
• Infrastructure costs: ₹3-5 (AWS, servers, databases)

Revenue per order:

• Merchant commission: 15-20% of order value (₹30-60 for average ₹300 order)
• Delivery fee: ₹20-30 (often waived for promotions)

Net margin: Thin to negative on many orders, especially after promotions.

The problem: We could not achieve profitability at current scale. We needed 10x order volume to spread fixed costs and improve unit economics.

Trade-off: Growing 10x required significant capital investment (marketing, operations, technology). We did not have that capital, and raising it would require proving stronger unit economics first.

Constraint 2: Operational Intensity

Running a hyperlocal marketplace required constant operational effort:

• Merchant support: Helping merchants with menu updates, order issues, payout questions
• Customer support: Handling complaints, refunds, delivery delays
• Delivery partner management: Onboarding, training, resolving disputes
• Quality audits: Visiting merchants to ensure hygiene and service standards
• Manual interventions: Handling edge cases that automation could not solve

The problem: Operational costs scaled linearly with order volume. We needed more people to handle more orders. This limited profitability.

Trade-off: Automation could reduce operational intensity, but it required upfront investment and time to build. We were caught between needing to grow and needing to automate.

Constraint 3: Market Depth

Kendrapara had a population of ~150,000. Not everyone was a potential customer:

• Smartphone penetration: ~60-70% (improving but not universal)
• UPI adoption: ~50-60% (growing but not ubiquitous)
• Willingness to pay delivery fees: ~30-40% (many preferred to pick up themselves)
• Addressable market: ~20,000-30,000 potential customers

The problem: We were approaching market saturation in Kendrapara. To grow, we needed to expand to other cities. But each new city required merchant onboarding, delivery partner recruitment, and local operations—essentially rebuilding the platform from scratch.

Trade-off: Expanding to new cities required capital and operational capacity we did not have. Staying in Kendrapara limited growth potential.

Constraint 4: Competitive Pressure

Swiggy and Zomato were not active in Kendrapara, but they were expanding to Tier-2 cities. If they entered Kendrapara, they would have:

• Brand recognition: Customers already knew and trusted them
• Capital: They could afford to subsidize orders and acquire customers aggressively
• Operational scale: They had playbooks, technology, and teams to scale quickly

The problem: We could not compete on price or brand. Our advantage was local knowledge and merchant relationships. But that advantage was fragile.

Trade-off: We could try to build defensibility (exclusive merchant partnerships, superior service quality), but it would take time and resources we did not have.

The Product-Market Fit Question

We had product-market fit at a surface level: customers wanted hyperlocal delivery, and we provided it.

But we did not have sustainable product-market fit—the kind where the business model works, unit economics are positive, and growth is capital-efficient.

The question was not "Do customers want this?" The question was "Can we deliver this profitably and sustainably?"

The answer, at our current scale and operational model, was no.

The Decision We Made

We had three options:

Option 1: Raise capital and scale aggressively

• Pros: Could improve unit economics through scale, expand to new cities, build automation
• Cons: Required convincing investors that we could compete with incumbents, dilution of ownership, pressure to grow at all costs

Option 2: Continue operating at current scale and optimize

• Pros: Maintain control, focus on profitability, avoid dilution
• Cons: Limited growth potential, risk of competitive entry, operational burnout

Option 3: Wind down operations and apply lessons to new opportunities

• Pros: Preserve capital, avoid operational burnout, apply learnings to better opportunities
• Cons: Disappointing customers and merchants, admitting failure, starting over

We chose Option 3.

It was not an easy decision. We had customers who relied on us. We had merchants who depended on our platform for orders. We had delivery partners who earned income through us.

But we also recognized that continuing to operate without a path to sustainability would only delay the inevitable and waste more resources.

The Shutdown Process

We shut down CenterShops responsibly:

1. Customer communication: We notified customers 30 days in advance. We explained the decision honestly and thanked them for their support.

2. Merchant transition: We helped merchants transition to alternative platforms or direct delivery models. We provided data exports and operational guidance.

3. Delivery partner support: We paid out all pending earnings and provided references for other gig economy platforms.

4. Data handling: We deleted customer data per our privacy policy and retained only anonymized transaction data for analysis.

5. Financial closure: We settled all outstanding payments to merchants, delivery partners, and vendors.

Impact: The shutdown was orderly and respectful. We maintained trust even as we exited.

Trade-off: The shutdown process took time and resources. But it was the right thing to do.

The Lessons We Learned

Lesson 1: Traction ≠ Product-Market Fit

Traction proves demand. Product-market fit proves that you can deliver on that demand profitably and sustainably.

We had traction. We did not have sustainable product-market fit.

Lesson 2: Unit Economics Matter from Day One

You cannot "make it up in volume" if your unit economics are fundamentally broken. Scale amplifies problems; it does not solve them.

We should have focused on unit economics earlier, even if it meant slower growth.

Lesson 3: Operational Intensity Is a Hidden Cost

Marketplaces require ongoing operational effort. That effort scales with order volume unless you invest heavily in automation.

We underestimated the operational intensity required to run a hyperlocal marketplace.

Lesson 4: Market Depth Limits Growth

Tier-2 cities have smaller addressable markets than Tier-1 cities. You hit saturation faster.

We should have planned for multi-city expansion earlier or chosen a larger initial market.

Lesson 5: Timing Matters

We launched before Swiggy and Zomato entered Kendrapara. That gave us a window to build. But we did not move fast enough to build defensibility before they could enter.

Timing is not just about being first. It is about building fast enough to create a moat.

The Path Forward: ONDC and ChittaTaxis

The lessons from CenterShops now inform two new directions:

ONDC (Open Network for Digital Commerce)

ONDC is an open protocol for digital commerce in India. It aims to democratize e-commerce by allowing any seller to reach any buyer through any app.

Why it matters: ONDC could solve some of the problems we faced with CenterShops:

• Reduced operational intensity: Merchants can list on ONDC once and be discoverable by all buyer apps
• Shared infrastructure: Payment, logistics, and discovery are standardized, reducing platform-specific costs
• Network effects: More merchants and buyers join the network, improving liquidity

What we are evaluating:

• Can ONDC support hyperlocal delivery models?
• What are the unit economics for ONDC-based platforms?
• How do we differentiate in an open network?

Trade-off: ONDC is still evolving. Betting on it requires accepting uncertainty. But the potential to solve marketplace infrastructure problems is compelling.

ChittaTaxis (Ride-Sharing for Tier-2 Cities)

We are applying CenterShops lessons to a new opportunity: ride-sharing in Tier-2 cities.

Why ride-sharing:

• Better unit economics: Ride-sharing has higher transaction values (₹100-300 per ride vs. ₹30-60 commission per food order)
• Lower operational intensity: Fewer edge cases than food delivery (no food quality issues, no menu management)
• Larger addressable market: More people need rides than need food delivery

What we are building differently:

• Unit economics first: We are modeling profitability before launch, not after
• Automation from day one: Driver onboarding, ride assignment, and payout processing will be automated
• Multi-city playbook: We are designing for multi-city expansion from the start
• Security and compliance: Applying CenterShops security lessons (penetration testing, cloud architecture, payment security)

Trade-off: Ride-sharing has different challenges (driver safety, vehicle maintenance, regulatory compliance). But the lessons from CenterShops give us a head start.

The Real Lesson

Failure is not the opposite of success. It is part of the path to success.

CenterShops did not achieve sustainable product-market fit. But it taught us:

• How to build and launch a marketplace
• How to validate demand in Tier-2 markets
• How to design secure, scalable systems
• How to manage merchants, customers, and delivery partners
• How to recognize when to pivot

Those lessons are now assets. They inform how we approach ONDC and ChittaTaxis. They make us better operators, better product leaders, and better technologists.

The core insight: In startups, the goal is not to avoid failure. The goal is to learn fast, adapt quickly, and apply those lessons to the next opportunity.

CenterShops was not a failure. It was a learning platform. And the lessons we learned are now the foundation for what comes next.

This concludes the CenterShops series. Thank you for reading.

Continue the journey: Closing the Gap: Why Tier-2 Markets Need Local Digital Commerce