WorkWorkInfoInfoLearnLearnGet Into TouchGet Into Touch
LinkedInLinkedInResumeResume

From 400 pharmacies in week one to 3,000+ today — a mobile app built for how Nepal's pharmacy owners actually work

I designed mobile inventory logging with autocomplete and notebook-style rows — no POS training, no scanner hardware. Four hundred pharmacies signed up in the first week. Owners now save about 1.5–2 hours a day compared to paper.

Timeline12 Months(24/25)
RoleProduct Designer
PlatformAndroid/iOS
Outcome3,000+ pharmacies
Mero Pharmacy Manager app screens across sales, inventory, and customer management

Business Context

Competitors reached about 12% adoption in smaller cities. Mero signed 400+ pharmacies in week one and now serves 3,000+.

Mero earns from pharmaceutical ads today, with a planned move to wholesaler marketplace fees (2–3% on supplier orders). The product only works if owners open it daily. Shops that log inventory fewer than three times a week do not see ads and do not come back.

Training, desktop software, and setup time kept most owners on paper. Only about 12% of Nepal's ~15,000 registered pharmacies used competitor tools. More daily use meant more ad views — and a path to connecting shops with wholesalers.

The design had to beat the notebook on speed, not beat it on features. If logging took longer than writing by hand, owners would revert.

Research and Problem Discovery

Problem statement

User: Small pharmacy owners (45+, low digital literacy, Nepali-first, ₹8K–₹15K Android on 2G/3G).

Action: Log daily sales (40–60 entries), track customer dues, check stock, reorder from suppliers.

1. Wrong layout: POS apps use SKU, batch, and barcode columns. Owners track medicine, quantity, and customer — like their notebook.

2. Typing too slow: “Esomeprazole” on a ₹8K phone took about 18 seconds per line. Forty medicines a day meant twelve minutes of typing — slower than five minutes in a notebook.

3. Training took too long: Competitor POS needed 4–6 hours of training and two days to set up. Owners could not shut the shop that long.

Result: Digital was slower and harder than paper. About 70% went back to the notebook within two weeks. Competitor adoption in smaller cities stayed near 12%.

Field observation (8–10 pharmacy visits)

Eight to ten visits across Kathmandu and Bharatpur over two months, two to three hours each.

  • 6 of 8 owners opened their notebook first when shown digital tools
  • All 8 had smartphones (₹8K–₹15K Android)
  • 2 of 8 had desktop computers; neither was in daily use
  • 7 of 8 said: “I tried digital before. Too complicated. Back to the notebook within two weeks.”

User interviews (15–20 pharmacy owners)

Thirty to forty-five minute interviews on daily workflow, pain points, and past digital attempts.

  • Competitor POS training averaged 4–6 hours
  • Most owners stopped using digital tools within two weeks of training
“The trainer spent 4 hours teaching me, and I still forgot after he left”
“Barcode? Most medicines here don't have barcodes”
“I can't afford ₹15K for scanner hardware”
“Typing takes too long. I already know the medicine names; I just want to log quickly”

Competitor benchmark

PlatformDesktop POSDesktop + mobile webMobile appMobile-first
Training required4–6 hours3 hours2 hours<10 minutes
Hardware neededScanner (₹15K)DesktopNoneNone
Setup time2 days1 day1 hour10 minutes
Input methodTyping onlyTyping onlyTyping onlyAutocomplete + typing
LanguageEnglish onlyEnglish onlyEnglish + NepaliNepali-first
Adoption (smaller cities)~8%~15%~10%400+ week 1

Options Considered and Decision

Option A

Desktop POS system

Hardware partner, barcode scanners, desktop software with inventory reports and analytics.

Rejected

₹28K upfront, half a day of training, and a year to roll out — and it still did not match how owners already worked.

Option B

Web app

Mobile-friendly web app, offline support, no app store install, typing with autocomplete.

Considered

No install step, but typing stayed slow, no home-screen icon, and offline was harder to get right than native.

Option C · Chosen

Mobile-first app

Native Android with autocomplete, notebook-style rows, offline sync, Nepali and English UI, SMS due reminders, and WhatsApp supplier reordering.

Selected

