ERPNext CRM in Kenya

ERPNext's own CRM or a dedicated one for a Kenyan business?

The sales side of ERPNext covers lead capture, opportunities, quotations, the customer and contact master, a territory tree, sales persons and commissioned partners. For a Kenyan business selling products from stock, where an inquiry becomes a quote and an order within days, that is usually enough. The gain from one database is concrete: a rep quoting an agro-dealer sees what is in the Eldoret depot, whether the dealer is over their credit limit and whether last week's M-Pesa payment has been matched.

I advise looking at a dedicated CRM when:

• Sales are long and consultative, such as solar installations, equipment for hospitals or software services, where forecasting and follow-up sequences matter more than stock.
• Marketing runs campaigns with scoring, landing pages and attribution to paid ads.
• A large field team needs offline-capable mobile apps and route planning beyond what ERPNext's web interface offers.

Frappe CRM, a separate app from the makers of ERPNext with a newer interface, is another option worth evaluating with Frappe or your implementer for your version. Should an outside CRM win, the remaining job is connecting the two: customers, prices and quotes flow in one direction, with one system owning each record. Read the general ERPNext CRM page for product scope; the trade-offs are covered in my CRM consulting service.

Territories, distributors and reps on patchy networks

A Kenyan route-to-market can mix direct sales to supermarkets, appointed distributors in each region, sub-distributors serving dukas and agro-dealers, and reps who visit both. ERPNext gives you the building blocks:

• Territories as a tree, for example region, then county, then route, so reports roll up from a single route to the national total.
• Sales persons linked to customers and territories, carrying item-group targets where management sets them.
• Sales partners for agents or distributors paid a commission, or ordinary customers with their own price list for distributors who buy and resell.
• Customer groups separating supermarkets, wholesalers, retailers, agro-dealers and institutions, each with its own pricing and credit rules.

Connectivity is the practical constraint. ERPNext is a web application, and while it works on phones, reps on rural routes may lose signal for hours. I test the forms reps will use on a typical route, keep them short, and agree a fallback: notes captured offline and entered at the next stop, or a lightweight mobile tool that syncs to ERPNext when a connection returns. Confirm with Frappe or the implementer what offline support your version or any mobile app actually provides.

Related distribution patterns appear on distribution ERP.

From lead to quotation to an invoice that clears eTIMS

A quote that cannot become a valid invoice wastes everyone's time. In Kenya, invoices to registered buyers typically carry the buyer's KRA PIN and pass through your eTIMS route, so customer data needs to be right before the first quotation goes out, not when finance tries to invoice.

The flow I design and test:

• Lead conversion requires the business name as registered, the KRA PIN where the buyer has one, the contact person and the payment terms requested.
• Credit approval for new accounts by finance before a sales order can be submitted, with a credit limit set on the customer.
• Price lists per customer group, with pricing rules for volume or promotions and approval for discounts beyond a rep's limit.
• Tax templates on quotations, so VAT treatment your advisor defines carries through to the sales invoice.
• One chain of documents, quote then order then delivery note then invoice, with no retyping of prices or terms, so the document KRA receives matches what the customer accepted.

Institutional tenders follow the same chain but usually need document checklists attached to the opportunity. Whether your eTIMS app validates customer data before submission is worth confirming with its maintainer. For integration patterns, see sales and ERP integration.

M-Pesa status, SMS and WhatsApp in the sales conversation

Reps who also collect payments need to see what a customer owes and what has already been received. After the finance team allocates M-Pesa receipts against invoices, the customer dashboard in ERPNext shows the outstanding balance and recent payments. I add a simple rep report: overdue amounts by customer on today's route, so a visit can cover both a new order and a collection. The accounting design behind M-Pesa matching sits on my ERPNext Kenya page.

Messaging is the other half. ERPNext can send SMS through a configurable gateway setting, and community apps exist for WhatsApp through approved providers. Uses to evaluate:

• Order confirmations and delivery notifications by SMS, which reach basic phones.
• Payment reminders with the Paybill number and account reference included.
• WhatsApp conversations captured against the customer, so history survives when a rep leaves.
• Promotional messages only to contacts with a recorded basis for marketing.

For each app or gateway, check who maintains it, which ERPNext versions it supports and the provider's charges. Message wording in Swahili or Sheng belongs to fluent colleagues on your side to draft and approve, as the engagement runs in English. Integration method follows my system integration approach.

Marketing consent, data protection and points to verify

Personal details of buyers, distributor staff and prospects stored in the CRM fall under Kenya's Data Protection Act, and it affects direct marketing by SMS, WhatsApp and email. Whether your business must register with the Office of the Data Protection Commissioner, what basis you rely on for marketing and how long records are kept are questions for your legal or data protection advisor. I configure ERPNext to follow their answers.

Typical settings:

• Fields on leads and contacts for the marketing basis, the channel it covers and the date it was recorded.
• Marketing lists built only from contacts with a valid basis, and an opt-out flag that removes them from every list.
• Role and user permissions restricting reps to their own territories.
• A retention routine for leads that never converted.
• Care with phone numbers collected at events or from distributors, which may not carry consent for your marketing.

Ahead of go-live, ask Frappe or the implementer to state in writing which sales features ship with your version, which messaging apps are maintained for it and where the system is hosted. I am independent of Frappe and every implementer, with no commissions involved. Alternatives are discussed on Odoo CRM Kenya and Zoho CRM Kenya, and the Kenya hub explains how my remote work runs.