Odoo Customization Services in Pakistan
Custom code is a liability you agree to carry. We keep it small, keep it in its own module, and write it so the next upgrade does not eat it.
What changes the cost of Odoo customization in Pakistan
The delivery method is the same everywhere. What moves the number is what this market demands of the system, and how much of that Odoo already covers.
Pakistan runs FBR Digital Invoicing (electronic sales tax invoicing under section 23 of the Sales Tax Act 1990, Chapter XIV of the Sales Tax Rules 2006). That is configuration and testing work inside the build, not an afterthought, and it is the item most often left out of a quote.
9 of the 13 payment options that matter in Pakistan are not shipped with Odoo, so they need a paid connector or a build. 4 ship in the box.
10 of the 13 couriers used in Pakistan have no Odoo connector. 3 do. Which ones you actually use changes the estimate more than the number of users does.
Odoo's Pakistan localization does not cover everything. The gaps are listed on the country page and each one is either a build or a bought module.
Statutory payroll in Pakistan has its own rules. Whether Odoo ships a payroll localization for this market decides if that is configuration or development.
Market facts on this page checked on 22 August 2026 by Waqas Riasat, Way4Tech.
Where Pakistan starts from
Pakistan has 5 native localization items in Odoo and 5 documented gaps beyond them. Customization work here usually starts at that gap list, not from a blank module.
Where we deliver in Pakistan
Customization does not change shape by city. The brief is written the same way for a team in Karachi as for one in Sialkot: what the process actually is today, and where Odoo's default flow does not match it. Karachi, Lahore, Islamabad, Rawalpindi, Faisalabad, Multan, Peshawar and Sialkot, and Punjab, Sindh and Khyber Pakhtunkhwa, are covered.
What odoo customization has to satisfy in Pakistan
The rules that decide how much of this is configuration and how much is a build. Everything below is from our Pakistan register, checked against a primary source.
Live and in force for every sales tax registered person. SRO 1413(I)/2025 of 1 August 2025 brought all registered persons into scope on a phased calendar that ran out during 2025, and FBR's Sales Tax General Order 01 of 2026, dated 30 March 2026, restates the obligation as applying to all sales tax registered persons.
- Clearance model, not post-audit reporting. Invoice data goes to FBR's Computerized System in real time and the system returns a unique FBR invoice number before the invoice is issued to the buyer.
- JSON payload posted to the FBR / PRAL digital invoicing web API. There is no XML format in this scheme.
- Unique FBR invoice number printed on the invoice, in the format XXXXXX-DDMMYYHHMMSS-0001.
- Verifiable QR code of 7x7 mm, generated from the unique FBR invoice number and printed on the receipt.
- Digital signature created and recorded on the sales tax invoice.
- Accounting Sales tax records and documents must be retained six years after the end of the tax period to which they relate, under section 24 of the Sales Tax Act 1990. FBR's own summary page still says five years and is out of date against the Act.
- Accounting There is no SAF-T style audit file. The closest thing is Annexure C of the monthly sales tax return, which is now auto-populated from the electronic invoices cleared through the integrated system, so the invoice data model and the return draw on the same data.
- Accounting Financial statement disclosure is driven by the schedules to the Companies Act 2017, administered by SECP: the Fourth Schedule for listed companies and the Fifth Schedule for non-listed companies, with the applicable reporting framework per class of company set in the Third Schedule. SECP amends these by SRO, so the disclosure set moves.
- Accounting There is no statutory national chart of accounts. Odoo's Pakistan localization ships a basic chart, taxes, a tax report and a withholding tax report, and companies extend it themselves.
- Payroll EOBI old-age benefits contribution is 5% from the employer and 1% from the employee, calculated on the federal minimum wage rather than on actual salary. That fixed base is the detail most generic payroll builds get wrong.
- Payroll Employers with six or more workers must register with the provincial social security institution for the province the employee works in, PESSI in Punjab and SESSI in Sindh. The contribution is employer only.
- Payroll Salary tax withheld by the employer is deposited with FBR within seven days, and a withholding statement is filed quarterly by the 20th after quarter end. The tax year ends 30 June, and annual salary certificates follow it.
- Basic Pakistani chart of accounts
- Sales tax taxes
- Tax report
- Withholding tax report
- PKR currency and standard Odoo accounting on top
- Unique FBR invoice number, the 7x7 mm QR code, the digital signature, the software registration number on the invoice layout, and the 72-hour edit window with Commissioner approval after that.
- Provincial sales tax on services. Separate registration, rate set and return per provincial authority, and the input tax split between the federal and provincial regimes.
- Section 153 withholding driven by vendor ATL status, with the ATL and non-ATL rate pair per payment type, plus the quarterly withholding statement.
- Sales tax return annexures and the STR-7 output.
- Payroll. There is no Pakistan payroll localization, so EOBI, provincial social security and salary tax slabs are all custom.
Reviewed 2026-08-22. The full Pakistan register
How we run the work
5 stages, the same in every market: Requirement capture, Technical specification and estimate, Build in sprints, Test and review, Deploy and hand over. The method does not change by country, so it is written up once rather than repeated here.
The integrations this market usually needs
Badged by what it takes in Odoo. Anything not marked In Odoo is a paid connector or a build, and that is the part quotes usually miss.
Questions we get asked
- Will customisation break our next Odoo upgrade?
- Well-written custom modules do not break, they need porting, and the effort depends on how deeply they reach into standard behaviour. Code that extends existing models ports quickly. Code that replaces standard logic is expensive at every version. That is the single biggest reason we push back on requests that duplicate what Odoo already does.
- Do we own the code?
- Yes. Source goes to your repository with the commit history intact, plus build and deploy instructions. There is no licence key, no time bomb and no obfuscation. If you replace us, the next team can read what we wrote.
- Does Odoo have an official localization for Pakistan?
- Yes. Odoo ships 5 native items for Pakistan, covering the basics of the chart of accounts and statutory setup. 5 areas are still outside that localization and get built or bought separately.
- Is e-invoicing mandatory in Pakistan?
- Live and in force for every sales tax registered person. SRO 1413(I)/2025 of 1 August 2025 brought all registered persons into scope on a phased calendar that ran out during 2025, and FBR's Sales Tax General Order 01 of 2026, dated 30 March 2026, restates the obligation as applying to all sales tax registered persons. The Pakistan e-invoicing page carries the full detail and the sources.
- What VAT or sales tax does Odoo have to handle in Pakistan?
- Federal sales tax on goods is 18%, set by section 3(1) of the Sales Tax Act 1990. Reduced rates and zero rating apply to specified goods.
- Do you work with businesses in Karachi and other parts of Pakistan?
- Yes. Odoo customization runs remotely by default, and being based in one city inside Pakistan does not change the plan or the price. Cities we cover for on-site visits: Karachi, Lahore, Islamabad, Rawalpindi, Faisalabad, Multan, Peshawar, Sialkot. Regions we cover: Punjab, Sindh, Khyber Pakhtunkhwa. We travel on-site for discovery workshops and go-live week when the engagement calls for it.