Autocomplete cut entry from about 18 seconds to under five. The layout matched the notebook. No training session. Worked on ₹8K phones over 2G.

Why mobile-first won

  • Autocomplete cut typing from about 18 seconds to under five per medicine
  • Owners saved 1.5–2 hours a day from week one compared to manual bookkeeping
  • The layout read like a notebook; no training session required
  • Ran on ₹8K Android over 2G — no scanner or desktop needed
  • Faster daily logging kept owners coming back, which supported ads and a future wholesaler marketplace

Tradeoff: what we gave up

Analytics depth

Lost: Profit margins, trend charts, and per-SKU breakdowns.
Why acceptable: Owners wanted something simpler than a dashboard, not more charts to learn.
Revisit when: When owners start asking for monthly sales trends.

Barcode scanning

Lost: Fast scan entry for barcoded medicines.
Why acceptable: Most stock in smaller cities has no barcode. Autocomplete works for any name they type.
Revisit when: When barcode coverage becomes common in urban shops.

Multi-user / multi-location

Lost: Shared accounts for chains or multiple staff.
Why acceptable: Most Nepal pharmacies are one shop, one owner.
Revisit when: When chain pharmacies become a meaningful share of users.

Real-time supplier integration

Lost: One-click reorder through supplier APIs.
Why acceptable: Suppliers in smaller cities order over WhatsApp, not web portals. API work would take months.
Revisit when: When the wholesaler marketplace launches.

The app that replaces the notebook must be simpler than the notebook, not more complex.

The Design and Decision by Decision

Screen 1 of 5

Screen 1: Home dashboard

Weekly totals on open

Decision

Show last week's NPR total and a sales vs expenses card above every shortcut on home.

Why

Owners open the app to see how the shop is doing. That answer should not require opening reports.

Rejected

A charts dashboard that needed training to read.

Mero Pharmacy Manager home screen with weekly NPR totals, services grid, and bottom navigation

Services grid for daily tasks

Decision

Four equal tiles: Price list, Sales & Expenditure, Customer Record Management, and Request A Feature.

Why

A grid like mobile banking apps in Nepal: one tap per daily task, no buried menus.

Rejected

A hamburger menu with workflows two or three levels deep.

The Outcome

Beta testing (5 pharmacies, 8 weeks)

Five pharmacies, weekly visits, eight weeks of real use.

  • Week 1: All 5 set up in under 10 minutes (competitor POS needed 4–6 hours of training)
  • Week 2: 4 of 5 asked for autocomplete after a few letters — full names were too slow to type
  • Week 4: All 5 reported saving 1.5–2 hours a day compared to the notebook
  • Week 8: All 5 still logging daily

Autocomplete was not optional. Typing "Paracetamol" on a ₹8K phone took about 18 seconds. After three or four letters, entry dropped to under five.

From Pilot to Platform: 7.5x Growth

Week 1

400

pharmacies
Month 3

~900

estimated
Month 6

~1,800

estimated
Current

3,000+

active

Mero grew from 400 pharmacies in week one to 3,000+ today. Competitors in smaller cities stayed near 12% adoption for years. Mero became Nepal's largest mobile pharmacy app.

Competitor POS tools took years to reach 12% adoption. Mero reached about 20% of Nepal's ~15,000 pharmacies — mostly on phones, with setup in under ten minutes.

Time Savings at Platform Scale

Per pharmacy

1.5–2

Hours saved daily

Manual bookkeeping took 2–3 hours a day. With the app, about 30–45 minutes.
Platform-wide

5,250

Hours saved daily

3,000+ pharmacies at roughly 1.75 hours saved each — about 5,250 hours a day across Nepal.

What the scale unlocks next

The app is free and ad-supported today. At 3,000+ pharmacies, the product is ready to connect shops with wholesalers — the next step for the business.

Next case study

3 min read
siddart

© 2026 Sidd Art | All Rights Reserved.

Last updated on Jan 01, 2026

Find Me Online

  • Linkedin
  • Instagram
  • Figma Profile
  • Resume

Around the Site

  • Info
  • Learn
  • Articles
  • Get into touch

Things I Built

  • Stacklite.live
  • Polaroid Camera