“Which price list did you use?”
Omar has Lumen Gloves' monthly Excel file open. Sara has a side sheet left over from before Beezr. The glove prices don't match. Both files look official. Neither has coffee stains, so that's no help.
This is when a spreadsheet becomes a system. People depend on it to agree on work. We'll look at the signs, test your sheet, then plan what comes next.
When a spreadsheet becomes a system, what changes?
Excel deserves a fair start. A quick cost check needs room to think. You may want to change a guess and compare results. A sheet suits that work.
Sometimes the main software makes a small task too hard. Sometimes it lacks the field you need. A side sheet fills the gap. Treat that as a clue about the work, not a fault in the person.
The change comes when the sheet becomes a shared set of instructions. Who should call the supplier? Which price is cleared for use? Who may change it?
Think of a notebook used as the office rule book. It can hold the rules. But someone still has to check who follows them.
Here's how the Excel cycle can take hold:
How the side sheet returns
- Commission a custom system — pay for the work you know about.
- Meet a new need — the process changes after launch.
- Make a temporary sheet — use it while the change waits.
- Keep using both — the next gap gets another sheet.
When should you stop using Excel for this process?
Look at the hand-offs, not just the file size. Several people editing is a reason to check the setup. It isn't proof that you need a new app.
Answer yes or no to these questions:
- Do several people edit the sheet to keep work moving?
- Do copies arrive with names like
_v2_final? - Does the same supplier or product appear in several sheets?
- Do approvals happen in chat, away from the row?
- Do people struggle to find who changed a key value?
- Does only one person understand how the workbook works?
Don't turn the answers into a made-up risk score. Pick a “yes” and follow one real task. Ask what happens if that step goes wrong.
Suppose a price changes after Omar agrees to an order. Can Hana find the agreed price and the decision? If the answer needs a chat search and a phone call, start there.
Our take
Our take. Move a process when its rules need a home. Don't wait for a crash to make the case. Equally, don't replace a sound cost model just because it's a sheet.
How do you share Excel for multiple users to edit?
Try the sharing fix first if rival copies are the issue. Microsoft documents co-authoring: store the workbook in OneDrive or SharePoint Online. Share its link with edit access. People can use Excel for the web or a supported Excel app. The feature comes with a Microsoft 365 subscription.
That gives the team a shared workbook. It doesn't choose your approval rules. Decide who owns each list and where decisions belong.
Here are three sensible routes. The catches are things to check before you choose.
| Route | Fits when | The catch |
|---|---|---|
| Keep Excel and improve sharing | The job is analysis or a shared list | Agree on ownership and use one shared link |
| Use Access or another database | Related records matter more than a free-form grid | Plan the forms, access and support too |
| Build a process app | Work needs forms, roles and approval steps | Someone must define and maintain those rules |
Microsoft's Access and Excel guide makes a useful distinction. Excel suits analysis and calculations. Access suits structured data held in related tables. Your choice still needs to fit the people doing the work.
Keep the sheet or move the process?
- If copies are the main problem → try co-authoring first — check whether it resolves the confusion.
- If the work is analysis → keep the workbook — give its inputs a clear owner.
- If shared records need controlled actions → map an app — name the records, roles and approval steps first.
What does a spreadsheet-to-app move look like?
Start with the smallest useful process. For Sandline, that's agreeing which supplier price is ready to use. Keep Lumen Gloves' incoming workbook as the source file. Decide where the checked price belongs.
Sandline · example
One glove price, with a decision attached
In Beezr, Sandline can build Suppliers, Products and Supplier Prices modules. Each price record links to its supplier and product. Omar uses a form to enter the proposed price.
A permission profile can let procurement edit the price field. Sales can see it as read-only. An approval workflow sends the price for review. Its history records the decision, who made it and when.
Set the status as a lookup field with Track changes enabled. From then on, its history shows old and new values. Sara can check the shared record rather than keep a separate approved-price sheet.
Myth / Reality
Myth: moving the rows means the process is finished. The import is a start. You still need to agree who edits, who approves and what happens when a price is wrong.
Before building, remove duplicate suppliers and check product codes. Write down what each column means. Compare the new records with the old file before anyone relies on them. Plan when the old side sheet stops accepting edits.
For the structure behind those links, read what a data model is.
Key takeaways
- If you're technical: define record keys, relations and field types before moving data.
- If you're not: follow one price from receipt to approval. Ask where each decision lives.
- Keep useful spreadsheets. Give shared processes clear owners and rules.
Turn your workbook into an app in Beezr
Use Sheet to App for the structure, then set the rules.
- Prepare one
.xlsxworkbook — use worksheets for Suppliers, Products and Supplier Prices. - Review the fields — each worksheet becomes a module; each column header becomes a field.
- Add relations before it builds — link price records to suppliers and products.
- Set forms and permission profiles — choose which fields each role can edit, read or have hidden.
- Add approval and status history — use an approval workflow and enable Track changes on the status lookup.
Questions people ask before moving a workbook
Questions readers ask
Why is Excel so slow?
Don't assume the file has outgrown Excel. Microsoft's performance guide points to worksheet design and repeated calculations. Find the slow part first. Speed and process control are separate questions.
Why is Excel changing my numbers?
Excel can remove leading zeros or convert entries as it reads them. Microsoft explains these conversions. Treat codes as text before entry or import. Check the import preview before using the data.
Excel vs database: which should I choose?
Use the job as your test. Are you exploring costs, or keeping related business records? The comparison above helps you choose. A database also needs a usable way for people to enter data.
Can I turn a spreadsheet into an app?
Yes, you can start from an Excel file. Beezr's Sheet to App takes one .xlsx workbook. Each worksheet becomes a module and each column header becomes a field. Review the fields and add relations before it builds. Then design the forms, permissions and workflow. The workbook gives you a start, not the finished process.
Sandline Supplies is a fictional example company.
Sources
- Collaborate on Excel workbooks at the same time with co-authoring · Microsoft Support · accessed 2026-10-17
- Using Access or Excel to manage your data · Microsoft Support · accessed 2026-10-17
- Keeping leading zeros and large numbers · Microsoft Support · accessed 2026-10-17
- Excel performance: Improving calculation performance · Microsoft Learn · accessed 2026-10-17