Business system
Reference buildMeridian Dispensary
A dispensing and inventory system for a pharmacy: prescriptions, batch tracking, expiry control and reordering in one place.
- Dated
- 2025
- Product type
- Business system
- Technologies
- 4
The system, across devices
The short version
Why it exists.
Every build here answers a specific operational problem. This is the one it answers.
- 01
What was wrong
Dispensing recorded on paper and stock counted by eye. Expiry dates were found during an audit rather than before one, and reordering depended on whoever happened to notice a gap on the shelf.
- 02
What we built
A dispensing record tied to the stock it draws down, with batches and expiry tracked per item, interaction checks at the point of dispensing, and reorder points that raise themselves.
- 03
What changes
Expiring stock surfaces weeks ahead instead of at audit. Reordering happens on a threshold rather than a hunch, and every dispensed item has a record attached to a batch.
What it does
The parts that matter.
Not a feature list — the four things this product is actually for.
Dispensing on the record
Each prescription is logged against the batch it came from, with who dispensed it and when.
Batches and expiry
Stock is held per batch, so expiry is a property of the item rather than a note on a shelf.
Checks at the counter
Interaction and dosage checks run at the moment of dispensing, not after the fact.
Reordering that raises itself
Thresholds per item, so the gap on the shelf is flagged before anyone walks past it.
What it took
The disciplines behind it.
How it is built
The technologies.
Chosen because they suit the problem and because a team other than ours can maintain them.
- Next.js
- TypeScript
- PostgreSQL
- Prisma
This build has a full interactive system behind it in the showcase — the storefront, the operations side, and the connection between them.
Open the systemStart a project
You have seen what we build. Now let us build yours.
Tell us which part of the business you want to run better. We will come back with how we would approach it, what it would take, and whether we are the right people for it.
- 01An engineer reads the brief — not a sales inbox.
- 02You get a written response on approach, risk and rough shape of effort.
- 03If it looks like a fit, a call to pressure-test the scope.