What Does a Company Lose When ERP Adoption Is Low?

Picture a mid-size manufacturing company. The accounting manager pulls the monthly stock report not from the ERP system but from a spreadsheet the warehouse clerk maintains on his own computer. The purchasing officer writes down orders in a notebook before eventually entering them into the system — sometimes. The production supervisor walks into the morning meeting with a table he put together himself. The software is installed, the license fee is paid, the server is running. But the actual work still follows the old routine. This picture is familiar to many small and medium-sized businesses across Turkey.

ERP — enterprise resource planning — software is designed to connect every department under one system. Inventory, purchasing, accounting, sales: all of it feeds into the same database. But that integration only delivers value when employees actually use the system. When adoption is low — meaning a significant share of daily transactions are recorded somewhere other than the ERP — the company is effectively running two systems at once. One official, one unofficial.

The unofficial system almost always lives in Excel. Excel is not a bad tool; it handles calculations and lists well enough. But when a company records stock movements in both the ERP and a spreadsheet, those two records need to match. When they do not, which one is correct? The answer is usually unclear. The accountant trusts the number in the program; the warehouse clerk defends his own table. Resolving the discrepancy can take two people half a day. That half day is money the company will not get back.

Measuring adoption does not require a complicated method. Ask a few direct questions: How many stock movements were entered into the system this week, and how many were not? How many sales orders were opened in the system, and how many were handled by fax or phone and only touched the program at the invoicing stage? How many bank payments were reflected in the accounting module on the same day they were made? One week of tracking these numbers is enough. The result usually surprises managers: in many companies, a third to half of all transactions bypass the system entirely.

Every transaction that stays outside the system creates two kinds of cost. The first is time. Entering the same information in two places, reconciling two tables, chasing down discrepancies — each of these consumes employee hours. The second is error. When an order is entered late, the stock figure looks wrong. A wrong stock figure leads to a wrong purchasing decision. Excess material sits in the warehouse and ties up cash. Or a shortage stops production and a customer complains about a delay. This chain reaction can easily exceed the monthly license fee many times over.

Before trying to raise adoption, a manager needs to understand why it is low. There are three common reasons. First, employees do not know the system well enough; they open a screen, cannot figure out what to do, and fall back on familiar habits. Second, the setup for that particular department is incomplete — for example, the warehouse module is active but no barcode reader is connected, so manual entry feels too slow. Third, management does not monitor system use; because no one asks, employees do not feel obligated to enter data. Each reason calls for a different fix.

Here is a practical first step: this week, ask each department head one question — ‘Which transactions did your team not enter into the system, and why?’ Write down the answers. If the answer is ‘we do not know how,’ contact your software vendor or local reseller and ask for additional training; most authorized resellers in Turkey provide this kind of support. If the answer is ‘it takes too long,’ review the module setup with your implementation partner. If the answer is ‘there is no need, we already have it in Excel,’ it is time to close that spreadsheet. If you are paying for a system, the system should do the work.

This article was originally written in Turkish by Gökhan MERCANOĞLU on April 5, 2004 and has been automatically translated into English and other languages using machine translation.


When enterprise software selection succeeds, it does not merely put more information on a screen; it gives management clearer decisions. Silos decrease, responsibility becomes visible, and measurable progress starts. Therefore, the issue is not tool selection but rebuilding operating discipline through technology.


Gökhan Mercanoğlu
ERP ve Kurumsal Yazılım