Procura
Procurement software
Inventory, suppliers, reorder planning and purchase orders in one connected application.
Runs purchasing at a veterinary hospital.
Drag sideways to turn it.
Try it
A small working version of the workflow, running in your browser with fictional data.
Reorder check
Sample dataLower a count below its reorder point, then draft the order.
| Item | On hand | Reorder at | Supplier |
|---|---|---|---|
| Nitrile gloves, M (box) | 20 | Meridian Medical | |
| Syringes 3 ml (box) | 6 | Meridian Medical | |
| Gauze swabs (pack) | 50 | Tanjung Clinical | |
| Surgical masks (box) | 40 | Tanjung Clinical |
See stock levels and reorder points before deciding what to buy.
Review reorder planning alongside a fictional stock list.
Follow the order workflow using fictional suppliers and sample amounts.
The problem
Stock levels, supplier information and purchasing decisions are difficult to follow when they live in separate spreadsheets and conversations.
What I built
I built a procurement application that connects inventory, suppliers, purchase orders, requests for quotation and planning. It brings the buying workflow into one place instead of treating each document as a separate task.
How it works
- Review stock and reorder points
- Plan purchases by supplier
- Draft and review orders
- Track the purchasing history
Under the hood
Go serves the web interface and embeds its assets in a single binary. SQLite keeps the inventory and purchasing records together. Spreadsheet import and unit-of-measure mappings support existing operational data.
What this page does not claim
The screenshots use a separate seeded demo database. No supplier is contacted and no purchase is submitted from this portfolio. Operational records and client results are not published here.
What should your software do?
Tell me what your team does today, what gets repeated, and what a better workflow would look like.