Contact Info
What does a Kenyan distributor need from Odoo Inventory?
A Kenyan distributor needs Odoo Inventory set up with warehouses for the Nairobi center, coastal and upcountry depots, routes that show stock moving by road and across borders to East African customers, lots and expiry for food, agro-inputs and health products, and product data complete enough for the eTIMS route on invoices. The design and testing happen remotely, with no link to any implementer, and each Enterprise-only feature is flagged.
Last reviewed by Vikas Saroj
A Kenyan distributor's stock is spread along a corridor: containers clearing at Mombasa, a main warehouse around Nairobi, depots in Nakuru, Kisumu or Eldoret, trucks on the road and sometimes customers or sister companies in Uganda, Rwanda or Tanzania.
Odoo Inventory can represent each of those places and the steps between them. The design work is choosing which steps to record, which products need lots and expiry, and how product data supports the eTIMS invoice that follows each sale.
I work remotely as an independent consultant with operations, depot and finance leads.
Each piece of work follows goods from the port or supplier to the customer, and the data each step leaves behind.
A warehouse per depot, with resupply from the main warehouse driven by reordering rules, and transit stages so goods on a truck to Kisumu or Eldoret are visible and owned.
Transfers to sister companies or customers in neighboring countries modeled with clear ownership points, so stock leaving Kenya is not counted twice or lost at the border.
Expiry-dated lots and earliest-expiry picking for seeds, agrochemicals, veterinary products, food and pharmacy lines, with near-expiry reports per depot.
Product master fields that your eTIMS route may require, such as classification and unit codes, defined and filled before go-live so invoices are not rejected later.
Third-party and bonded warehouses modeled as locations with clear status, and a data exchange agreed with each provider so their records and yours match.
Barcode use planned around the connectivity at each depot, with a fallback for receiving and dispatch when the network drops, and a rule for catching up afterward.
Follow goods along the corridor
Locations, routes and product data
Main warehouse, then depots
Kenyan distribution relies on road transport from a central warehouse to depots and customers, and the time goods spend on the road is where stock gets lost in most spreadsheets. In Odoo, I set up each depot as a warehouse that resupplies from the main warehouse, with dispatch, transit and depot receipt as distinct steps. Stock that left Nairobi but has not reached Kisumu sits in a transit location with a known owner.
Decisions to settle with your logistics lead:
Van sales from depots can be modeled with each van as a location, but on-the-road invoicing and cash or M-Pesa collection usually need a specialist app integrated with Odoo. The general feature overview is on the Odoo Inventory page.
Many Kenyan distributors and manufacturers serve customers across the East African Community, either directly or through sister companies. That raises inventory questions beyond customs paperwork, which stays with your clearing agent.
Patterns I design in Odoo:
Intercompany accounting and consolidation sit on the finance side; my Odoo Accounting Kenya page covers them. The platform-level discussion of East African groups is on the Odoo consultant Kenya page.
Distributors of seed, agrochemicals, animal health products, packaged food and pharmacy lines in Kenya handle products where expiry and batch matter for customers, regulators and recalls. In Odoo, each lot can carry an expiry date, and picking by earliest expiry sends staff to the lot that runs out first.
Design points I agree with your operations and quality leads:
Regulatory registrations and product approvals for agro-inputs and medicines belong to your compliance staff and the relevant authorities. Odoo can store reference documents against the product and block sales of items flagged as not approved, if you want that control. Wider patterns are on inventory and warehousing.
Odoo Inventory moves stock; invoices and tax are handled in Odoo Accounting with the Kenyan localization and whatever eTIMS route your version uses. Inventory still matters, because eTIMS integrations may require item-level data such as product classification and unit codes, and some may report stock movements as well as sales. What exactly your connector needs is something I confirm with Odoo or the module provider, and your tax advisor confirms the rules behind it.
What I check:
Landed costs from Mombasa imports reach product cost through Odoo's landed costs feature, while import duties and VAT are recorded in the accounting setup. The localization and any eTIMS connector differ by version and edition, so gaps are logged with an owner through gap analysis.
Kenyan importers often store goods in third-party or bonded warehouses before duty is paid or before onward distribution. In Odoo these become locations or warehouses with a status that shows whether goods are cleared, with an agreed exchange of data with the provider and a named person for mismatches.
Barcode scanning helps at receipt, picking and counts, but in recent versions Odoo's barcode app has been an Enterprise feature, and depots with weak connectivity need a fallback. I test scanners on the network each depot really has before committing.
Cases where I would steer you away from Odoo Inventory, or ask for stronger proof:
I have no Odoo sales interest in the outcome. If you are still choosing a platform, start with the Kenya ERP consultant page; processors should also read Odoo Manufacturing Kenya. Work is remote, with visits only by arrangement.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
Yes. Resupply routes with dispatch, transit and depot receipt steps keep goods on the road in a transit location until they arrive. Short or damaged receipts go to a claims location. I design these steps and test them with one depot first.
eTIMS integrations may require item classification and unit codes on products, and some report stock movements too. Requirements depend on the route your version uses, so I confirm them with Odoo or the module provider and make sure the product master is complete before go-live.
Yes, Odoo supports several companies in one database, each with its own warehouses. Each company needs its own localization and tax setup, and automatic intercompany documents depend on edition. I check localization coverage for Kenya and each neighboring country in a test database before you commit.
Odoo is web-based, so depots need a usable connection. I test the screens and scanners each depot will use on its real network, recommend backup connectivity where needed and agree a written fallback for receiving and dispatch during outages, with a supervisor check once the link returns.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.