AlphaMed

In one paragraph

AlphaMed connects patients to licensed partner pharmacies. Patients order from an aggregated catalogue, pharmacies receive and fulfil those orders in a dedicated partner app, and a Go backend routes each order to a pharmacy that can actually fill it.

The problem

Finding a specific medicine in stock means calling pharmacies one at a time, or physically walking between them — while ill, which is the entire context. Meanwhile pharmacies have no visibility of demand they are missing.

What I built

• A patient app — search an aggregated catalogue across partner pharmacies, order, and track fulfilment.

• A partner fulfilment app — pharmacies accept, prepare and dispatch orders against their own stock.

• A Go backend holding the catalogue, routing each order to a pharmacy that can fill it, and tracking through to delivery.

The constraint that shaped everything

Medicine is not a general marketplace category, and treating it like one produces something worse than useless.

Fulfilment must route to a licensed pharmacy that genuinely holds the item. That single constraint moves the interesting problem away from catalogue breadth — where a normal marketplace competes — and onto availability and routing.

Showing a patient a medicine that no nearby partner can dispense is worse than showing them nothing: they stop searching, believing the problem is solved.

So the catalogue is a view over what partners can actually supply right now, not a master product list with availability bolted on. An item that cannot be routed does not appear. That makes the system look smaller than a naive competitor and behave far better — every result is a result you can act on.

Stack

Go · MongoDB · Flutter · partner-scoped auth and order routing