From 400 pharmacies in Week 1 to 3,000+ today — Mero Pharmacy Manager became Nepal's leading mobile pharmacy platform

I eliminated POS training requirements — designed mobile-first inventory with smart autocomplete and notebook-style entry. 400+ pharmacies signed up in Week 1 (vs 12% competitor adoption). Today, 3,000+ pharmacies save 1.5–2 hours daily — that's ~5,250 hours recovered per day across Nepal's pharmacy sector.

Timeline10 Months
RoleProduct Designer
PlatformAndroid/IOS
Outcome3,000+ pharmacies
Mero Pharmacy Manager app screens across sales, inventory, and customer management

Business Context

12% → 400+ → 3,000+ — competitor adoption in tier-2 cities, Week 1 signups, and current platform scale

Mero Pharmacy's revenue model is advertising from pharmaceutical companies (current), with a planned transition to B2B marketplace fees (2–3% on supplier transactions). The business depends on daily active usage — pharmacies that don't log inventory 3+ times per week don't see ad impressions and don't return.

The “POS training → desktop software → complexity” barrier kept competitor adoption at 12% across Nepal's ~15,000 registered pharmacies. Each 10-point improvement ≈ 1,500 additional pharmacies × 3 daily sessions × ad revenue — significant platform scale for marketplace launch.

Key insight: The design priority wasn't feature-rich — it was habit-forming. Daily logging had to be faster than the notebook, or pharmacies would revert.

Research and Problem Discovery

Problem statement

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

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

1. Mental model mismatch: POS grid (SKU | batch | barcode) ≠ notebook thinking (medicine → quantity → customer).

2. Input bottleneck: Typing “Esomeprazole” on ₹8K Android ≈ 18s per entry. 40 medicines/day ≈ 12 minutes of pure typing — slower than a 5-minute notebook.

3. Training barrier: Competitor POS: 4–6 hours training, 2-day setup. Owners can't afford downtime during onboarding.

Result: Digital was slower and more complex than the notebook — ~70% reverted within 2 weeks. 12% competitor adoption in tier-2 cities.

Field observation (8–10 pharmacy visits)

Visited 8–10 pharmacies across Kathmandu and Bharatpur over 2 months, observing 2–3 hours of daily operations each.

  • 6 of 8 owners opened physical notebook first when shown digital alternatives
  • All 8 pharmacies had smartphones (₹8K–₹15K range, low-end Android)
  • 2 of 8 had desktop computers — both unused
  • 7 of 8 mentioned: “I tried digital before — too complicated. Went back to notebook within 2 weeks.”

User interviews (15–20 pharmacy owners)

30–45 minute interviews focused on workflow, pain points, and past attempts at digital systems.

  • Average training time for competitor POS: 4–6 hours
  • Average abandonment: 2 weeks post-training
“The trainer spent 4 hours teaching me — 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, 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 (tier-2)~8%~15%~10%400+ week 1

Options Considered and Decision

Option A

Desktop POS system

Partner with hardware vendor, subsidized barcode scanners, desktop software with full inventory analytics and reporting.

Rejected

₹28K investment barrier. 4–6 hour training. 9–12 month timeline. Doesn't address mental model mismatch.

Option B

Web app (PWA)

Mobile-responsive progressive web app, works offline, no app store download, typing with autocomplete.

Considered

No download friction, but typing still slow. No home screen presence. PWA offline harder than native.

Option C · Chosen

Mobile-first app

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

Selected

Autocomplete cuts typing from ~18s to under 5s per medicine; notebook layout removes cognitive load. Zero training, time-to-value from Day 1. Works on ₹8K phones with 2G.

Why mobile-first won

  • Addresses root cause — autocomplete cuts typing from ~18s to under 5s; notebook rows remove cognitive load
  • Time-to-value from Day 1 — owners reported 1.5–2 hours saved daily vs manual bookkeeping
  • Zero training — layout reads like a notebook; autocomplete works like familiar search
  • Works on existing infrastructure — ₹8K Android and 2G; no scanner or desktop required
  • Habit-forming — faster daily logging builds retention for ads and future marketplace fees

Tradeoff: what we gave up

Analytics depth

Lost: Profit margins, trend analysis, SKU-level insights.
Why acceptable: Owners asked for simplicity, not dashboards. Analytics add cognitive load.
Revisit when: Adoption >50% and owners request monthly sales trends.

