What the client came with
Aid comes from different sources and goes to different people. Without a single record it’s impossible to know what’s in the warehouse and who has already received it.
What we built
- A public site with request submission
- A warehouse with stock levels and movements
- Distribution of aid across organizations
- Telegram Mini App for coordinators
- A superadmin level above the organizations
What’s inside the panel
- Requests and their statuses
- Warehouse: intake, issue, stock levels
- Organizations and coordinators
- Distribution reporting
Details worth knowing
The pain was put into words by the client and moved to the home page: “Notebooks, Excel and chaos in the warehouse”. That’s where we started.
The build is two-sided: on one side organizations run the warehouse, on the other people submit requests for aid. The system matches stock levels with needs, so aid doesn’t sit in the warehouse and isn’t handed out twice.
Warehouse accounting became the way in: an organization needs it on its own, before the second side even joins.
Stack
- Laravel
- Telegram Mini App
- MySQL
Numbers verified against the project
How it looks
More from this niche
We’ll build a system like this around your process
Come without a spec — we’ll write it together on the first call.