01
Production
M-Pesa Daraja
Safaricom Daraja API. All four flows, end-to-end signed and reconciled.
- Flows
- STK Push, C2B, B2C, B2B
- Auth
- OAuth 2.0 + signed callbacks
- Retry
- Idempotent, exponential
- Audit
- Per-tx log in Odoo
We build Odoo to run your real operation. Not slide decks, not sandboxes, not vendor demos that fall over on month one.
You get the same engineers from kickoff to support — no handoffs, no junior-bench bait-and-switch.
Every implementation is built for Kenyan compliance: eTIMS invoicing, PAYE, NSSF, SHIF, HELB, M-Pesa via Daraja.
We deliver these in any combination — a standalone implementation, a customisation sprint, an integration project, or a long-running support retainer. Most engagements blend two or three.
We’d rather build a working module than draft a strategy deck. Every line of code we write is built to survive your Kenyan tax cycle, your monthly M-Pesa reconciliation, and your auditor’s questions in October.
Stand up Odoo as your operating system — sales, inventory, accounting, HR, manufacturing, and the apps that actually fit how your team works in Nairobi, Mombasa, or Kisumu.
We configure the apps your business actually runs on, wire them to your bank, your KRA account, and your M-Pesa till, then train the team that uses them daily.
Every implementation moves through the same four stages, with written sign-off between each. No surprises, no scope drift.
Live Odoo instance, configured for your chart of accounts, your warehouses, your tax rates, with post-launch hyper-care included.
We’ll recommend based on your data residency, audit, and budget needs — not based on what earns us a kickback.
Native invoicing day one.
On the floor with your team, included.
First-response SLA.
Stock Odoo gets you most of the way. We build the modules, workflows, and reports that close the gap — without forking core or breaking your upgrade path.
Six production-grade connectors. Each one wired with retry logic, signed callbacks, and a full audit trail in Odoo. When something fails, you know what, when, and how to replay it.
Safaricom Daraja API. All four flows, end-to-end signed and reconciled.
Full OSCU and VSCU device flows. Invoices signed before they leave Odoo.
Equity, KCB, Co-op, NCBA, ABSA, DTB. Statement ingestion and auto-reconciliation.
Order confirmations, invoices, payment links, support threads. Cloud API native.
Validate counterparty PINs at point of entry. Block invalid PINs before invoicing.
Sendy, Pickup Mtaani, Bolt, in-house fleets. Status webhooks into Odoo orders.
QuickBooks, Tally, Sage, Pastel, custom spreadsheets, that one Access database from 2014. We move it all into Odoo with the history intact and the trial balance still balancing.
We map every table, every column, every quirk of your legacy data — the misspelt customer names, the closed prior periods, the GL accounts no one remembers creating.
Deduplication, normalised tax codes, validated VAT/PIN numbers, properly typed dates. Your data lands in Odoo cleaner than it left the source system.
Full migration in a staging instance. We balance trial balances, customer ageing, and stock valuations against your source — before you ever go live.
A single, scripted cutover window. Final delta sync from the legacy system, GL freeze, and switch — usually completed over a weekend.
Monday morning your team logs into Odoo and finds every customer, every invoice, every product, every payslip — right where they expect it.
A system no one uses is a museum. We train every role — from the warehouse clerk scanning a waybill to the CFO closing a quarter — in the language and the workflow they actually use.
All sessions delivered in English or Swahili. Recordings provided. Refresher session at 30 and 90 days post-launch included.
A real SLA with humans on the other end — not a ticket form that vanishes into a queue. Four priority tiers, response times we publish, and a named engineer who already knows your instance.
Every support engagement is owned by a named lead engineer who knows your customisations, your integrations, and your edge cases. We don’t rotate tickets to whoever has capacity — you talk to the same people every time.
Odoo unreachable, payroll can’t run, invoices can’t issue. Business stops.
A key workflow is broken (M-Pesa reconciliation failing, eTIMS rejecting). Workaround exists.
A report is wrong, a screen is slow, a permission isn’t quite right. Annoying, not blocking.
“How do I…?” — small enhancements, training questions, configuration tweaks.
Four engagement models, from a one-week diagnostic to a multi-year retainer. Most clients start with a Discovery Sprint, even if they have already decided to build.
Reach us through any channel, or use the form. Every enquiry gets a real reply from a real Odoo consultant within 24 hours.
By submitting, you agree to be contacted about your project. We never share enquiries with third parties.
An Odoo consultant will reply within 24 hours, weekdays.