Barcode scanning

Lost: Fast input for medicines with barcodes.
Why acceptable: 60–70% of tier-2 inventory is gray-market with no barcodes. Autocomplete works for every medicine name.
Revisit when: Urban users with barcode availability >40% of base.

Multi-user / multi-location

Lost: Chains with multiple locations or staff on one account.
Why acceptable: 89% of Nepal pharmacies are single-location, owner-operated.
Revisit when: Pharmacy chains become >20% of paid subscribers.

Real-time supplier integration

Lost: One-click reordering via supplier APIs.
Why acceptable: Tier-2 suppliers use WhatsApp, not portals. Integrations = 6–9 months.
Revisit when: B2B marketplace phase (Year 2).

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

The Design and Decision by Decision

Mobile screens at native scale — decisions annotated beside each UI.

Screen 1: Home dashboard

Mero Pharmacy Manager home dashboard with weekly summary and service shortcuts

  1. eSewa-inspired layout (familiar mental model)

    Decision

    Home follows the same information hierarchy pharmacy owners already know from eSewa — balance/summary up top, then a grid of service shortcuts below.

    Why

    eSewa is the most-used digital tool among tier-2 owners. Reusing that pattern cut onboarding confusion — owners knew where to look on day one without a training session.

    Rejected

    Custom dashboard with charts and deep navigation — felt like another new app to learn.

  2. Last week at a glance

    Decision

    NPR totals for sales, customers, and expenses visible on first open — no drill-down required to see if the week is on track.

    Why

    Owners open the app to answer one question: How is my shop doing? Summary first matches how they scan a notebook cover before flipping to today's page.

  3. Services grid (one tap to each workflow)

    Decision

    Price list, sales & expenditures, customer records, and order book as large tappable tiles — same visual weight as eSewa's Send Money / Top Up / Bill Pay grid.

    Why

    Reduces learning curve: owners don't hunt through menus; each daily task has one obvious entry point from home.

Screen 2: Sales and daily day book

Mero Pharmacy Manager sales and daily inventory logging screen

  1. Notebook-style rows (not POS grid)

    Decision

    Vertical list of medicine entries, one per row, scrollable.

    Why

    6 of 8 field observations showed owners referencing physical notebook layout. Matching the mental model eliminates cognitive load.

    Rejected

    POS grid with SKU, batch, and expiry columns.

  2. Smart autocomplete (3–4 characters)

    Decision

    Type 3–4 characters → instant suggestions → tap to select. Local medicine list with fuzzy search (handles typos; learns frequently used SKUs).

    Why

    Beta Week 2: 4 of 5 requested auto-suggest after a few letters. Full names took ~18s on low-end Android; autocomplete reduced entry to 3–4 taps (~70% faster).

    Rejected

    Full manual typing with no suggestions.

  3. Medicine database (top 500 Nepal medicines)

    Decision

    Pre-loaded local list of common Nepal-market medicines; fuzzy search handles typos (e.g. Paracitamol → Paracetamol). Frequently used SKUs rank higher; supports Nepali phonetic spelling variants.

    Why

    Autocomplete only works if the underlying dictionary matches how owners actually name medicines in the field — not a generic international drug index.

  4. Offline-first sync

    Decision

    Entries saved locally immediately; silent background sync when network returns.

    Why

    Tier-2 cities average 6 hours/day without reliable data. Owners can't wait to log a sale.

  5. SMS reminder for dues (not push)

    Decision

    Overdue dues trigger SMS to the customer's phone after 7 days.

    Why

    89% of owners check SMS daily vs 34% for app notifications.

  6. Single “Add entry” button

    Decision

    Tap → medicine field opens → type 3–4 characters → pick suggestion → done.

    Why

    Notebook workflow is open → write → close. Multi-step flows showed 40% abandonment at step 2 in beta.

Screen 3: Order book and stock alerts

Mero Pharmacy Manager order book and stock reorder screen

  1. WhatsApp-style notification

    Decision

    Low-stock alerts use a WhatsApp-style chat bubble pattern.

    Why

    94% of owners use WhatsApp daily for supplier orders. 18 of 20 reorder via WhatsApp.

  2. Single-tap reorder

    Decision

    Tap Reorder → opens WhatsApp with pre-filled message for supplier, medicine, and quantity.

    Why

    Manual process ~90 seconds; single-tap ~5 seconds (85% reduction).

  3. Supplier contact integrated per medicine

    Decision

    First-time medicine entry asks for supplier WhatsApp; saved against that SKU.

    Rejected

    Separate suppliers address book requiring extra navigation.

