Choosing and Implementing an ERP System for Small Companies

The acronym is part of the problem. ERP stands for Enterprise Resource Planning — a phrase coined in the 1980s for large factories planning raw-material purchases, and one that has little left to do with what a warehouse owner in Amman is actually buying. The name stayed, the meaning drifted, and the result is that everyone in the room uses the word meaning something different.

The name that did more harm than good

When a vendor tells you "this is an ERP system," they have not yet told you anything. They might mean accounting software with stock bolted on. They might mean a platform that needs a team to run it. The word commits them to nothing and gives you no basis at all for comparing two quotes. That is why you will find me avoiding the term wherever I can in this book, and asking instead: which processes will this system run, who will enter the data, and which decision gets easier afterwards?

The definition I use

An ERP system is one database into which your business transactions are entered once, and then seen by every department that needs them, at the same moment, without being retyped.

That is the whole of it. Notice what is absent: no module count, no cloud, no AI, no reporting. Those are details that come later. The substance is two things: a single source of truth, and entry once.

Take a sales invoice. In a company without a unified system the invoice is written in a book or a file, then stock is decremented by hand in a second file, then the accounting entry is recorded in a third program, then the customer's balance is updated in a fourth sheet. Four writes for one event. Each is a chance to be wrong, and each error surfaces weeks later. A unified system makes it one write that shows up in all four.

That is the real gain, and it is an operational gain rather than a technical one: reducing the number of times a single fact gets written down.

What an ERP system is not

Three things are sold under the name and are not it:

• Accounting software. It records what happened financially. It does not run a purchase request, a stock movement, or an approval chain. Excellent at what it was built for, and plenty of companies need nothing more.
• Separate programs joined by a spreadsheet. If moving data between them is manual, you have four systems rather than one, and the retyping problem is exactly where it was.
• A reporting dashboard. A report is an output, not a system. A beautiful dashboard on top of data keyed by hand in four places is a beautiful dashboard on top of four possible errors.

Why "modules" is the wrong measure

Vendors will show you module lists: sales, purchasing, inventory, accounting, HR, manufacturing, maintenance, assets. The longer list looks like the better deal. It is not.

An unused module is not neutral — it has a cost. It needs configuring, it puts fields on screens, it confuses new staff, and it sits inside your licence and maintenance invoice. I have seen companies pay every year for manufacturing modules that were never once opened.

The right measure is not module count but: how many of your daily processes will actually move into this system in the first six months? If the answer is three, then the system that does those three well beats the one claiming thirty.

The question that comes before everything

Before any quote and before any demo, sit down and write the answer to one question:

Which decision can I not make today because the information is missing or untrustworthy?

Real answers look like this: "I don't know how much stock has been sitting for more than six months." "I don't know the profit per item after shipping cost." "I don't know exactly what customers owe me today." "I find out an item is out of stock when a customer asks for it."

If you cannot write three answers of that kind, you do not need a system yet — you need to work out what you want to know. That is not something you can buy.

Action steps

Before the next chapter:

1. Write, on one page, the three decisions you cannot make today because of information. In specific wording, not phrases like "organising the work."
2. Follow a single sales invoice from the moment of order to the moment cash is collected, and write down every place a piece of its information gets copied to. Count the times.
3. Ask your staff: which information do you enter more than once? The answer usually comes in seconds, and it will not be what you expected.