Custom Odoo Modules
New models, fields and workflows for the parts of your business Odoo doesn't ship out of the box.
BUILT IN-HOUSE
CUSTOM DEVELOPMENTS.
Custom Odoo modules, portals, dashboards and reports, scoped to what the standard doesn't cover, written against your processes and handed over with the source.
Your workflow
We write this
Custom module
Odoo core
M‑Pesa · eTIMS · USSD
What we build.
Six kinds of Odoo development work we've shipped across finance, operations, logistics and field teams in East Africa.
Portals
Branded customer, partner and staff portals. Secure, mobile-friendly, tied into your Odoo records.
Dashboards & Reporting
Board-ready dashboards and operational reports built on live Odoo data. No spreadsheets in the loop.
Workflow Automations
Approval chains, batch posting, triggered emails and scheduled jobs that take clicks out of the day.
Data Migrations
From legacy ERPs, spreadsheets and in-house systems into Odoo, without losing history or audit trail.
Recent builds
Seven custom developments, anonymised.
Recipe-accurate POS for a coffee chain.
POS order
Recipe engine
Stock moves
Cafe warehouse
A regional speciality coffee chain running a dozen cafes needed their POS to reconcile against ingredient stock the day a session closed. We extended Odoo POS to read each order against a recipe database, aggregate ingredient consumption (variants included), and post the resulting stock moves back to the cafe's warehouse, with cafe-to-HQ requisitions and auto-scrap on receipt layered on top.
Baristas never open an inventory screen; stock reconciles the moment a session closes.
- POS recipe-depletion engine with variant support
- Multi-cafe requisition workflow (draft to done)
- Role-based warehouse assignment per user
- Auto-scrap on receipt for consumable categories
Donor budgeting for a multi-currency NGO.
Donor budget
Burn-down engine
Frozen FX
Live spend view
An international non-profit with grants in five reporting currencies needed donor-budget burn-down in real time. We built a budgeting module that tracks each donor budget against invoices, payments and analytic lines with per-line frozen exchange rates, then layered tier-based approvals over cost centres, grants and payroll, plus a staff-advance workflow that locks the expense sheet until cleared.
Programme staff see spend against budget in real time, in the currency each grant reports in.
- Donor-budget model with live, multi-currency burn-down
- Frozen FX on every analytic line
- Tier-based approval chains on cost centres and grants
- Advance and clearing workflow wired to expenses
Feature-phone ordering over USSD.
USSD menu
USSD gateway
MTN MoMo
Sale order + delivery
A clean-cooking fuel producer selling into rural East Africa needed customers to order and pay without an app or a web browser. We built a generic USSD gateway as an in-house product and a fuel-specific flow on top: a customer dials a short code, walks through a menu, selects product and quantity, and pays via MTN MoMo. The session writes a sale order, triggers a delivery pick, and folds into the carbon-credit contract on the partner record.
Customers order and pay from a feature phone, with no app and no smartphone required.
- Reusable USSD gateway module
- MTN MoMo settlement on session complete
- SMS confirmations via Africa's Talking
- Carbon-credit contract attached to the partner
Outgrower tracking for a fair-trade importer.
Farmer registry
Certification gate
Purchase order
A European fair-trade importer sourcing from cooperatives across Sub-Saharan Africa needed one view over every farmer they buy from. We built an outgrower database that captures owned versus leased acreage, certification status and expiry, offtake volumes under agreement, training attendance and cooperative membership, and wired it into Odoo purchase orders so buyers can see who is certified for a given harvest.
Buyers see at a glance which farmers are certified for a harvest and whose certificates are about to lapse.
- Farmer registry with certification tracking and expiry alerts
- Acreage and offtake-agreement management
- Training history per farmer
- Purchase-order integration with certification gating
Post-period COGS revaluation for a commodity retailer.
Late landed cost
Revaluation engine
Journal delta
Daily snapshot
An East African energy retailer whose buy prices swing with global commodity markets needed to correct historical costs when landed-cost invoices arrived weeks late, and do it without reversing closed-period transactions. We built a revaluation engine that recalculates COGS across prior stock moves and landed costs, posts the delta to dedicated journals, and keeps daily product-valuation snapshots so auditors can trace the before and after.
Historical costs get corrected without reversing closed periods, with a daily trail auditors can follow.
- Retrospective COGS recalculation across historical moves
- Daily product-valuation snapshots
- Batch update wizards with full audit trail
- Integration with landed-cost timing
Device lifecycle for a gig-rider fleet.
Serialised device
Check-in / out
Repair order
Payroll deduction
An electric-mobility operator with hundreds of delivery riders needed to know, per rider, which phone, battery and tablet they were holding, what state it was in, and how much to dock this week if they broke it. We treated every serialised device as a tracked asset with a check-in/out state machine, wired repair orders so engineers can assign damage costs back to a rider's weekly bill, and added QR labels, SMS and portal access.
Every device is accounted for per rider, and repair costs flow straight onto the right weekly bill.
- Serialised device register with state machine
- Rider-level asset assignment and QR check-in/out
- Repair-driven damage deductions linked to payroll
- Rider portal and SMS notifications
Trips in, invoices and commissions out.
Nightly REST
Dedupe & match
Rate cards
Vendor bills
A fleet operator running corporate chauffeur services pulls booked trips from a third-party ride platform, bills them to corporate clients at contract rates, and pays drivers on a tiered commission. A nightly REST ingestion job pulls trips with deduplication and fuzzy driver and vehicle matching. A contract-rate-card engine prices per km with minimum charges and full-day caps. A payout engine then calculates commissions and posts vendor bills.
Trips land as invoices and driver payouts automatically, with a database guard so no trip is ever paid twice.
- Nightly REST ingestion with dedupe and fuzzy matching
- Contract rate cards (per-km, min charge, day-cap)
- Tiered commission payouts with vendor bills
- SQL-level guard on trip-to-payout uniqueness
Describe the gap and we'll scope the build.
Seven case studies, seven gaps the standard Odoo didn't cover. If you're reading this with an eighth in mind, send it over. A short call is usually enough to tell whether it's a module, a portal, a mobile app or a mix, and roughly what it costs.
Start the conversationNo build in that sector yet. The CTA card is still open.
Built to hand over
You own what we build.
Every build ships as source you control, documented and versioned, so your team or your next partner can pick it up without us in the room.
Source & repository
You get the full Git history and the repository. The code is yours, not licensed back to you.
Documentation
Each module ships with a README, data-model notes and an upgrade guide written for the next developer.
Automated tests
Critical logic is covered by Odoo unit tests, so a version upgrade doesn't quietly break what we built.
Versioned releases
Modules carry a version and deploy through your pipeline, so every change is traceable and reversible.
No lock-in
Standard Odoo patterns, no hidden dependencies. Any competent Odoo developer can maintain it.
Support after launch
We stay on for handover and support. You keep running whether or not we are still in the picture.
Need something bespoke?
Describe the workflow, the volume and the deadline; we'll tell you what building it looks like and what it costs.