Orders lost between the table and the kitchen
Why an order gets lost with paper or messaging, which part of the problem Ya Sale solves and what still depends on the venue's staff.
An order gets lost when information changes hands and no one can say where it ended up: the guest ordered, the waiter wrote it down, and the kitchen either never saw it or saw it twice. Fixing this does not require a large system; it requires the order to live in one place with a visible state.
Where it breaks
- The order is taken from memory and written down afterward.
- Two people serve the same table and one does not know what the other ordered.
- The kitchen gets a paper ticket that disappears among the others.
- The guest changes something and the change never reaches the person cooking.
What Ya Sale solves
| Risk | What the product does |
|---|---|
| The order is lost while being transcribed | The guest sends it and it is stored with its table, its dishes and its notes. |
| No one knows which table it belongs to | Each table has its own code; a code from another table is not accepted as this table's. |
| The kitchen does not see it | It appears in «Pedidos y cocina» (Orders and kitchen) with its state. |
| No one knows whether it has gone out | Staff move it forward: pending, in preparation, ready, delivered. |
| The guest's phone fails | The order is already on the server; it does not depend on that screen. |
How to start without changing the whole operation
Pick one shift and a few tables
You do not need to switch the whole venue on the first day.
Publish the menu
With the dishes and prices for that shift.
Walk the full journey
A real order, from the code to delivery, with the staff who will use it.
Decide how confirmation works
Whether the order goes straight to the kitchen or a person accepts it first.