CASE STUDY 04 / PHARMACY E-COMMERCE
Szimpatika
Making pharmacy selection part of the shopping journey
Read the case study
CENTRAL DESIGN QUESTION
How should pharmacy selection shape the shopping journey?
Szimpatika needed a storefront that combined shopping with editorial content while supporting pharmacy-specific pricing and a distinct prescription experience. I owned the UI redesign, including a custom homepage and a map-based pharmacy selector. The design brought the required pharmacy choice into the shopping journey and used a clear visual change to distinguish prescription mode. The redesigned storefront went live.
MY ROLE
Product designer responsible for the storefront UI redesign.
SCOPE
A homepage combining shop, blog and news content; map-based pharmacy selection; distinct visual treatment for prescription mode.
DELIVERY
A redesigned storefront that reached production.
A pharmacy choice changed the shopping context
The platform’s pricing model depended on the selected pharmacy. Users could add products to the cart only after choosing their preferred pharmacy. That made selection a prerequisite for shopping, with a direct effect on the meaning of the prices they saw.
This constraint needed to be understandable during the journey. If the interface treated pharmacy selection as incidental account information, people could reach a shopping action without having established the context required to complete it.
My work translated that requirement into the storefront UI. The pharmacy choice needed to be visible enough to be recognised as part of shopping, and the selection interaction needed to fit within the broader product experience.
FIG 1 · THE SELECTION FLOW
Pharmacy selection establishes the context required before a customer can add products to the cart.
Bringing the required choice forward
I designed a map-based pharmacy picker that brought the selection into the flow before users could add products to the cart. The map gave the choice a geographic context, while the storefront provided a visible entry point to the selection.
The reasoning was tied to the platform’s commercial model. Selecting a pharmacy established the context in which the customer could proceed. Making that step part of the interface helped explain why the product experience depended on a choice that an ordinary webshop might not require.
I treated the picker as part of the shopping interaction, rather than a separate locator feature. Its purpose in this project was to support the required pharmacy selection. That connection between the business rule and the user’s next action shaped its place in the experience.
The design still involved a trade-off: an early required choice introduces work before the customer can add an item. The reason for accepting that step was the dependency itself. The interface needed to help the person complete it and understand its relevance, rather than allow them to continue under an undefined pricing context.
FIG 2 · MODE SWITCH
Distinguishing prescription mode
Prescription products followed different fulfilment constraints within the project, including a restriction on delivery. I designed a distinct mode using a change in brand colour, supported by the visible prescription label in the navigation.
The colour change provided an immediate visual signal that the customer had entered a different shopping context. The label gave that context an explicit name. This retained continuity with the storefront while making the mode change recognisable.
The distinction mattered because familiar commerce patterns can create expectations about what happens after selection. A customer who sees the same presentation everywhere may assume that the same fulfilment options apply everywhere. The prescription treatment was intended to bring attention to the different context before those expectations carried further into the journey.
The delivery restriction described here was a requirement of this project. The case demonstrates how I communicated that constraint in the interface, rather than offering a general statement about pharmacy regulation in other markets.
FIG 3 · CONTENT HIERARCHY
Deals and products lead the homepage. The magazine sits below, giving visitors a reason to come back without crowding the shop.
Giving shopping and editorial content a shared homepage
The storefront also needed to accommodate a blog and news content. I designed a custom homepage that brought those content types together with the shopping experience.
The challenge was one of hierarchy. Product browsing and editorial reading are different activities, and the homepage had to make both available without requiring every section to receive the same emphasis. The interface needed to support a visitor arriving with a product in mind while also giving health-related content a place in the wider experience.
I handled that through the composition of the homepage and the organisation of the navigation. Shopping, editorial areas and the pharmacy-selection requirement belonged to one storefront, with clear roles for each. The design work connected these parts visually without implying that content reading and purchase preparation were the same task.
This made the homepage a meaningful part of the redesign. Its job extended beyond presenting a catalogue: it introduced the range of content and services while keeping the required shopping context accessible.
Carrying the rules into the interface
The most consequential decisions in this project concerned how business constraints became visible to customers. Pharmacy-specific pricing shaped the selection flow. The prescription fulfilment requirement shaped the distinction between modes. The combination of shop and editorial content shaped the homepage hierarchy.
Those requirements were given parts of the product context. My responsibility was the UI response: where the required choice entered the experience, how the relevant modes were recognised and how the homepage brought the content together.
This separation is important to how I describe the project. I owned the redesign of the interface; I do not claim to have created the platform’s pricing model or determined the underlying fulfilment rules.
06 · WHAT THE WORK ACHIEVED
How should pharmacy selection shape the shopping journey?
07 · TAKEAWAY
Szimpatika reinforced the value of making the source of a constraint understandable. A required step is easier to interpret when its connection to the shopping task is visible.
NEXT CASE STUDY · 05 / 06
Problem Register
Helping state institutions share and solve digital service problems