CRM Consultant, Iraq

Wholesalers, sub-dealers and direct accounts

Most Iraqi distribution runs through layers. An importer sells to large wholesalers, who sell to sub-dealers and shops, while some customers such as hospitals, contractors or chains buy direct. A CRM that treats every customer as an equal record hides the structure that drives the business.

I design the account model around your actual channel:

• Account types for wholesaler, sub-dealer, retailer and direct key account, each with its own required fields and visit expectations.
• Parent and child links where a wholesaler serves known sub-dealers, so the company can see which end customers its volume really reaches.
• Exclusivity and territory fields where dealers hold agreed areas or product lines, so new inquiries are routed to the right dealer rather than undercutting them.
• Key account plans for direct customers, with contacts across purchasing, technical and finance roles.

Inquiries that arrive by phone or message from unknown buyers get a routing rule: direct customer, existing dealer's area or new dealer prospect. Without that rule, reps answer whoever calls and channel conflicts grow quietly.

The design is written down as a short CRM specification before any configuration starts. It also becomes the basis for choosing a platform, since some handle account hierarchies and dealer territories far better than others. For the commercial context, see wholesale ERP and distribution ERP.

Field reps, cash collections and weak signal

Iraqi field sales often combine taking orders, checking stock on shelves and collecting payment, frequently in cash. Reps spend their day on the road between towns where mobile coverage can be patchy. A CRM that needs a constant connection, or asks for a long form at every stop, will be abandoned within weeks.

I keep the field workflow short and resilient:

• A visit record with check-in, outcome, next step and an optional order, designed to take about a minute.
• Testing of each shortlisted mobile app on real devices in weak coverage, checking which actions work offline and how they sync later.
• A same-day rule for anything captured on paper or in a message when the app could not be used.
• Collection tasks generated from overdue balances in the ERP, so a visit covers payment as well as new business.

Cash itself is recorded in the ERP, not in the CRM. The rep's collection receipt, the handover to the cashier and the bank deposit are finance transactions with their own controls. The CRM shows the rep what is owed and whether the customer is on hold, and receives a confirmation once finance has recorded the payment.

Supervisors get a simple weekly view: visits against plan by territory, orders taken, collections outstanding and accounts not visited. That report, used consistently in sales meetings, does more for adoption than any training session. The ERP side of these links is covered on my Iraq integration consulting page.

Price lists, discounts and quotes in dinars and dollars

Iraqi importers often buy in dollars and sell in dinars, dollars or both, depending on the channel and the customer. Price lists can change quickly when supplier costs or exchange conditions move, and reps sometimes quote from an old list saved on their phone.

The CRM design settles a few points with finance:

• One source for prices. Price lists are owned by the ERP and published to the CRM, so a rep cannot quote from a list finance has withdrawn.
• Currency per channel. Which customers are quoted in dinars, which in dollars, and whether a quote may show both.
• Validity. A validity period on every quote, with expired quotes flagged for review before an order is accepted.
• Discount limits. Approval rules by role and margin, recorded in the CRM so exceptions are visible.

Deal values in the pipeline are stored in the quoted currency, and reports convert using the rate finance specifies, so management sees a consistent total. When a deal is won, the order passes to the ERP with its currency and agreed price, and invoice and payment status flow back to the account.

Exchange rate policy and any tax treatment are decisions for your finance team and advisor; the CRM applies them consistently. For contractors and suppliers who sell through tenders rather than price lists, my Zoho CRM notes for Iraq cover that pattern on one platform.

Arabic, Kurdish and English records, and who may see them

Customer records in Iraq often need three languages. A dealer in Erbil may have a Kurdish trading name, an Arabic registration and an English contact email, while a Basra wholesaler deals only in Arabic. Names transliterated differently by each rep quickly create duplicates.

I agree a naming standard with your team: which name is primary, whether a second field holds another script, and a language preference per contact for messages and documents. Duplicate checks rely on phone numbers, registration numbers or tax identifiers rather than spelling. The engagement runs in English; Arabic and Kurdish wording seen by customers comes from your bilingual staff, and I test that it displays and prints correctly in the chosen platform.

Access is the other half. Dealer lists, price agreements and customer contacts are commercially sensitive, and a departing rep with a full export can take a territory with them. I design roles so reps see their own territory, managers see their teams and exports are limited to named people, with an audit trail of changes to key records.

Data protection expectations in Iraq may come from local rules and, very often, from international principals or clients through contracts. Your legal counsel decides what applies. I then build their guidance into origin and consent fields and opt-out handling for marketing messages, so a contact who asks not to be messaged is respected across every channel the team uses.

Choosing a CRM when local support is thin

In Iraq the platform decision depends heavily on who will support it. Coverage by experienced implementers varies by platform and region, and a CRM that nobody nearby can administer becomes a liability once the project team has gone.

I score options on the usual factors, process fit, integration with your ERP, mobile behavior and licensing model, and add three that matter particularly here:

• Support reach. Who can help in Baghdad, Basra or Erbil, in which languages, and whether remote support from abroad is realistic for your team.
• Admin capacity. Whether someone in your company can manage users, fields and reports after go-live, and how much training they need.
• Hosting and payment. Where data would be stored, and how subscriptions are billed and paid from Iraq.

Often the simplest answer is the CRM inside the ERP you already run or are about to choose, whether Odoo, ERPNext, Zoho or Dynamics 365, because it removes one integration and one support relationship. A standalone CRM makes sense when sales needs depth the ERP module cannot provide.

I advise remotely, alongside whoever configures the system, and travel only when it has been agreed beforehand. For the wider systems decision, see the Iraq ERP consultant page, the ERP selection consultant page, my CRM consulting service and the Iraq hub.