A spreadsheet is honest: whoever opens it can edit it, formulas travel with people, versions fork in WeChat. A system looks clumsier: price changes need permission, negative stock is blocked, duplicate customers must merge. The clumsy side is the rules a company can keep. Once volume grows, sheets break first on concurrency and definitions. See Excel inventory breaks once volume grows. Two people open the same file; the last save silently overwrites the earlier discount. In a system that should be a conflict, not a month-end fight.
// EXCEL
# discount lives in a sales note
IF(mood_good, 0.85, 0.95)
VLOOKUP(customer, private_sheet, 2) 'file on D:
stock = last_week_count - group_screenshots
Save as "final(3)-edit.xlsx"
// SYSTEM
# discount lives in policy and approval
price.require(role, audit)
customer.id = master // one master record
stock -= qty on outbound
history.append(who, when, why)
Sheets keep results. A system keeps constraints
A sheet can keep last year’s ship quantities. It cannot keep “who may discount to 85%.” When that person leaves, the next hire can only guess. Why operations hold together when people leave is in Why operations do not fall apart when people leave. Treat the system as an electronic ledger and you only moved the sheet into a browser — rules stay verbal. See ledger vs. operations system.
People say “our sheet is already disciplined.” It is — until three people edit the same cell. Promotions, free goods, and one order across warehouses add columns and fork definitions. If sales and finance each keep a customer file, reconcile is translation. See Sales and finance looking at the same customers and contracts. Stock matching the books means the decrement happens on outbound — not a month-end manual edit. See How a system makes inventory match the books.
Moving from sheets to a system means moving a rule list
Do not turn every column into a field. First list the rules you must not break: block over-credit or not, allow negative stock or not, who approves a price change. Write those as states and permissions, then the sheet can retire. Migration steps are in How to move old data and spreadsheets into a new system. The path gap with and without a system is in How the work path differs with a business system and without one. In interviews DaXi Technology writes verbal rules as configurable items — we do not draw a more complex sheet first. To pull rules out of the spreadsheet, go to the Business systems service page and bring the file you actually use. Color and comments are not permission. Merged cells are not master data. Carry those habits into a system and you get another hard-to-maintain web sheet.
Export is for analysis. It is not an order entry again
Exporting Excel for analysis after launch is normal. What is not: the analysis file becoming the order entry again. Export is read-only. Work goes back to the system. When report requests swell, ask first whether anyone edits that column at order time. If yes, it is work, not a report. If no, it can stay in a sheet or a dashboard.
The longer the formula, the more it looks like a rule — and the more dangerous it is. A sheet that auto-calculates margin usually hides tax-in, freight, and free goods in a note column. A new person cannot use it. In a system those should be fields and switches, not a hidden column on page three. A “read-only” file on a shared drive does not stop Save As. Real read-only is permission: the warehouse cannot change list price; sales cannot change stock. That is the constraint you can keep. Print the sheet you use, circle the cells that cost money if they break. Circled cells go into the system first. Uncircled ones can stay in Excel a few more months. After circling you will find the valuable rules are often fewer than twenty. The rest is habitual extra columns.