Pharmacy and healthcare marketplaces, from a team that has shipped one.

Why a pharmacy is not just another provider

In a generic marketplace, the provider app is a list of jobs to accept. A pharmacy panel does more. The pharmacist decides whether an order can go ahead at all, and that decision depends on a document the patient uploads, not on what is in the basket. So the panel opens on prescriptions waiting for review, not on orders waiting for a rider.

The patient side changes too. People often order medicine for someone else: a child, a parent, a partner who is too ill to do it. A prescription in one name attached to an account in another is normal here, not a sign of fraud. We ask whether patients can keep profiles for family members, so each prescription and file sits with the right person and the pharmacist sees whose medicine it is.

The extra state at the front of every prescription order

A food order is placed, prepared and brought to the door. A prescription order has another state before any of that: submitted and waiting for review. While it waits, the patient needs to see that someone is looking at it, the payment must not be treated as final, and no rider should be assigned. When the pharmacist rejects it, the patient needs a reason and their money back, without anyone sending an email.

Then there is the handover. A rider collecting a sealed bag from a pharmacy and handing it to a patient creates two moments that may need proof: that the right pharmacy released it, and that the right person received it. We ask what your operators need recorded at each moment, such as a time, a code the patient reads out, or a photo, and build that record into the rider app and the console.

Three sides, three different views of the same patient

In a two-sided marketplace, the provider usually sees the customer's name, address and order. In a pharmacy marketplace, each side should see less. The pharmacist needs the prescription attached to this order, not the patient's whole file. The rider needs an address and a handover check, not the prescription. Your console team needs enough to resolve a complaint, and no more.

That is why Help24 keeps medical files in a PIN-protected vault. For your platform we write the view for each role down in phase one, before screens are designed, because adding a restriction after launch means changing every screen that already shows the data. Help24's Flutter mobile and Flutter Web apps share most of the business logic, so a rule about who sees what is written once and holds on both.

What we ask before we quote a pharmacy marketplace

On top of our five standard questions, a pharmacy build adds three. Who reviews prescriptions, and what do they need to see to decide? Does a handover need proof, and what kind? Who holds the patient's money while a prescription waits? The answers change the pharmacy panel, the rider app and the payment flow, so we settle them in scope rather than discover them in the build.