Picture a mid-sized textile company in Bursa. Accounting runs on one program, inventory is tracked in a separate ledger, and sales orders live on paper. Pulling these three sources together at month end can take days — and the numbers rarely match. ERP (enterprise resource planning) software steps in at exactly this point: it brings data from different departments into a single system so everyone sees the same information at the same time.
An ERP program is essentially several software modules connected under one roof. The accounting module, the stock module, the purchasing module and the sales module all work together. When a warehouse worker records an incoming shipment, accounting updates automatically. When the sales team creates an order, stock levels change instantly. Processes that used to run on paper or in separate programs can now be watched from a single screen. In Turkey, programs like SAP, Navision, LOGO and Netsis are among the names that come up most often when companies start looking at these systems.
The most concrete benefit is time. Month-end closings that used to stretch over days can be finished within a single working day. Instead of running to the warehouse to check stock, a manager can read the current figure off the screen. The purchasing department knows exactly how much raw material is left, so it stops over-ordering. In a textile business this brings down both storage costs and waste. A manager who arrives at the office in the morning can see yesterday’s sales figures, outstanding receivables and stock levels in one place — information that previously required separate conversations with the accountant, the warehouse supervisor and the sales manager.
The second clear benefit is fewer errors. When the same information is entered by several people into different programs or ledgers, the numbers inevitably drift apart. In an ERP system, data entered once flows through every connected module. When an invoice is issued, accounting, stock and the customer account all update at the same moment. Double entry disappears. For accountants this makes a real difference at year end and when preparing tax returns — the hours once spent ‘reconciling the numbers’ can go toward other work.
But there is a less comfortable side to these programs that deserves an honest look. The most common problem on the ground is data quality. Before the software goes live, years of incorrect, incomplete or inconsistent records have to be moved into the new system — and whatever is wrong in the old records comes along for the ride. Stock items that exist in the warehouse but not in any ledger, customer balances entered incorrectly, invoice dates that do not add up — if these go into the ERP unchanged, the system will not work properly. Implementation partners usually call this phase ‘data cleaning,’ and it is almost always the hardest part of the project. Companies that treat it as a minor detail find themselves switching back and forth between the old and new systems months after go-live.
The second major problem is staff resistance. The accountant has used the same program for years. The warehouse supervisor is comfortable with a handwritten ledger. The sales team does not want to learn a new screen. This resistance is rarely deliberate — people feel safe with what they know. A manager buys the software and arranges installation, but several months later employees have quietly drifted back to their old habits. The only way around this is training — before the system goes live and again after. A single training session is not enough; people need someone available when questions come up. This is where support from the local authorised reseller becomes critical. Companies left on their own after installation often abandon the system the first time something goes wrong.
The third problem is expectation management. Managers who expect everything to improve the moment the system is switched on are usually disappointed within a few months. An ERP program is a tool; it does not fix broken processes, it only runs existing processes faster and in a more organised way. If the purchasing process is already tangled, the software will automate that tangle rather than untangle it. This is why it is essential to map out clearly how each process will work before the project begins. As 2002 approaches, these three areas — data cleaning, staff training and realistic expectations — will decide whether an ERP project succeeds or stalls. Buying the software is only the starting point. The real work begins after that.
This article was originally written in Turkish by Gökhan MERCANOĞLU on July 23, 2001 and has been automatically translated into English and other languages using machine translation.