[ WORKS · WEB APP ]
Daoke
An inventory and process application for produce: every stage from delivery to packing, recorded with weight, photo and the person responsible, instead of scattered across paper and chat.
- Web App
- Fullstack
Private build — no public URL to link.
- Client
- Daoke
- Role
- Development
- Collaboration
- With Skalatama
- Status
- Private build
The problem
Produce moves through a chain of hands — delivered by a supplier, sorted, packed, shipped — and each stage was written down in its own way: a weighing slip, a photo on someone's phone, a note in a group chat. By the time anyone asked what happened to a batch, the answer was spread across three of those.
The people who needed the numbers were not the people entering them. Management wanted stock, waste and staff output; the floor needed to keep working with one hand while holding a crate of vegetables in the other.
What I built
Daoke gives each stage a screen of its own: newly arrived produce, produce in process and finished produce, plus a warehouse view — each recording supplier, staff, weight and photographs in a single entry. A statistics view reads those same records back as stock and staff figures, and access is set by role, so a floor user sees their stage and not the rest of the system.
The interface is built for that one-handed context: capture straight from the camera, weight as the main action, and a preview of the photographs before a record is saved.
What shipped
A screen per stage
Newly arrived, in process and finished produce as separate screens, plus a warehouse view and a daily recap.
Photographs on every record
Weight plus images per entry, with a viewer to check them before or after the fact.
Statistics
Stock and staff figures drawn from the entries themselves, filterable by date.
Role-based access
Each person sees only the stages they work on, not the whole operation.
Supplier & staff records
The reference data the floor works from, kept in one place.
Built for the floor
Camera capture, large targets, and pages that stay usable on a slow connection.
Outcome
- A batch is one record with its photographs, instead of a search through a group chat.
- Stock and staff figures come from entries the floor already makes, so nobody keeps a second set of books.
- A disputed weight can be checked against its photographs rather than argued about.
