P-01 / Case study
Medhey
A multi-vendor marketplace for shopping, selling and booking services in Bhutan.
- Project type
- E-commerce & services marketplace
- My role
- Full-stack developer
- Context
- Production platform
- Status
- Live
- Technologies
- Laravel
- PHP
- JavaScript
- MySQL
- REST APIs
01
The challenge
A marketplace has two very different customers at once: buyers who want a fast, trustworthy checkout, and sellers who need to manage products and orders without help.
The same data — products, orders, user accounts — has to serve the website and the mobile apps, stay consistent, and be protected.
02
My role
Full-stack developer. Full-stack work on Medhey, an e-commerce and services platform where buyers shop online, sellers run their stores and customers book services — on the web and through companion iOS and Android apps.
03
The approach
- 01Worked across the stack: storefront pages, backend business logic, database changes and the APIs consumed by other clients.
- 02Treated order and product flows as the critical path — validated every state change on the server rather than trusting the client.
- 03Kept user data handling conservative: authorisation checks on every account and seller action, and no sensitive details exposed in API responses.
Development process
- Think
- Design
- Build
- Test
- Deploy
- Improve
04
Architecture overview
A simplified view of how the system is organised. Internal infrastructure details are intentionally left out.
- ClientsWeb storefront and companion mobile apps
- ApplicationServer-side business logic for catalogue, cart, orders and accounts
- APIAuthenticated REST endpoints shared by web and mobile
- DataRelational database for products, orders, users and sellers
05
Key features
Buyer and seller journeys
Separate flows for customers shopping and for sellers starting and running a store.
Product & order workflows
Catalogue, cart and order handling from placement through fulfilment.
Services
Beyond physical products, the platform offers bookable services, including travel.
User accounts
Customer data handled with authorisation checks on every account action.
06
Challenges
- Consistency across clients
- Changes on the web had to stay compatible with the mobile apps using the same backend.
- Production care
- Shipping into a live marketplace means migrations, releases and fixes must not interrupt shoppers.
07
The result
The platform is live in production, serving customers through the website and mobile apps.
No metrics are published here unless they have been verified.
08
What I learned
“Working on a live marketplace taught me to think about every change in terms of the people it touches — a “small” schema change can affect a buyer at checkout, a seller in their dashboard and a mobile app release at the same time.”
— Rupesh Dahal