From spreadsheets to software, at the right moment

Moving from spreadsheets to software is a decision most restaurants make too early or too late. Too early, and a venue pays a monthly fee for software that does what a simple sheet did for free, with more set-up and less flexibility. Too late, and the venue runs on a fragile web of spreadsheets that only one person understands, rebuilt every Monday from exports, full of errors nobody can trace, and holding numbers that arrive too late to act on.

Spreadsheets are excellent tools. They are flexible, cheap and familiar, and many good restaurants run parts of their business on them for years. The question is not whether spreadsheets are good or bad, but whether a particular spreadsheet has stopped being the tool and started being the problem. There are clear signals when that happens.

This guide sets out the four signals that a spreadsheet has become the problem, what spreadsheets are still best for, how to judge the software ROI of moving, and how to handle data migration without losing the history that makes the numbers meaningful. It covers the inventory spreadsheet and the food cost spreadsheet in particular, because they are the two most venues rely on.

A spreadsheet can be built in an afternoon by anyone with basic skills, shaped exactly to the venue's needs, and changed whenever those needs change. It costs nothing beyond software most businesses already have. For a single venue with a capable manager, a few well-built sheets can handle costing, stock counts, rotas and weekly numbers perfectly well.

That flexibility is the spreadsheet's strength and, eventually, its weakness. A sheet that anyone can change is a sheet that anyone can break.

Some jobs suit spreadsheets even in large venues: one-off analyses, budgets and forecasts, testing a new menu's costing before it goes live, comparing supplier prices, planning an event. These are jobs where flexibility matters more than repetition, and where one person works on the sheet at a time.

Keep spreadsheets for jobs like these. The four signals below apply to spreadsheets that have become part of the venue's daily or weekly routine.

A spreadsheet has become the problem when one or more of four things is true:

Any one of these is a warning. Two or more usually mean it is time to move.

Spreadsheets are built for one person at a time. When the head chef, the bar manager and the general manager all need the same stock sheet, versions multiply: one copy on the office computer, another emailed on Tuesday, a third on someone's phone. Each is slightly different, and nobody is sure which is right.

Shared online spreadsheets help, but they bring their own problems: people overwrite each other's work, formulas get changed by accident, and there is no record of who changed what. When several people need the same information, at the same time, during the working day, software designed for sharing usually serves better.

A spreadsheet is only as current as the last time someone updated it. Many venues rebuild their weekly numbers on Monday from exports out of the till, the booking system and the card terminal. By the time the sheet is ready, it is Tuesday afternoon, and the week it describes is long past.

If decisions are made late because the numbers arrive late, the spreadsheet is costing more than it saves. Software that records the numbers as service happens makes them available the next morning, without the rebuilding.

Every spreadsheet that has been used for a while contains mistakes: a formula copied wrongly, a row that was deleted, a total that does not include the last column, a price that was typed in the wrong cell. In a small sheet, they are found quickly. In a large one built over years, they hide.

If the numbers in a spreadsheet sometimes look wrong and nobody can explain why, or if two sheets that should agree do not, the spreadsheet has become unreliable. Decisions based on unreliable numbers can be worse than decisions based on none.

Many venues have a spreadsheet that only one person understands: the manager who built it years ago, with formulas, hidden sheets and colours that mean something to them alone. When they are away, nobody updates it. When they leave, it dies.

A system that depends on one person is a risk. If the venue would struggle to run for a month without that person's spreadsheet, it is time to move what it does into something the whole team can use.

Beyond the four signals, count the hours. How long does it take each week to update the stock sheet, rebuild the weekly numbers, copy bookings into the guest list, or reconcile the till with the card terminal? Multiply by a manager's hourly cost and by 52 weeks.

Many venues are surprised by the total. A spreadsheet that takes four hours a week to maintain costs more than many software subscriptions, before counting its mistakes.

