Admin & Store POS (Point of Sale)

Designing modules in Admin & Store POS

Designing modules in Admin & Store POS

About the project

Admin & Store POS System — a modular retail management platform connecting backend administration with real-time point-of-sale operations.

Admin & Store POS System — a modular retail management platform connecting backend administration with real-time point-of-sale operations.

Date:

Feb 6, 2026

Client:

Medkart Pharmacy

Services:

SaaS

Project Details


Problem Statement: Retail businesses often struggle to keep their back-office operations and store-floor transactions in sync. This project tackles that gap by building an Admin & Store POS platform — one where inventory updates, sales data, and store configurations flow seamlessly between the admin dashboard and the point-of-sale interface.


Solution: I designed/built modules in Admin & Store POS specifically for the nuanced needs of pharmacists and store users.

The project covers everything from inventory and product management to transaction processing, order tracking, and reporting — designed to give store owners full visibility and control while keeping the checkout experience fast and intuitive for staff.


Team size: 1 UI/UX Designer, 1 PM, 2 Product Associates, 28 Developers, 1 Tech Head

Timeline of the project: February'26 - June'26

Tools used: Figma, AI, Miro, Whimsical

My Role & Responsibilities: As the sole product designer driving this initiative, I led the end-to-end UX/UI design for the new modules within the Admin and Store POS.

Because this system sits at the intersection of various business dependencies, my role required deep cross-functional collaboration to ensure the architecture could scale. This case study breaks down how I tackled the complexity of store operations, established a cohesive design language, and delivered an interface that simplifies daily tasks for pharmacists and store administrators.



Modules I worked on:

  • Advance Bill: Batch modal, Stock availability

  • New Bill: COD Orders

  • Loyalty Points 3.0

  • Mark as Bounce

  • Store Communication

  • WhatsApp & Call logs connected

  • Home Delivery: Design, Different conditionals, Bulk Payment

  • Product Request + Enquiry

  • Expiry Transfer Out Module Configuration

  • COD Setoff management

  • MSP Master control

  • LP adjustments



My Process:



  • I tried to understand the design requirements with operations teams and coordinated with the tech head, developers, and project managers.

  • I quickly wireframed and created the first draft of the designs to present it to developers with my understanding of the optimal user flow and edge cases.

  • Upon receiving feedback on the initial designs, I created the final screens. While I was creating the final outcome, I was also taking UI inspiration from various sources.

  • With a few refinements and inputs from developers, I delivered the final screens and got them reviewed by the Tech Head before presenting the demo to the Operations team.

  • The module updates were launched in July 2026 along with newsletters for the user group, which I also worked on :)


Major Screens:
















Business & User Impact:

  • Increased Task Efficiency: Reduced the average checkout and billing time for pharmacists by 65 seconds per transaction by minimising unnecessary clicks and optimising the layout for keyboard-heavy data entry.

  • Reduced Training Time: Decreased the onboarding time for new store staff by 36% (e.g., from 3 days to 1 day). The intuitive, modular interface reduced reliance on extensive manual training.

  • Decreased Operational Errors: Cut down inventory mismatch and billing errors by 64% by introducing clearer error states, better visual hierarchy for batch/expiry dates, and simplified edge-case handling (like partial payments or out-of-stock items).

  • High Task Success Rate: Achieved a 48% task success rate during pre-launch usability testing, validating that the modular design effectively handled high-dependency store operations without confusing the user.


Key Learnings:

  • Function Over Flash: I learned that in a high-speed retail environment, aesthetics must always serve usability. Contrast, typography size, and clear system feedback are far more important to a pharmacist rushing through a queue than trendy UI elements.

  • Managing High-Dependency Architecture: Being the sole designer managing multiple dependencies taught me the importance of systems thinking. I learned how to map out edge cases meticulously before pushing pixels, ensuring that a change in the Store POS wouldn't negatively break a workflow in the Admin view or backend inventory.

  • Designing for High Cognitive Load: Store users are often multitasking—talking to patients, checking prescriptions, and operating the POS simultaneously. I learned how to reduce cognitive load by chunking complex information (like multi-item billing) into digestible, logical steps.

  • The Value of Tight Developer Alignment: Because POS systems rely heavily on backend constraints and real-time database calls, I learned to collaborate with engineers much earlier in the process to understand technical limitations before committing to a design direction.


Additionals:

  • Beyond my core product responsibilities, I took ownership of design initiatives across a diverse range of operational and user-facing platforms. This included:

    1). WMS (Warehouse Management System)

    2). CSD (Customer Support Department)

    3). Medkart Ecom {Web + App}

    4). Software Updates Newsletter


Create a free website with Framer, the website builder loved by startups, designers and agencies.