A build-to-order Odoo localization that loads Algeria's full wilaya and commune hierarchy with bilingual French and Arabic names, wired into partner addresses and reporting. ECOSIRE builds, installs, and supports it after your quotation. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $299.00 USD; request a quote for a scoped proposal.
アプリマニフェスト
あなたのワークフローに合わせて構築
A build-to-order Odoo localization that loads Algeria's full wilaya and commune hierarchy with bilingual French and Arabic names, wired into partner addresses and reporting. ECOSIRE builds, installs, and supports it after your quotation.
自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。
一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。
ECOSIRE がお客様の Odoo 上で構築・設定・インストールします。
約2〜4週間で稼働し、リリース後のサポート期間が付きます。
If you run Odoo in Algeria, you have almost certainly hit the wall where res.country_state for Algeria is either empty or holds a handful of stale province names, and there is no concept of a commune at all. Sales reps type wilaya and commune names free-hand into street2/city, spelling them inconsistently in French, Arabic, or transliterated Latin, so your customer master becomes impossible to group, filter, or map. Delivery zones, tax jurisdiction logic, and any "revenue by wilaya" pivot fall apart because the geography lives in unstructured text instead of proper records. Odoo core simply does not ship the 58-wilaya, ~1,500-commune administrative structure, and it certainly does not carry the official bilingual French/Arabic names that Algerian invoices and shipping labels require.
We build a localization module that seeds the complete, current Algerian administrative hierarchy as first-class Odoo data. Wilayas are loaded as res.country.state records scoped to Algeria (country_id = DZ), and communes are added as a dedicated model (for example x_dz_commune or a namespaced dz.commune, agreed at scoping) with a many2one back to their parent wilaya, each carrying the official code, the French name, and the Arabic name. Bilingual names are handled through Odoo's translation layer so the same record renders in French or Arabic based on the user's or partner's language, rather than being duplicated into separate columns. The data ships as versioned XML data files in the module (data/ with noupdate where appropriate) so it installs cleanly and can be re-seeded or corrected on upgrade without clobbering records you have linked to.
On the integration side we extend res.partner with a commune field and, where you want it, computed helpers via @api.depends that keep wilaya and commune consistent (selecting a commune back-fills its wilaya; changing wilaya filters the commune domain). We wire the fields into the partner form and search views (XML/OWL), add them to the address block and to relevant list/search filters and group-bys, and expose them to QWeb so invoices, delivery slips, and other reports print the correct bilingual place names. Access is governed by ir.model.access.csv for the new commune model plus record rules if you multi-company, and the data is reachable over the standard XML-RPC/JSON-RPC API so external systems and e-commerce fronts resolve the same canonical geography. The module targets Odoo 17.0, 18.0, and 19.0, works on Community and Enterprise, and its __manifest__.py declares the correct dependencies (typically base/contacts) with no reliance on Enterprise-only features unless you ask for them.
Because this is build-to-order, nothing is downloaded off a shelf: after a short scoping call we confirm the exact model naming, which fields you need on the partner, report and view touch-points, and language defaults, then build, test on a staging copy of your database, and hand over installable source. Typical delivery is 2-4 weeks from confirmed scope. Pricing starts from $299 (indicative, single-company base scope); multi-company record rules, additional integrations (e-commerce, delivery carriers, external systems), deeper localization such as postal-code or daira layers, and migrating a large volume of existing free-text addresses into structured commune records increases the quoted scope.
Companies selling across multiple wilayas that need structured, consistent addresses to plan delivery zones and report revenue by region instead of free-typed city text.
Internal ERP owners and accountants who need bilingual French/Arabic place names to appear correctly on invoices, delivery slips, and partner records for local compliance and clean reporting.
Consultancies delivering an Algerian rollout who want a tested, maintainable localization data layer with proper `res.country.state`/commune modelling rather than building and maintaining the geography themselves.
Teams running Odoo eCommerce or carrier integrations who need canonical wilaya/commune values exposed over the API so checkout, shipping, and back office all reference the same geography.
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| Algeria geography coverage | Full 58 wilayas + ~1,500 communes seeded as proper records | Whatever you build and maintain yourself | Often partial or wilaya-only, no communes | |
| French + Arabic names | Bilingual via Odoo translation layer, prints on reports | Possible but you own the translation data | Language coverage varies, often French only | |
| Data model quality | `res.country.state` + dedicated commune model with parent link | Depends on your team's design discipline | Fixed model you cannot easily change | |
| Fit to your workflow | Built to your fields, views, and report touch-points | Fully bespoke but all effort is yours | Generic, take-it-or-leave-it configuration | |
| Testing & rollback | UAT on staging with a documented rollback plan | Only if you resource it | Install at your own risk, no engagement | |
| API exposure | Wilaya/commune exposed over XML-RPC/JSON-RPC for integrations | Requires deliberate design | Depends on module internals | |
| Support & ownership | Post-go-live support window + full git repo handover | Self-supported | Vendor-dependent, limited scope | |
| Total cost of ownership | Fixed quote from $299 indicative, then supported | High build + ongoing maintenance cost | Low sticker price, hidden gaps and rework |
No. This is a build-to-order module: ECOSIRE builds it to your confirmed scope, then installs and supports it. There is no instant download. We hand over installable source and a git repository once your version is built and tested on staging.
Typically 2-4 weeks from confirmed scope. After a short scoping call we lock the model naming, partner fields, and report/view touch-points, then build, run UAT on a staging copy of your database, and deploy. Larger integrations or address-migration volume can extend the timeline, which we state in the quote.
Pricing starts from $299 (indicative, single-company base scope). We hold a scoping call, confirm exactly what you need, and then issue a fixed quote before any build starts. Drivers like multi-company record rules, extra integrations, deeper localization layers, or migrating large volumes of free-text addresses increase the quoted scope.
We target Odoo 17.0, 18.0, and 19.0 on both Community and Enterprise. Your build is pinned to one major version. The module avoids Enterprise-only dependencies unless you specifically request features that require them.
Each wilaya and commune carries its official French and Arabic name through Odoo's translation layer, so the same record renders in the correct language for the user or partner. QWeb reports such as invoices and delivery slips print the appropriate bilingual place names.
Every engagement includes a post-go-live support window for defect fixes and questions. Because you receive the full git repository, you own the code. We can also quote ongoing maintenance, data refreshes if administrative boundaries change, or upgrades to a newer Odoo major version later.
Yes, as an optional scope item. We can build a migration routine that maps existing city/address text onto the new structured commune and wilaya records, with a documented rollback plan. Migration effort scales with data volume and cleanliness, so it is quoted after we review a sample.
A build-to-order Odoo localization that loads Algeria's full wilaya and commune hierarchy with bilingual French and Arabic names, wired into partner addresses and reporting. ECOSIRE builds, installs, and supports it after your quotation.