Skip to content
Walid Redwan

Independent Odoo partner · Egypt & the Gulf

Odoo, implemented properly.

Most failed implementations were not a software problem. I run implementations end to end — scoping, configuration, custom modules, data migration and go-live — and stay on afterwards, so the system your team logs into on Monday is the one that was promised.

Working across Odoo 17 · 18 · 19 Enterprise & Community Arabic-first localization Egypt ETA e-invoicing UAE VAT

2013

on Odoo since OpenERP 7.0

7

active client systems

2

countries served

100%

work done by the consultant you hire

Services

What I actually do

Narrow on purpose. Everything below is Odoo — no reselling, no subcontracting the delivery to a team you never meet.

Implementation

From discovery to go-live: process mapping, fit-gap against standard Odoo, configuration, data migration, training and hypercare. Standard first, custom only where the business genuinely differs.

Custom development

Prefixed, self-contained modules that survive upgrades. No core patching, no unversioned studio sprawl — everything in git, reviewed, and documented so the next developer is not stuck.

Migration & upgrades

Version jumps with the custom layer carried across: module refactoring, data validation, a parallel-run staging environment and a rollback plan you can actually execute.

Project rescue & audit

A stalled or half-delivered Odoo, taken apart and reported honestly: what is salvageable, what has to be rebuilt, what it costs. Often the fastest money you will spend on the project.

Integrations & compliance

Egypt ETA e-invoicing, UAE VAT, payment gateways, WhatsApp, shipping carriers, bank statements and external systems — built as modules, not as scripts running on someone laptop.

Support & managed care

A named person who already knows your database. Monthly retainer covering fixes, small enhancements, user questions and upgrade planning, with a clear response window.

Services →

How I work

Three commitments

These are the things clients say made the difference — so they are stated up front rather than discovered later.

01

Standard Odoo until it hurts

Every customization is a permanent tax on upgrades, training and support. If standard Odoo can carry the process with a change in how you work, that is the recommendation — even when the custom build is the bigger invoice.

02

Everything in git, everything documented

Your modules, configuration notes and deployment history live in a repository you own. If we stop working together, another developer can pick it up and be productive the same week.

03

One accountable person

You talk to the consultant who writes the code and configures the system. Nothing gets lost between a sales contact, a project manager and an offshore team.

Selected work

What the projects look like

Client names are withheld until each one approves publication. The shape of the work is what matters here.

Security & manpower services

Egypt & UAE

Thousands of guards deployed across hundreds of client sites, scheduled on spreadsheets, with payroll rebuilt by hand every month and no reliable link between a shift worked and a line on the client invoice.

Site and shift scheduling built as a custom module on top of standard Employees and Payroll, feeding both payroll and contract billing from a single attendance record. Monthly close went from a fortnight of reconciliation to a reviewed run.

Trading & distribution

Egypt

A growing product catalogue with landed costs, multiple warehouses and a sales team quoting from memory, on a system nobody could safely upgrade because customizations sat in the core.

The custom layer rebuilt into prefixed modules with a staging-then-production promotion path, landed cost automated, and margins visible per shipment for the first time.

Case studies →

Considering Odoo, or trying to fix one?

A short call is usually enough to tell whether this is a configuration problem, a process problem or a project problem.

Book a discovery call