Waqas Riasat
Odoo developer at Way4Tech. Builds and maintains the modules listed on the Odoo apps store under this account, and writes the Odoo posts on this site.
Every figure on this page is counted at build time from the module catalogue and the blog, so it matches what is actually listed. Each listing below can be opened on the Odoo apps store and read in full.
What he works on
- โ Odoo module development.
120 modules listed on the Odoo apps store, every one of them built for Odoo 19.0. The catalogue on this site is generated from the manifest of each module, so the pages and the code cannot drift apart.
- โ Odoo implementation and support work.
Scoping, configuration, data migration, and the long tail of production support that follows a go-live.
- โ Writing on this site.
36 posts, tagged implementation, e-invoicing, odoo implementation, localization and payroll among others. All of them are listed further down this page.
Published work you can inspect
The largest of the listings, linked to the Odoo apps store so the version, the description and the price can be checked at source.
WT Dental Clinic Management
Odoo 19.0
Areas the published modules cover
Counted from the category in each module manifest.
Posts
The Odoo implementation checklist
A checklist you can actually work through: what to settle before signing, what to gather per phase, the go or no-go criteria, and who owns what after go-live. Every item is a thing somebody ticks, not advice.
Odoo 18 vs Odoo 19: upgrade now or wait
We will not sell you a feature-by-feature diff we have not verified. What we can source is which version ships the localization or payment provider you need, and a test for whether your upgrade is urgent or deferrable.
Odoo Community vs Enterprise, decided properly
The edition question gets answered on the wrong number. What Community genuinely leaves out, the four triggers that actually decide it, and why none of our 139 modules needs an Enterprise subscription.
Odoo implementation in Australia: PINT A-NZ, payday super, and nine payment rails with no connector
What an Australian Odoo build has to satisfy: Peppol eInvoicing under PINT A-NZ Billing, GST and BAS, state payroll tax, payday super since 1 July 2026, and the payment and carrier rails Odoo 19 does not ship.
Why Odoo implementations fail
Not the software. The same failure modes turn up across implementation, migration, integration, payroll, POS and e-invoicing work. Named plainly, with the cheap prevention against each one.
Odoo implementation in Canada: 13 tax positions, Interac, and the payroll that is not in the box
What a Canadian Odoo build has to satisfy: no e-invoicing mandate but a Quebec WEB-SRM regime, GST, HST, QST and PST by province, Regulation 105 withholding, and the payroll, Interac and Canada Post gaps Odoo 19 does not fill.
The Odoo implementation timeline, week by week
Six phases, three published time bands, and the gate that has to close before each one ends. What a 3 to 4 week rollout compresses, what an 8 to 12 week one adds, and why configuration is never the thing that runs late.
What an Odoo implementation actually costs
The published bands are the easy part. What moves the number is how many of your payment rails and couriers have no Odoo connector, and whether your market runs clearance or reporting e-invoicing. Counted per country.
Odoo implementation in the United States: no mandate, 45 sales tax regimes, and where the budget goes
There is no US B2B e-invoicing mandate. What decides a US Odoo build is sales tax across up to 45 state regimes, nexus thresholds that keep moving, the 1099 changes for tax year 2026, and the payment and carrier integrations Odoo 19 does not ship.
Odoo implementation in Bahrain: no e-invoicing mandate, and WPS 2.0 anyway
Bahrain has 10% VAT, no e-invoicing obligation, and an Enhanced Wage Protection System that ended manual salary payments. What the market requires of the system, and the eleven of fourteen couriers Odoo does not cover.
Odoo implementation in Turkey: e-Fatura, the รถzel entegratรถr question, and why hosting is a compliance decision
What a Turkish Odoo build has to satisfy: e-Fatura and e-Arลiv through GฤฐB, the private integrator your client is already contracted to, e-Defter, the archiving rule that constrains hosting, and the couriers with no native connector.
Odoo implementation in Jordan: JoFotara rejects your discount policy, and nine payment rails have no module
What a Jordanian Odoo build has to satisfy: JoFotara clearance on UBL 2.1, the negative-value rejection that forces a pricing redesign, the ISTD rounding tolerance, and the wallets and rails that are custom builds.
Odoo implementation in Oman: Fawtara has dates, Odoo has nothing for it
Decision 189/2026 fixes Oman's e-invoicing dates at 1 April 2027 and 1 October 2027, on PINT OM over Peppol. Odoo 19 ships a solid Oman accounting localization and no e-invoicing at all. Where that leaves your plan.
Odoo implementation in Egypt: two ETA systems, a USB key, and accounting standards that are not IFRS
What an Egyptian Odoo build has to satisfy: ETA e-invoice clearance, the separate e-receipt system, CAdES-BES signing on a physical token, Egyptian Accounting Standards, and the payroll that has no localization.
Odoo implementation in France: the Plateforme Agreee, the annuaire, and where go-lives slip
What a French Odoo build has to satisfy from 1 September 2026: routing through an approved platform, the four new mandatory invoice mentions, FEC on audit, the DSN gap, and the payment and carrier rails Odoo 19 does not ship.
Odoo implementation in Kuwait: the 5% retention is the project, not the tax code
Kuwait has no e-invoicing mandate and no VAT. What it does have is a 5% contract retention tied to tax clearance certificates, three-decimal currency, and a localization that stops at the chart of accounts.
A chart of accounts is not compliance: what an Odoo country localization actually contains
Odoo ships a localization for your country. That can mean anything from a chart of accounts and nothing else to a full clearance integration. How to tell which one you are getting.
Odoo implementation in Bangladesh: no e-invoicing mandate, and what that actually changes
Bangladesh has no clearance e-invoicing scheme. What it does have is Mushak 6.3, EFD/SDC devices in named sectors, and an l10n_bd module that stops at a tax report. Here is what that leaves you to build.
Odoo implementation in Germany: E-Rechnung, DATEV and the four rails you have to build
What a German Odoo build has to satisfy: the section 14 UStG e-invoicing transition, SKR03 or SKR04, the DATEV handover, ELSTER and E-Bilanz gaps, and the payment and carrier integrations Odoo 19 does not ship.
Odoo implementation in Qatar: no VAT, no e-invoicing spec, and a chart of accounts
Qatar's e-invoicing law is an approved draft with nothing in force, l10n_qa is a chart of accounts and nothing more, and Dhareeba has no Odoo integration. What that means for scope, cost and sequencing.
Odoo implementation in India: IRN, e-way bill and the audit trail question finance asks first
What an Indian Odoo build has to satisfy: GST e-invoicing through an IRP, the e-way bill, the 30-day reporting bar, the rule 11(g) audit trail, and which couriers and gateways still need buying or building.
Odoo implementation in the UAE: the ASP deadline sets your timeline
The UAE Electronic Invoicing System puts an Accredited Service Provider between you and the FTA, and Odoo ships no UAE e-invoicing module. What the mandate obliges, what is missing, and how to plan around both.
Odoo implementation in the United Kingdom: MTD, Bacs and the parts that are not in the box
What a UK Odoo build actually has to satisfy: Making Tax Digital through the HMRC API, CIS deduction rates, Bacs files, Peppol for public-sector buyers, and the payment rails and carriers Odoo 19 does not ship.
Odoo implementation in Pakistan: FBR Digital Invoicing first, everything else after
What a Pakistani Odoo build has to satisfy before anything else: FBR Digital Invoicing clearance, provincial sales tax on services, section 153 withholding, and the wallets and couriers that have no connector at all.
Odoo implementation in Saudi Arabia: what ZATCA decides before you do
A Saudi Odoo build is shaped by Fatoora clearance, GOSI and a payment and courier list that sits mostly outside Odoo's shipped connectors. What the market requires, what is missing, and what to have ready.
Build it, buy it, or configure it: picking Odoo modules without regret
A three-way test for every requirement, what to check on an apps store module before you buy, how to write custom code that survives an upgrade, and the questions that kill bad requests early.
How to scope an Odoo project so the quote survives contact with reality
Fixed price only works against a scope somebody wrote down. How gap lists, dispositions and per-item estimates keep a quote honest, and which parts should never be quoted before an assessment.
Multi-company and multi-currency in Odoo: the calls you cannot take back
One database or several, how many decimals, where the data physically lives, and which entity files what. The setup decisions that are cheap on day one and a migration afterwards.
Eight early warning signs an Odoo rollout is going wrong
Most failed ERP projects were visibly failing in week three and nobody said so. The signals that show up early, what each one costs by month four, and the cheap fix while it is still cheap.
Moving off spreadsheets into Odoo without stalling halfway
The failure mode is not a bad system, it is a half-migrated one where both the sheet and the ERP are partly true. A working order for the move, and the decisions that keep it going.
Odoo payroll localization: twelve countries ship, and what the rest costs to build
Which markets have an official Odoo payroll localization, what those modules actually cover, what has to be built where there is none, and why the parallel run is the only proof that counts.
What Odoo's delivery carrier list actually covers, and what that costs you
Across eighteen markets only three carriers are native everywhere. Which carriers Odoo 19 ships, which it does not, what an aggregator connector really buys, and how to budget the gap.
Choosing an Odoo payment gateway when Stripe is not available where you are
Odoo shipping a connector is not the same as you being able to open an account. How to pick a gateway when the default answer does not trade in your market and the local card scheme is not native.
Clearance or reporting: the question that decides your Odoo e-invoicing build
A clearance mandate puts the tax authority inside your order-to-cash. A reporting mandate does not. That one distinction changes the Odoo build, the data work and the go-live plan.
The Best HRMS for Pakistan Businesses in 2026
An honest review of HRMS options for Pakistan SMBs - BambooHR, Keka, Darwinbox, Odoo HR, and custom builds. Which fits your scale and budget?
How to run your own Odoo SaaS platform
Step-by-step guide to building a multi-tenant Odoo SaaS for your own customers. Architecture, hosting, automation, pricing.
Questions about an Odoo build?
Send the details and you get a straight answer on whether it is a configuration, a purchase, or a build.