Fields, views, automations and bilingual PDF reports adapted to how your Saudi company works, without custom code and without breaking upgrades.

Saudi contracting, trading and eCommerce companies rarely fit a standard form: a quotation needs the CR number and national address, a sales order needs the Salla order ID and courier, and the owner wants a sign off button before a price list goes out. Odoo Studio edits Odoo from inside the interface and stores every change as configuration that exports as a module, which is why Naqlah, an Odoo Gold Partner in Saudi Arabia, uses it from the first phase instead of writing code that breaks at the next upgrade.
Studio adds the fields Saudi operations need, such as CR number, unified national number, national address, iqama number and expiry, GOSI number and Qiwa contract ID, after Naqlah checks which already exist in the KSA localization so nothing is duplicated. Identifiers such as iqama numbers are restricted per user group through access control lists to respect the Personal Data Protection Law. Arabic and English report layouts are edited in the same designer with right to left alignment, while the seller VAT number, QR code, Arabic text and invoice type that ZATCA requires stay intact and the Phase 2 XML continues to come from the localization, not the report. Every change travels with the database through Odoo upgrades and is reviewed by Naqlah at each one, which is the core of our customization approach.
ZATCA safe reports
Layout changes keep the QR code, VAT fields and Arabic text in place. The e-invoice XML stays with the Saudi localization, so a nicer PDF never risks compliance.
Government portal fields
Fields for Qiwa, GOSI, Mudad and Etimad data are captured once on the employee or partner and exported when a portal upload is due.
Upgrade ready
Configuration, not code. Changes export as a module for staging tests, so the annual upgrade is a checklist rather than a rebuild.
1. Requirement captured
Naqlah sits with the process owner to define the field, view, report or automation, for example a Salla order ID on the sales order fed by a webhook from the Salla integration.
2. Built on staging
The change is built in Studio on a staging database, with access rules set for any sensitive field.
3. Tested bilingually
It is tested with Arabic and English data, and with ZATCA checks where an invoice or quotation layout is involved.
4. Exported and deployed
The change is exported as a module, documented in the change log and deployed to production, ready for the next upgrade.
Timelines depend on scope, and Naqlah gives you a clear roadmap in the first consultation.
| Area | Before | With Odoo via Naqlah |
|---|---|---|
| New field | Custom module from a developer | Added in Studio and exported as configuration |
| Report layout | Word template outside the system | PDF designer in Arabic and English |
| Automation | Manual follow up by staff | Rule on create, update or button click |
| External events | Nightly import or manual entry | Webhook in real time with a call log |
| Upgrades | Customizations break and get rebuilt | Configuration carried over and reviewed |
| Documentation | None | Exported module and change log |
Everything else, we cover in a free 30-minute consultation.
Free consultation. Meet the team and get a clear roadmap in one call.