E-commerce
We build online stores for Kenyan businesses — M-Pesa and card payments, real inventory management, and, where the back office demands it, a storefront wired directly into Odoo ERP so stock and orders stay in one place.
- From
- KES 130,000
- Timeline
- 4–6 weeks
- Deliverables
- 18 itemised
- Ideal for
- Retailers outgrowing WhatsApp order-taking
- Typical engagement
- KES 130,000 one-time · ERP integration quoted separately · full pricing
What we build
3 ways we deliver E-commerce
Storefront Build
A shop built to convert, not just to display a catalogue.
You receive
- Product and collection architecture
- Search, filtering and merchandising
- Cart and checkout optimised for mobile
- Customer accounts and order history
- Automated order and shipping notifications
- Performance tuning for slow connections
Payments & Checkout
Take money the way your customers actually pay.
You receive
- M-Pesa STK push integration
- Card payments via a Kenyan gateway
- Pay-on-delivery and manual reconciliation flows
- Automatic receipts and invoices
- Refund and partial-refund handling
- Failed-payment recovery prompts
Odoo ERP Integration
One source of truth for stock, orders and customers across the business.
You receive
- Two-way product and inventory sync
- Orders pushed into Odoo on payment
- Customer record matching and deduplication
- Price list and promotion mapping
- Sync monitoring with failure alerts
- Reconciliation runbook for your finance team
Shipped and running
Stores you can open right now
Not mockups. Inspect the load times and the checkout for yourself.
Kranian Farms
A high performance Agri-Ecommerce platform for Kranian Farms. Built with custom CMS and a fluid, immersive UI.
Survitec
A custom e-commerce platform for Survitec, integrated with Odoo ERP for back-office operations.
When stock lives elsewhere
If inventory is managed in a back office rather than on the site, we wire the storefront straight into Odoo ERP so stock, orders and customers stay in one place. Survitec is a live example of that build.
How the engagement runs
Four steps, and you see work at the end of each
Every stage ends in something you can hold, review or reject — never a status update.
Catalogue and rules
Week 1We map your products, variants, pricing rules and delivery zones before writing code. Most e-commerce projects go wrong here, not in the design.
You getA catalogue model and a written set of commerce rules.
Design the buying path
Week 1–2We design the path from landing to paid — listing, product, cart, checkout — for a mobile user on a mediocre connection, because that is who is buying.
You getDesigned buying path, prototyped end to end.
Build and integrate
Week 2–5Storefront, payments and any ERP sync are built together and tested against real transactions in a sandbox before a shilling moves.
You getA staging store processing test payments end to end.
Test, launch, reconcile
Week 5–6We run live low-value transactions, confirm every record lands where it should, then open the doors and watch the first days closely.
You getLive store, reconciliation runbook, and staff training.
What we build it with
No mystery stack
Everything below is mainstream and documented, so another team could pick your project up tomorrow if they had to.
Before you ask
Questions we get on E-commerce
Answered plainly, including the ones with awkward answers.
Yes. We implement M-Pesa STK push through the Daraja API, including callback handling and reconciliation, so a paid order is recorded as paid rather than needing someone to check a phone.
Something specific to your situation?
Ask us directly