Mistakes in a spreadsheet cost more than the time spent fixing them. A labour cost that is understated for a month leads to a rota that stays too heavy. A food cost formula that misses one ingredient makes a dish look profitable when it is not, so it stays on the menu at the wrong price. A guest list with duplicates sends the same email twice and annoys the guests the venue most wants to keep.

These costs rarely appear on any report. They show up instead as profit that is a little lower than expected, for reasons nobody can quite find.

One spreadsheet deserves special care: the allergen matrix. Many venues keep it in a spreadsheet, and many keep it well. But it is the one sheet where an error can harm a guest, and where an out-of-date version is dangerous. If the matrix is a spreadsheet, it needs one owner, one master copy, and a dated update every time a recipe or supplier changes.

If the menu shown to guests is built separately from the matrix, the two can drift apart. Our guide to building an allergen matrix that stays correct covers how to keep them in step.

The inventory spreadsheet is one of the most common in restaurants: a list of items with their units, prices and quantities, updated at each stock count. For a small venue with a short menu, a weekly count of key items and a monthly full count in a spreadsheet can work well for years.

It starts to struggle when the venue has many items, several storage areas, frequent price changes, or more than one person counting. At that point, dedicated inventory software can save time and errors. Our guide to spreadsheet vs inventory software covers the decision in detail.

The food cost spreadsheet calculates what each dish costs to make, from the price of each ingredient and the quantity used. It is essential for setting prices and knowing margins. Many chefs build excellent costing sheets, and for menu development they are often better than any software.

The weakness is keeping it current. When supplier prices change, every dish that uses the ingredient changes too, and a sheet that is not updated gives the wrong margins. Our guide to recipe costing covers how to cost a dish properly.

The weekly numbers spreadsheet is often the first one to move. It is usually built by hand from several other systems, takes hours, arrives late, and is full of small errors. Software that records sales, covers, bookings and payments in one place can produce the same numbers automatically, the morning after.

If your weekly numbers come from a spreadsheet you rebuild from exports, that is usually the strongest case for moving.

Some venues keep their guest list in a spreadsheet: names, emails, birthdays and notes collected over years. It works until marketing rules come into play. Consent must be recorded and respected, unsubscribes must be honoured promptly, and personal data must be protected. A spreadsheet emailed between managers does none of these well.

A guest list is usually safer in software that records consent and handles unsubscribes. Our guide to marketing consent covers what must be recorded.

Before moving, estimate the software ROI: what the software will save and earn, against what it costs. Count the hours saved each week, the mistakes avoided, the decisions made sooner, and any extra trade it brings, such as fewer no-shows or more direct bookings. Compare with the full cost: subscription, set-up, training and the hours spent moving.

If the return is clearly positive, move. If it is close, wait until one of the four signals becomes stronger. Our guide to software ROI shows how to do the sum.

Do not move everything at once. Start with the spreadsheet that shows the strongest signals and costs the most hours, often the weekly numbers or the guest list. Move it, settle it, and only then look at the next.

Some spreadsheets will never need to move. A costing sheet the chef uses for menu development, or a budget the owner reviews once a quarter, may be best left as it is.

Choose the software by the job the spreadsheet does today, and by the moments when it fails. If the weekly numbers spreadsheet is the problem, the software must produce those numbers reliably, without exports. If the guest list is the problem, it must record consent and handle unsubscribes. Test each candidate against the real work, not a demonstration.

Our guide to choosing restaurant software without a demo haze sets out a scoring sheet built from your own shifts.

Set-up takes longer than most people expect. Menus, dish costs, tables, booking rules and user accounts all need to be entered, checked and tested before the software can replace the spreadsheet. Plan the set-up as a small project, with an owner, a list of tasks and a date.

Set up in a quiet week, and test with real examples from the spreadsheet: last Saturday's bookings, a typical order, a dish whose cost you know. If the software gives the same answer as the spreadsheet, or a better one you can explain, it is ready.

Data migration is the work of moving information from the old spreadsheet into the new software. It is usually the hardest part of the move, and the part most often underestimated. Old data is messy: duplicates, missing fields, inconsistent names, old prices, guests who never gave consent.

