Picture a building materials company with two branches in different cities. At the first branch, stock counts happen once a month on a fixed schedule. At the second, the accountant runs them whenever it feels right. At the first branch, a warehouse approval is required before any invoice is issued. At the second, the sales rep walks straight to the register. When the general manager sits down at year-end to compare the two branches, the numbers do not add up. Who is doing it right and who is doing it wrong is impossible to tell. This situation is familiar to many small and medium-sized businesses.
This is exactly the problem that ERP (enterprise resource planning) software promises to solve. An ERP system brings all company operations — sales, purchasing, warehousing, and accounting — into a single software platform. But the real value is not the software itself. It comes from the fact that installing the software forces a company to write down how it actually works. Who does which task, in what order, with what documents — all of this gets defined inside the program. Once those definitions are in place, the system requires every branch to follow the same steps.
In practice, this means that if warehouse approval is set as a requirement before invoicing, the system will not open the invoice screen until that approval arrives. If stock counts must happen on a set schedule, the program sends reminders and records the results. When a staff member leaves and a new one arrives, the process does not change, because the rules are built into the software. The new employee opens the system and sees exactly what needs to be done. The job no longer depends on what the previous employee kept in their head.
Training costs drop noticeably as a result. In companies without standard processes, each branch needs separate training because each branch works differently. When a new employee joins, the old one must stay nearby for weeks to pass on unwritten knowledge. With an ERP and a standard process in place, training comes from one central source and takes far less time, because the program guides the user through each step. For branches in cities far from headquarters, this difference is especially significant — sending a trainer from Istanbul to another city costs both time and money.
Error costs fall in a similar way. When the same task is done differently across branches, mistakes are unavoidable. One branch entering an invoice date incorrectly can cause months of confusion in the accounts. A standard process means the program checks required fields and blocks entries that do not make logical sense. When the accountant closes the month and pulls data from all branches, everything arrives in the same format. There is no need to correct each branch separately before the numbers can be used.
That said, every branch has its own real-world conditions. One branch extends credit terms to large customers while another works cash-only. One branch sells a different product range and uses different units of measure. Ignoring these differences when building a standard process is a mistake. In a well-designed ERP setup, the general rule is defined centrally, but specific exceptions are also built into the system. Credit approval authority, for example, is assigned only to the branch manager — a regular employee cannot grant it, but when the manager approves, the system accepts it. Without this balance, field staff find ways around the software. ‘The system does not handle this, let us write it down by hand’ becomes the workaround, and that quietly destroys everything the standardization was meant to achieve.
For a small business owner considering an ERP system, the right question to ask first is this: do I actually know how the same task is being handled in each of my branches right now? If the answer is ‘I am not sure’ or ‘everyone does it their own way,’ the work of answering that question must come before choosing any software. An ERP program automates the way a company already works — it does not fix a broken process on its own. Deciding which process is correct, and separating genuinely necessary exceptions from habits that just grew over time — these decisions come before the software selection. Companies that work through these questions get real results from their ERP investment. Those that skip this step end up with expensive software and branches that still work differently from one another.
This article was originally written in Turkish by Gökhan MERCANOĞLU on March 17, 2003 and has been automatically translated into English and other languages using machine translation.