In short
Excel is a brilliant tool for one person and one question. It struggles when several people, documents and companies depend on the same numbers. The signs you need an ERP (one system for sales, purchasing, stock and accounting) are practical: the same order typed three times, stock promised twice, stores and accounts arguing about deliveries, and a month-end spent reconciling. If three or more of the nine signs below sound familiar, it's time to look properly.
What are the signs you need an ERP?
These nine signs come up again and again in B2B trading, distribution and project-supply businesses:
- The same order is typed into three different files.
- Sales promises stock the warehouse doesn’t have.
- Stores and accounts disagree about what arrived.
- Month-end means a week of reconciling stock to the books.
- Nobody can say who owes what, or when they’ll pay.
- Approvals live in chat threads.
- Everyone sees everything, or nobody sees anything.
- A second company, warehouse or currency doubled the work.
- You’re retyping customer POs into quotations.
Each one is explained below, with what changes when you move to an ERP.
1. The same order is typed into three different files
What it looks like: the quotation is in Word, the order is in an Excel tab, the delivery note is handwritten and the invoice is in your accounting package. Each is typed separately, by a different person.
Why it hurts: every retype is a chance to change a price, a quantity or a tax rate. When the customer disputes an invoice, nobody can say which version was right.
What changes: in an ERP, each document is created from the one before it. An accepted quotation becomes a sales order, the order becomes a delivery note, and the delivery becomes the invoice, with lines, discounts and tax carried across.
2. Sales promises stock the warehouse doesn’t have
What it looks like: two salespeople sell the same 50 units to two customers on the same afternoon. The stock sheet was last updated on Sunday.
Why it hurts: you lose credibility with the customer you let down, and you often pay for an urgent purchase to cover the gap.
What changes: an ERP shows stock on hand, reserved and available per warehouse. Confirming an order reserves its stock, so the next salesperson sees only what’s genuinely free. That’s stock reservation, and spreadsheets can’t do it reliably once more than one person is selling.
3. Stores and accounts disagree about what arrived
What it looks like: the supplier’s delivery note says 100, the storekeeper counted 96, the purchase order said 120 and the supplier invoices for 100. Finance finds out a month later.
Why it hurts: you pay for goods you never received, or stock records drift away from reality.
What changes: an ERP records a goods received note (GRN) at the gate, with short, over and rejected quantities and a reason for each. The supplier’s invoice is then checked against what was actually received.
4. Month-end means a week of reconciling stock to the books
What it looks like: the stock report says one value, the inventory account in the ledger says another, and someone spends days finding out why.
Why it hurts: the books are late, nobody fully trusts the margin figures and decisions wait for numbers.
What changes: in a connected ERP, every receipt, delivery, write-off and count updates the stock and posts its journal in the same step. Stock and the ledger stay in step because they’re posted together, not separately. We explain the causes in more depth in why your stock report and your accounts never agree.
5. Nobody can say who owes what, or when they’ll pay
What it looks like: the receivables list is a spreadsheet updated “when someone has time”. Salespeople don’t know which of their customers are overdue.
Why it hurts: cash collection slips, credit terms stretch quietly and you discover a bad debt too late.
What changes: an ERP builds receivables aging (current, 1–30, 31–60, 61–90 and over 90 days) from the invoices themselves, and due dates follow each customer’s credit terms. Everyone sees the same overdue list.
6. Approvals live in chat threads
What it looks like: a discount is approved with a thumbs-up in a group chat. Three months later, nobody can find who agreed it, or at what price.
Why it hurts: discounts and purchases slip through without proper sign-off, and auditors ask questions you can’t answer.
What changes: an ERP routes quotations and purchase requests to the right approver, often by amount, and records who approved what and when. The record stays with the document. That’s an approval workflow, and it replaces the thumbs-up.
7. Everyone sees everything, or nobody sees anything
What it looks like: the shared drive has one customer file that every salesperson can open, copy and take with them when they leave. Or the opposite: only the owner has the full picture.
Why it hurts: your customer list walks out of the door, or every decision waits for one person.
What changes: an ERP gives each role exactly what it needs. Salespeople see their own customers, managers see their team’s and storekeepers see quantities without prices.
8. A second company, warehouse or currency doubled the work
What it looks like: you opened a subsidiary in another country, a second warehouse or a supplier account in euros, and every spreadsheet now has a copy.
Why it hurts: group figures take a week to assemble, and exchange differences are guessed rather than calculated.
What changes: an ERP keeps each legal entity with its own currency, tax registration and books in one system, with stock held per warehouse. Group figures come from one consolidation rather than a week of copy and paste.
9. You’re retyping customer POs into quotations
What it looks like: a customer sends a 120-line purchase order or request for quotation as a PDF, and a salesperson spends the afternoon typing it into a quotation.
Why it hurts: quotations go out late, and typing errors become pricing errors.
What changes: some ERPs can now read the customer’s document and draft the quotation lines for you to check. It’s one of the few places where AI document extraction already saves real time in a trading business.
When is Excel still enough?
Excel is still enough when one or two people handle everything, you hold little stock and a good accounting package covers your invoicing and tax. If you have one location, a handful of suppliers and a few dozen invoices a month, the cost of an ERP may outweigh the benefit for now.
The tipping point usually arrives when work is shared. Once sales, the warehouse and finance all depend on the same numbers, spreadsheets stop being a tool and start being a risk.
What should you do when you spot the signs?
Don’t start with software demos. Start with your own flows.
- Count your signs. Note which of the nine apply, and what each costs you in time, errors or lost sales.
- Map two flows. Write down how a customer order becomes cash, and how a purchase request becomes a supplier invoice, with the real document names.
- List your must-haves. Include local needs such as tax codes, documents in your customers’ language and several companies, if you run them.
- Shortlist and test with your data. Ask vendors to run your flows, not their standard demo.
Our ERP buyer’s guide walks through each step, with demo scripts and a scoring table. If you’ve already decided to move, read our side-by-side comparison of Excel and an ERP, and see how data import and migration brings your sheets across.
How does 1flux handle these signs?
1flux is the AI-native ERP for B2B trade: one platform for selling, buying, stock and the books, from PO to paid. Here’s how it answers each sign.
Related comparison
1flux vs Excel and spreadsheets
Bring your customers, items and opening balances across, validated row by row, and run every flow in one system.