Clean before you move. Remove duplicates, fix obvious errors, and decide what not to move at all. Moving a messy spreadsheet into new software simply gives you messy software.

Not all history needs to move. Decide what the venue needs from the past: last year's weekly sales by service, for year on year comparisons; current dish costs and supplier prices; guests who have given marketing consent. Much of the rest can stay in the old spreadsheets, archived and read-only, where it can be found if needed.

Keeping the old spreadsheets is the simplest way to avoid losing history. Save them in one place, mark them as archived, and do not change them.

For the first few weeks, run the old spreadsheet and the new software side by side. Record the same numbers in both and compare. Where they disagree, find out why: the new software may be set up differently, or the old spreadsheet may have had an error all along.

Once the two agree for a few weeks, and the team is comfortable with the software, set a date to stop updating the spreadsheet, and tell everyone.

The reports the venue relied on in the spreadsheet need to exist in the new software, or be replaced by better ones. List them before moving: the weekly sales summary, the covers report, the food cost estimate. Check that each can be produced, and compare the first few with the spreadsheet versions.

Some spreadsheet reports exist only because the data was spread across systems. In one system, they may no longer be needed.

The team needs training on the new software, and some will miss the spreadsheet they knew. Explain why the change is being made, show the benefits for their work, and train in short sessions on real tasks. The person who built the old spreadsheet is often the best champion for the new system, if they are involved early.

Our guide to staff training that fits around service covers short, practical sessions.

Some venues should not move yet. A small venue with one capable manager, a short menu, and spreadsheets that are current and accurate may gain little from software. If none of the four signals is present and the hours are small, the spreadsheet is still the right tool.

Revisit the decision when the venue grows, a second site opens, or the person who keeps the spreadsheet leaves.

Here is an illustrative venue that moved its weekly numbers. The figures are examples.

servearound replaces the spreadsheets that are rebuilt from exports: bookings, orders, kitchen tickets and payments are recorded in one system as service happens, so covers, sales, spend per cover, no-shows and ticket times are ready the morning after. It does not import spreadsheets, so moving is a fresh start: the menu is built in the editor, each dish can carry its cost so the menu report shows margin and how much of the revenue has a cost behind it, and guest records build up from bookings and orders from the first day, with consent recorded.

Keep your old spreadsheets as the record of past trade. servearound does not handle stock, so an inventory spreadsheet that works can stay. See pricing, or get in touch to talk through the move.

When more than one person needs the same sheet at once, the numbers arrive too late, mistakes cannot be traced, or the sheet depends on one person.

No. They are excellent for one-off analysis, budgets and costing. They become a problem when they run daily or weekly routines they were not built for.

Only if it shows the four signals. Many small venues run stock well on a spreadsheet for years.

Keep it for menu development if it works. Make sure dish costs are kept current wherever margins are read.

Moving information from the old spreadsheets into the new software, ideally after cleaning it.

Decide what history matters, move only that, and keep the old spreadsheets archived and unchanged.

A few weeks, until the numbers agree and the team is comfortable.

Compare the hours saved, mistakes avoided and decisions made sooner with the full cost of the software.

One named person, usually the manager who uses the spreadsheet most, with the person who built it involved from the start.

Explain what the change saves them, train them on real tasks, and keep the old sheet available for reference during the first weeks. Most people stop missing it once the numbers arrive without the Monday rebuild.

Moving from spreadsheets to software makes sense at the right moment: when a spreadsheet is needed by several people at once, delivers its numbers too late, hides mistakes nobody can trace, or depends on one person. Until then, spreadsheets remain excellent tools, especially for costing, budgets and one-off analysis.

Check the four signals, count the hours, and estimate software ROI before moving. Move one spreadsheet at a time, starting with the one that costs most, often the weekly numbers or the guest list. Treat the inventory spreadsheet and food cost spreadsheet on their merits, clean data before migration, keep the old sheets archived, and run old and new side by side until they agree.