A mid-sized metal pipe distributor based in Konya, operating with 284 employees and serving both the domestic market and regional export channels, made its ERP investment decision in 2013. The owner’s instruction was clear: ‘I want better visibility into our sales.’ The consulting team took that sentence at face value and opened the system through the sales management module. Fourteen months later the software was still running — but inventory figures were unreliable, purchase prices were being corrected by hand, and the accounting team used the system only to issue invoices, not to generate reports. Return on investment could not be calculated because most of the process still lived in spreadsheets. This was not a failure of implementation. It was a failure of starting in the wrong place.In metal pipe trading, the real business problem is not in the sales process — it is buried in purchasing and inventory. Products such as raw steel sections, stainless profiles and black pipe fluctuate daily in price; the ferrous metals market moves directly with currency rates and commodity indices. When a distributor of this scale processes 40 to 60 sales line items per day, the controlling questions are: what did I pay for this product, how much do I have in stock, and what is today’s actual cost? A sales team that cannot answer these three questions accurately will quote at the wrong price regardless of how well it uses the sales module. That is the thesis of this article: in commodity-based sectors like metal pipe trading, an ‘open sales first’ approach corrupts the data from the very first day and turns the ERP into an unreliable tool within months. The correct starting point is always purchasing and inventory.So why do teams start with the sales module? Because that is what the owner sees and asks for. The sales process is tangible. Customer tracking feels intuitive. In every management meeting, ‘what did we sell and to whom’ is the first question on the table. Purchasing, by contrast, is quieter, more technical and less visible; supplier ledgers, payment terms and cost updates rarely dominate the owner’s daily agenda. But this invisibility does not make the purchasing module less critical — on the contrary, a single error in purchasing data propagates through the entire system and reaches the sales report at the far end. In the Konya case, supplier discount rates had never been entered into the system. As a result, cost bases were calculated short, and the gross margin figures the sales team was looking at did not reflect reality. The salespeople were working hard — but they were reading the wrong numbers.The inventory module sits at the centre of this picture. In metal pipe distribution, product variety is high: combinations of diameter, wall thickness, material grade and cut length can push a single warehouse past 600 to 800 SKUs with ease. Each of those products carries a different unit cost, a different supplier profile and a different lead time. Before any ERP goes live, every one of these definitions must be established without gaps; otherwise the system processes the right product under the wrong code, and by the time a stock count is done, the accounting ledger and the physical warehouse will not reconcile. In practice, this preparation phase — building the product master data — deserves at minimum one quarter of the entire project timeline. In Konya, three weeks were planned for it. It took eleven weeks. The reason: product names used on the warehouse floor differed from the names in the accounting ledger, and only a systematic inventory audit brought the discrepancy to light.Accounting integration is the third critical link, and this is where Turkey’s specific tax compliance requirements enter the picture. The mandatory e-Invoice and e-Ledger obligations — enforced progressively since 2012 for qualifying firms — require the ERP to operate in direct connection with the Revenue Administration’s infrastructure. By 2015, most commercial ERP packages include this integration as a standard feature, but configuration still requires a consultant. When an export dimension is added to metal pipe trading, foreign-currency transactions, exchange-rate accounting and customs declaration workflows join the equation. To manage this complexity reliably, the accounting module must be installed and tested against live transactions before the sales module goes live — otherwise a sales invoice is printed and delivered but no accurate accounting entry is created behind it. The difference between those two outcomes appears small in month one; it surfaces as a major reconciliation problem at year-end close.The most persistent obstacle in front of implementation is not technical — it is organisational. The purchasing officer resists entering supplier prices into the system because that information has always been kept close to the owner, and sharing it feels like a loss of position. The warehouse supervisor reverts to old habits with product codes because nobody has explained why the new system matters for his specific job. The accountant has no choice but to use the platform because e-Invoice obligations force it — but since no data flow from other modules has been properly established, corrections are being entered by hand every day. These three resistance points look independent. They all feed from the same root: nobody has clearly, concretely and repeatedly communicated why the ERP is being built and for whose benefit. A consultant’s job is to answer that question at every level before touching a single configuration screen.A SME owner in metal pipe trading preparing to invest in ERP should begin Monday morning with three questions. First: can I give my sales team accurate cost data without entering supplier price lists into the system? If the answer is no, the purchasing module is the first priority. Second: do my inventory definitions use the same language across accounting, the warehouse and the sales desk? If the answer is ‘we use different names in different departments,’ plan at least six weeks of master data cleanup before the project launches. Third: will my e-Invoice integration run through the ERP, or through a separate application? The answer to that question alone largely determines which ERP package is the right fit. The Konya distributor asked all three questions not at the start of the project but fourteen months into it. Restarting from the correct position was effectively the same as beginning from scratch. The cost of re-implementation reached 57 percent of the original project budget — a predictable outcome, and a preventable mistake.
This article was originally published in Turkish by Gökhan MERCANOĞLU on February 7, 2015. The English edition has been reviewed and edited by the author.