What we are building with ShiftOps right now
Gepubliceerd · 2 min leestijd
Most of our time at the moment goes into ShiftOps. This post is a short, honest status update: what it is, what we have been working on, and what is not done yet.
What ShiftOps is
ShiftOps is an operations tool for restaurants. It runs next to the POS you already have and puts the daily routine of a kitchen and a floor in one place: shift handovers, tasks, issue reports, opening, shift-change and closing checklists, and a view of what needs attention in the current shift. It also covers the parts that hospitality businesses have to get right and often keep on paper, such as HACCP lists and an allergen card.
It is a web app that works on a phone, a tablet and a computer. We are running it as a pilot with a restaurant, which is how we find out what actually matters on a busy evening instead of guessing at a desk.
What we have been doing lately
Features are the visible part. Lately we have spent more time on the parts that decide whether people can trust the tool.
- Allergens. The allergen card is only useful if it is never silently wrong. A dish must state all fourteen allergens explicitly, conflicting entries are caught, and changes are kept in a history so you can see what was true when.
- Safety records. HACCP status is tracked per check point, and a correction needs a reason. A record that can be changed without a trace is not much of a record.
- Photos and files. Access follows departments, uploads are checked and limited, and leftovers are cleaned up.
- Sign-in and devices. Known devices, sessions that expire, and unique login names.
- Backups and exports. An external backup location is required on a new installation, and your data can be exported as JSON, CSV and photos. Your data stays yours.
- Tests. The end-to-end test suite now runs in CI and has to pass before a release can be made.
All of this came out of a thorough audit of the whole product, followed by a round of fixes. We would rather find our own mistakes than have a customer find them.
What is not done
We prefer to say this plainly.
- Notifications by push or email are not built. For now the product does not claim to have them.
- Some interface improvements from the audit backlog are still open.
- We have not yet tested on every kind of hardware a customer might use.
What is next
Getting the hardening work released, putting ShiftOps in front of more restaurants, and keeping the product small and reliable rather than big and fragile. If you run a restaurant or a hospitality team and would like to hear more, or try it, contact us through the site.