In technology distribution companies, the ERP go-live announcement comes, the system is declared operational — and a few months later a familiar pattern emerges: inventory counts are accurate, the finance module has made the accountant’s life easier, and management reports pull up on screen without anyone having to call anyone. But the sales team is barely touching the system. Customer conversations still live in paper notebooks, quotations are still tracked in Excel, and order confirmations keep disappearing inside long e-mail chains. This picture is very common across Turkish technology distributors as of 2007. The problem is not technical. Connecting sales and customer relationships to ERP is not a matter of buying the right module — it requires redesigning working habits, and any implementation that fails to state this at the outset cuts the return on investment cleanly in half.A technology distributor’s business runs on a different rhythm than retail or manufacturing. The product catalogue is wide: printer consumables, server components, licensed software packages, networking hardware. The customer base is equally diverse: corporate procurement departments, systems integrators, small computer resellers, and the buying offices of retail chains. This variety makes the inventory side of ERP relatively straightforward — how much of which product is in stock, which supplier can deliver in what timeframe, and at what price each customer buys. The trouble is that the last question — what price for which customer, on what payment terms — still lives inside the sales representative’s head or on a crumpled phone note. When the system does not know a customer’s trading history, payment record, and negotiated price agreements, the accuracy of the inventory data no longer fully translates into better decisions at the point of sale.Consider a representative scenario that accurately reflects the sector: a mid-size IT distributor based in Ankara, with around 295 employees, starting an ERP project in late 2006. The company chose a solution built on Microsoft Dynamics NAV. Inventory, purchasing, and finance modules were operational within eight weeks. The real difficulty surfaced in week nine: the sales team — fourteen field representatives quoting and closing by phone — simply continued their existing habits. Quotations were prepared on paper or by e-mail, customer approvals were taken verbally, and orders were passed to the accounts department by phone or fax. The ERP picked up the transaction only at that final handoff point. Everything before that — the entire customer relationship — unfolded outside the system. Management was getting reports, inventory figures were clean, but nobody could see which customers were in the pipeline, who was likely to reorder and when, or which channel was quietly eroding margin.The root of this pattern is that ERP is most often positioned as a back-office and warehouse tool. When the sales team internalises the system as ‘something accounting uses’, that framing almost invariably becomes permanent if it is not deliberately challenged at the start of the project. So how does a distributor actually connect sales and customer relationships to ERP? There are a small number of critical integration points worth naming precisely. The first is customer-specific pricing: each customer’s agreed discount tier, payment terms, and credit limit must be held in the system so that a representative pulling up a quotation gets the correct figures without calling a colleague or consulting a spreadsheet. This single step makes it functionally necessary for the representative to log in, because there is no faster path to the right number. The second is the order confirmation flow: instead of a verbal or e-mail approval, an order confirmed inside the system drops directly as a warehouse pick request, which makes stock reservation accurate and eliminates the double-selling errors that are a persistent nuisance in distributor environments.The third integration point is customer trading history. When a representative can call up a customer’s last three orders, the prices agreed, and the outstanding balance without routing through the accounts team, the system starts to feel useful rather than bureaucratic. In Turkish distribution companies, deploying a separate CRM application alongside ERP is a tempting but often counterproductive move: data mismatches between two systems give the sales team a quiet justification for abandoning both. Deepening the customer card module within the ERP platform is almost always the more durable solution at this scale. That said, there is a limit that deserves a plain statement: ERP’s customer tracking is poorly suited to qualitative relationship notes — the kind of context that says ‘the last conversation was about a network performance problem, not price’. Trying to capture that in free-text fields makes search unwieldy and discourages entry. The practical boundary is therefore this: commercial and operational data belongs in the system; relationship context and meeting notes belong in the representative’s own records, at least at this stage of ERP maturity.What should be done in concrete terms? At the start of the project, the specific steps at which the sales team must interact with the system should be written out clearly and kept to between three and five touchpoints. More than that and the data-entry burden overwhelms representatives within the first fortnight, and the retreat to old habits begins almost immediately. The second step is designing those touchpoints so that the system is genuinely faster than the alternative: when a representative can retrieve a customer’s special price list in three clicks, using the system becomes the path of least resistance rather than an obstacle. When the speed advantage is obvious, resistance drops substantially. Third, management must request reporting directly from the system rather than via e-mail summaries. Telling a sales manager ‘pull it up yourself’ rather than ‘send me your weekly update’ is the most effective adoption incentive available at no additional cost. In the Ankara distributor scenario described above, this approach was combined with individual onboarding sessions in the two weeks before go-live — each session built around the representative’s own customer portfolio rather than a generic classroom format. Six weeks after go-live, %68 of all orders were being entered through the system; in the first version of the project, before the sales team approach was rethought, that figure had sat at %13.Getting ERP to cover sales and customer relationships in a technology distribution company is not a long journey, but it is a journey with a specific starting point: the sales team must experience the system as something that makes their own daily work easier, not as a reporting obligation imposed by management or finance. Establishing that experience is a more consequential consulting task than any module configuration. Before the project specification is written, the sales manager’s office deserves at least as much time as the finance director’s — and the first question asked there should not be ‘what reports do you need’ but rather ‘what would a representative see on screen first thing in the morning that would help them manage the day better’. The answer to that question is the real design brief for the sales layer of any ERP project in this sector.
This article was originally published in Turkish by Gökhan MERCANOĞLU on February 1, 2007. The English edition has been reviewed and edited by the author.