Order by supplier
- Products
- Collected
- Person in charge
- Visible
- History
- Shared
Collect the restaurant’s requests, prepare the order by supplier and make steps and history visible.

mayo takes requests out of scattered notes and messages, into a path that both the people working and the people checking can follow.
Bring the requests of everyone working in the kitchen into the same order.
Choose the supplier and add products before the summary.
Review the order and, when needed, send it for approval.
Orders of 70 or 80 lines move from notes to WhatsApp. Several people ask for different products and the latest version is never certain.
Requests, products and summary stay in the same flow. The owner can see delegated orders without rebuilding them from messages.
“You can’t make sense of the order that was sent or the goods that were received.”
Start from the supplier, add the products, re-read the summary and request an approval when needed. That way the order stays readable afterwards too.

The summary makes the order reviewable before approval. The shared history then keeps a reference point for whoever has to check or reconstruct a decision.
You see delegated orders and find the history again without asking every time which message holds the right version.
You collect the requests and prepare the order in the same path, with a summary that is easier to review.
To manage supplier orders without losing them on WhatsApp, collect the requests into a shared order, organise products and supplier, re-read the summary and ask for an approval if necessary. mayo also keeps a shared history: the order does not stay hidden in a conversation.
Start from a shared order, readable and verifiable before it becomes a lost message.