Case study

How we built Phone Club: a store, buyback and delivery platform on one backend 

Behind the scenes of Phone Club: a phone store, a sell-your-old-phone service and an in-house delivery system with three apps — all on one Node.js backend.

19 October 20267 min readBy Ashutosh Prajapati

Case studyASHKRIT

How we built Phone Club: a store, buyback and delivery platform on one backend

The starting point

Phone Club is a phone shop in NIT Faridabad that sells new, refurbished and pre-owned smartphones. The first goal was simple: a fast online store that makes buying a used phone feel safe. As the shop grew, so did the system — today it covers selling phones, buying them back from customers and delivering both ways with its own riders.

The pieces

The platform is eleven parts that work together:

  • ✦Store website and admin panel (phoneclub.in)
  • ✦Phone Club app for Android and iPhone
  • ✦Phone Club Sell website, admin and app for buying used phones
  • ✦A logistics portal for dispatchers and partner vendors
  • ✦Phone Club Rider, the app delivery agents use
  • ✦One Node.js API behind all of it, plus automatic uptime monitoring

One backend, separate databases

Instead of three separate servers, one Node.js and Express backend serves the store, buyback and logistics. Each has its own MongoDB database and its own logins, so a problem in one doesn't spill into another — and logistics is built as a self-contained module that can move to its own server with a one-line change.

The win is shared data without duplication: a buyback pickup becomes a logistics job automatically, and a store order's delivery status flows back to the customer's account.

Earning trust in a used-phone store

Every phone shows its condition (new, refurbished or pre-owned), grade, battery health and warranty. Checkout is Cash on Delivery, stock is reserved the moment someone orders and released if they cancel, and only customers whose order was delivered can leave a review. Returns and exchanges work per item, within each product's window.

Buying phones back, safely

Phone Club Sell gives an instant price from a short condition quiz — the deductions are applied step by step so the breakdown always adds up. Sellers book a free two-hour pickup, and the agent pays on the spot after wiping the phone in front of them.

Because the shop is buying second-hand devices, every seller is verified: a mobile OTP plus an Aadhaar Secure QR scan that is checked against UIDAI's digital signature, without ever storing the full Aadhaar number. Photos, the seller's signature and a PDF receipt are saved to the owner's Google Drive automatically.

A delivery system built for real roads

Phone Club Logistics runs every pickup, drop and exchange. Dispatchers plan jobs by date and zone; riders see their day in the Phone Club Rider app, navigate, and update each step. Since signal drops are common, updates are saved offline and sent in order once the phone reconnects. A job only closes with the customer's code, and any cash collected or paid out is recorded against it.

Partner businesses can send jobs through an API with keys and webhooks — the same way Phone Club and Phone Club Sell do.

Three apps, one codebase approach

All three apps are built with React Native and Expo, so each runs on Android and iPhone from one codebase. The shop app is controlled from the admin: banners, home-screen sections and offers change instantly, without publishing an app update.

Keeping it running

Every ten minutes, an automated check visits all five sites, the API and its database, and the SSL certificates. If anything is down — or a certificate is close to expiring — the team gets an email before customers notice.

What other businesses can take from it

Start with the part that makes money, design the backend so new parts can plug in, and add features only when they save real time. If you're running a business on calls, WhatsApp and spreadsheets, there's usually one workflow that's worth turning into software first — and that's where we'd start.

#Case study#E-commerce#Apps#Backend

Related service

API & backend

Secure APIs, databases and integrations — payments, auth, email, AI.

Explore →

(01)FAQ

Quick answers.

Why one backend instead of three separate ones?+

Customers, products and deliveries are shared between the store, buyback and logistics. One server with separate databases keeps them in sync, costs less to run and still lets each part move to its own server later.

How long does a platform like this take?+

It's built in phases. The store comes first, then features like buyback and logistics are added once the core is selling. We plan the backend so each new part plugs in instead of forcing a rewrite.

Can a small shop really need all this?+

Not on day one. Start with the store and add pieces when they save real time or bring real revenue — that's exactly how Phone Club grew.

Have a project in mind?

Tell us what you're building. We reply within 24 hours with honest advice and a clear next step.

Start a project →