ERPNext Implementation in Kenya: What the Process Really Looks Like

Most Kenyan businesses looking at ERPNext ask the same first question: "how long will this take and what exactly happens?" The honest answer is that ERPNext implementation is less about software installation and more about untangling how your business actually runs. The software part is the easy bit. The hard bit is agreeing on what a "delivery" means when Sales, Stores and Finance each have a different definition.

At Upeosoft Limited we have delivered over 200 systems, and ERPNext consultancy is where the company started. This article walks through what a real ERPNext implementation in Kenya looks like, stage by stage, so you can judge any proposal you receive - ours or anyone else's.

What ERPNext implementation actually includes

A complete implementation is not a login and a training video. It covers:

• Discovery and process mapping - documenting how orders, stock, cash and approvals move today
• Chart of accounts and company setup - multi-company, multi-branch, multi-currency where needed
• Master data preparation - items, customers, suppliers, price lists, UOMs, warehouses, opening balances
• Module configuration - Selling, Buying, Stock, Accounts, Manufacturing, HR, Projects, CRM as applicable
• Customisation - custom fields, scripts, workflows, print formats and reports that match your paperwork
• Integrations - M-Pesa, bank feeds, KRA eTIMS, e-commerce, existing systems
• Role and permission design - who can see margins, who can approve credit notes, who can edit a posted entry
• Data migration - historic transactions or opening balances only, decided deliberately
• Training - role-based, hands-on, with real company data
• Deployment and hardening - server sizing, backups, SSL, monitoring, restore testing
• Go-live support - the first month, where most projects are actually won or lost

If a quotation is missing four of those lines, it is not an implementation quotation. It is a licence-and-hope quotation.

Stage one: discovery, and why it cannot be skipped

Discovery is where we sit with your team and follow a single transaction end to end. A customer calls. Who takes the order? Where is it written? Who checks stock? Who approves credit? Who picks, who delivers, who signs, who invoices, who chases payment?

In most Kenyan SMEs, that journey crosses a WhatsApp group, two Excel files, a delivery book and a QuickBooks file that only one person understands. The output of discovery is a written process map plus a decision log: what stays the same, what changes, and what ERPNext will simply not do the way you do it today.

The three questions that shape the whole project

1. Do you cost stock at moving average or FIFO? This decides how your gross margin reports behave forever.
2. Where does cash enter the business? Till numbers, paybills, bank, cash sales at branch. Each one needs a landing account and a reconciliation route.
3. What must be approved before it is posted? Every approval you add slows the system down and protects you. Choose deliberately, not defensively.

Stage two: configuration and the gap list

We configure a working instance with your real master data, then run your actual scenarios through it. Not demo data - your slowest-moving item, your most complicated customer, your messiest discount structure.

Everything that does not work out of the box goes on a gap list, and each gap gets one of four decisions:

Decision	When we choose it
Change the process	The current process exists because of a spreadsheet limitation, not a business rule
Configure	ERPNext supports it natively through settings, workflows or custom fields
Customise	A genuine business rule that needs code - a custom app, script or report
Defer	Real, but not worth delaying go-live for

The single biggest cause of failed ERP projects in Kenya is treating every gap as a customisation. You end up with an expensive, fragile system that cannot be upgraded. Our default is: configure first, customise only where the business genuinely differs.

Stage three: data migration

Data is where timelines quietly die. Your item master has three spellings of the same product. Your customer list has duplicates from 2019. Supplier names include phone numbers.

We usually recommend migrating opening balances plus one to two years of transactional history, not everything. Full history migration is possible but expensive, and most businesses never open it. What you actually need on day one is:

• Item master, cleaned and categorised, with correct UOMs and conversion factors
• Customer and supplier masters with credit limits and payment terms
• Opening stock by warehouse with valuation
• Open sales orders, purchase orders, receivables and payables
• Trial balance as at go-live date

Cleaning is a client-side job that we support with templates and validation. If nobody on your team owns data cleaning, the project slips. That is the most predictable risk in any implementation.

Stage four: training that actually sticks

Training by module fails. Training by role works. A store clerk does not need to understand deferred revenue. They need to know how to receive stock against a purchase order, what to do when quantities differ, and who to call when they cannot.

We run role-based sessions using your own data, then a parallel run where the team enters real transactions in ERPNext alongside the old system for an agreed period. Parallel running is uncomfortable and adds work. It also converts theory into muscle memory before the old system disappears.

How long does ERPNext implementation take in Kenya?

Timelines depend on scope and, more than anything, on your team's availability. Broad brackets we see in practice:

• Single company, core finance, stock, sales and purchase: typically a few weeks to a couple of months
• Multi-branch distribution with M-Pesa and eTIMS integration: two to four months
• Manufacturing with BOMs, work orders and shop-floor capture: three to six months
• Group structure, multi-company consolidation, heavy customisation: six months and up, usually phased

We generally recommend phased go-live over big bang for anything beyond a single site. Phasing means stock and buying go live first, then sales, then manufacturing or HR. Each phase produces value and confidence before the next begins.

What it costs to get ERPNext implementation wrong

The licence saving from open source is real. The cost of a bad implementation eats it in months. The failure patterns we are most often called in to repair:

• Stock that never reconciles because opening balances were loaded without valuation, so every margin report is fiction
• Customisation on the core app instead of a custom app, making upgrades impossible and locking you on an old version
• No permission design, so everyone is System Manager and nobody can explain who changed a posted invoice
• A server with no tested restore - backups that exist but have never been proven
• Consultants who disappear at go-live, exactly when the real questions start

The most expensive ERP is not the one with the highest quote. It is the one your team stops trusting, because then you are paying for the system and still running the spreadsheets.

How to start well

Before you sign anything, do these four things:

1. Name an internal project owner with authority to make process decisions. Not IT - operations or finance.
2. Write down your top ten pains in plain language. "I cannot see stock by branch in real time" beats "we need better reporting".
3. Decide your go-live date and work backwards. Start of a financial period is cleanest.
4. Ask your vendor what happens after go-live, in writing, with response times.

And resist the pressure to bolt AI, dashboards and predictive analytics onto a system whose stock does not balance. We wrote about that pattern in why you should not get pressured into buying AI before your business is ready. Clean operational data first. The clever layer becomes easy after that, and impossible before it.

Talk to us about your ERPNext implementation

Upeosoft Limited is an ERPNext consultancy based in Nairobi, extended with custom engineering, mobile apps and AI automation. We work across retail and distribution, manufacturing, automotive, real estate, waste management, security services, professional services and lending - which means we have usually met your edge case before.

If you are evaluating ERPNext, or recovering from an implementation that stalled, tell us where it hurts and we will tell you honestly whether ERPNext is the right answer.

• Email: consult@upeosoft.com
• Phone: 0116 888 777
• Web: upeosoft.com