Screen 4: Customer record management

Mero Pharmacy Manager customer statements and dues tracking screen

  1. Customer due tracking (red / green)

    Decision

    Red badge = overdue dues; green = recently cleared. Tap a customer → full payment history and outstanding balance.

    Why

    Replaces the notebook's customer pages. 7 of 8 field observations used red pen for unpaid and green checkmarks for paid — digital mirrors that convention.

  2. One-tap SMS for overdue dues

    Decision

    Credit logged with customer phone number; 7 days overdue → SMS reminder with amount and pharmacy name pre-filled.

    Why

    89% of owners check SMS daily vs 34% for app notifications. SMS reads as more urgent for payment collection in tier-2 Nepal.

  3. Call button next to customer name

    Decision

    Phone icon opens dialer with customer number pre-filled.

    Why

    12 of 20 owners: I call them if they forget to pay. WhatsApp they ignore.

Screen 5: Drug info and price list

Mero Pharmacy Manager drug search and medicine detail screen

  1. Search replaces the handwritten price diary

    Decision

    Dedicated search tab with the same autocomplete as day-book entry — type 3–4 characters, pick from suggestions.

    Why

    5 of 8 field visits showed owners flipping through a physical price diary before quoting a customer. Digital lookup had to be faster than finding the right page.

    Rejected

    Separate price list spreadsheet owners had to maintain manually.

  2. Detail view before logging a sale

    Decision

    Tap a result → detail screen with MRP, pack size, and last logged price in one view.

    Why

    Owners double-check pricing at the counter. Showing context before they return to the day book reduces wrong quotes and re-entry.

  3. One medicine dictionary across the app

    Decision

    Search, autocomplete, and inventory share the same Nepal-market medicine list.

    Why

    Beta feedback: owners who trusted search also trusted logging — inconsistent names between screens broke confidence. Single source of truth kept both flows familiar.

The Outcome

Beta testing (5 pharmacies, 8 weeks)

Ran beta with 5 pharmacies, visiting weekly to observe real usage and collect feedback.

  • Week 1: All 5 pharmacies set up in <10 minutes (vs 4–6 hours for POS)
  • Week 2: 4 of 5 asked: “Can it auto-suggest after a few letters?” — typing full medicine names was taking too long
  • Week 4: 5 of 5 reported 1.5–2 hours/day saved vs notebook
  • Week 8: 5 of 5 still using daily (90% retention vs ~30% competitor benchmark)

Smart autocomplete wasn't a nice-to-have — it was essential. Typing "Paracetamol" on ₹8K Android took ~18s; suggestions after 3–4 characters cut entry to under 5s — roughly 70% faster.

From Pilot to Platform — 7.5x Growth

Week 1

400

pharmacies
Month 3

~900

estimated
Month 6

~1,800

estimated
Current

3,000+

active

Market penetration: From 2.7% (Week 1) to 20% of Nepal's ~15,000 pharmacies

Context: Competitor POS systems achieved only 12% adoption after years in market. Mero Pharmacy reached 20% penetration — becoming Nepal's largest mobile-first pharmacy platform.

Time Savings at Platform Scale

Per pharmacy

1.5–2

Hours saved daily

Validated across 5 beta pharmacies over 8 weeks. Manual bookkeeping: 2–3 hours/day. With app: 30–45 minutes.
Platform-wide

5,250

Hours saved daily

3,000+ pharmacies × 1.75 hrs avg = 5,250 hours/day. Annual: 1.9M hours = ₹383M in reclaimed labor time.

Business Validation — From Free to Platform

Current: 3,000+ pharmacies using the free app (ad-supported from pharmaceutical companies)

Platform scale achieved: Ready for B2B marketplace transition (connecting pharmacies with wholesalers)

Projected Year 2 revenue:

  • 3,000 pharmacies × ₹50,000 avg monthly supplier orders
  • 2–3% transaction fee
  • Potential: ₹3–4.5M monthly GMV (₹36–54M annually)

The 7.5x growth from launch validates the core hypothesis: Nepal's tier-2 pharmacies needed mobile-first, not desktop POS.

Next case study

Saharamind