One person, and the work that vouches for him

Where the experience comes from

Not from implementing Odoo for other people first. From running a multi-brand food and beverage group in Jeddah on it — restaurants, a bakery, catering and e-commerce across several companies in one Odoo 19 Enterprise database, with the point of sale, the manufacturing, the multi-company accounting and the storefront all in daily use.

That means the work starts from the operator's side of the desk. The question is never only “can Odoo do this” — it is whether the number that comes out at the end of the month is one you would sign your name to.

How I work

• Evidence before opinion. Findings come with the query, the record or the line of code behind them. If something is unverified, it is labelled unverified.
• Native Odoo first. Custom code only where standard configuration genuinely cannot do the job — and I will tell you when it can.
• Upgrade-safe by default. No patched core files, no changes that make the next version somebody else's problem.
• Plain answers. Including “that is not worth doing” and “this will not fix what you think it fixes.”

Published work

Some of the development is packaged and sold publicly on the Odoo Apps Store, which means the code is bought, installed and reviewed by people with no relationship to me. Each module has a write-up here explaining the problem it solves, how it works, and — explicitly — what it does not do. Alongside that, EHC publishes its own apps: Dawam, Indkom and Surra, and runs the Made with Love marketplace.

Odoo NotesWhat EHC does