What replaces Excel and WhatsApp in food delivery

Why the spreadsheet has to go and the chat does not

A delivery business runs on two things: a shared picture of what is happening now, and a record of what happened. Chat is superb at the first and hopeless at the second. Six months of orders in a chat is not history — it is an unsearchable transcript in which the same order appears three times with corrections.

The spreadsheet fails differently. It can hold the record, but nothing enforces it: two people edit the same row, a formula gets dragged one cell too far, and by the time you notice the totals are wrong you cannot tell when they started being wrong. And critically, it is passive. It never tells you anything. Every insight has to be gone and looked for by a person who had a bad day and did not feel like it.

So the chat stays. Kitchens read it, couriers read it, it works on a cracked phone with one bar of signal. What changes is who writes into it.

What the replacement has to do

• Take orders from wherever they come. The website, the phone, the aggregator, the walk-in. If one channel has to be re-typed by hand, that channel will be missing from every report you ever run.
• Post into the chat automatically, per location. The kitchen in one district should not be reading the other district's orders. And the owner decides which fields appear: the whole shift reads that chat, and the customer's phone number does not belong in it by default.
• Answer questions without exports. “Why was Tuesday lunch down?” should be a question you ask, not a pivot table you build.
• Give the data back. Whatever you move onto must export everything in one button. A system you cannot leave is worse than a spreadsheet you can.

The failure mode to watch for

Almost every rollout that dies, dies the same way: the new system covers eighty percent of orders, the remaining twenty keep going through the chat by hand, and within three weeks nobody trusts the system's numbers because everyone knows a fifth is missing. Then everybody goes back to the spreadsheet, and the conclusion drawn is that software does not work here.

The fix is to start from the channel you are worst at capturing, not the one that is easiest to connect. If phone orders are your gap, solve phone orders first, even though the website integration is the fun one.

Where Ovirno fits, and where it doesn't

This is the case Ovirno was built around, and the pilot behind it is a sushi delivery in Poland with several pickup points. Orders arrive from WooCommerce by webhook and are pulled again every five minutes in case the webhook did not make it; a Telegram bot per pickup point drops a card into that kitchen's chat, with a catch-all bot for anything that cannot be routed; phone and address are off by default. The analyst re-reads the numbers hourly and you can ask it out loud with your hands full.

Where it does not fit: we do not integrate with tills, and we do not dispatch couriers — there is no route optimisation and no driver app. If your bottleneck is the road rather than the record, a dispatch product will serve you better, and we will say so on the call rather than after the invoice.

If this sounds like your situation, the way to find out is not a demo of somebody else's data: send one export of your sales and thirty minutes later you are looking at your own business, with observations computed from your own numbers. Ask for that, or write on Telegram — the person who answers is the one who builds the thing.

Asked before every one of these