Most teams running Odoo in Arabic-speaking markets hit the same wall the first time they print a customer invoice or a delivery slip: the numbers look fine, but the Arabic characters render as empty rectangles, disconnected letterforms, or a face that simply was not designed for the Arabic script. Odoo core wires a fixed set of report fonts into the QWeb report layouts and the wkhtmltopdf rendering path, and none of them are chosen with Arabic typography in mind. You can switch the company font in the report settings, but the out-of-the-box choices do not give you a properly hinted, RTL-aware Arabic family, so bilingual documents look unprofessional and, in regulated markets, may not match the presentation auditors and customers expect.

The Arabic Reports Font Pack is a build-to-order Odoo module that replaces the default report typeface with a licensed, Arabic-compatible font family and wires it correctly through the whole PDF stack. Technically, we register the font faces in a dedicated asset bundle (loaded into the report web.report_assets_common / @font-face layer) so wkhtmltopdf embeds and rasterizes the glyphs instead of substituting a system fallback. We extend res.company and the paper-format / external-layout configuration so the Arabic face becomes the effective default across account.report_invoice, the sale and purchase order documents, stock pickings, and the customer portal — with the shaping and direction: rtl / unicode-bidi rules set so Arabic contextual forms join correctly and mixed Arabic-Latin lines do not scramble.

Because the pack is delivered as its own module with a clean __manifest__.py, it does not patch Odoo core files: font assets ship inside the module, the QWeb templates are extended via inheritance (xpath on the report layouts), and any configuration lives on standard models so it survives version upgrades. We handle the licensing and embedding subset correctly, keep the file size sane by subsetting to the ranges you actually print, and make sure the same font is applied consistently whether a document is generated interactively, from a scheduled action, or through the XML-RPC / JSON-RPC API. Where you need the on-screen backend or website to match the printed output, we extend the relevant frontend asset bundles too. It is built and tested for Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise (Enterprise's Studio-authored reports are covered the same way).

Delivery is build-to-order: it starts with a short scoping call where we confirm which documents, languages, and font weights you need, then we build against a copy of your database on staging, run UAT with your real invoices and reports, and deploy to production with a rollback plan. Typical delivery is 2-4 weeks from confirmed scope. Pricing starts from $299 (indicative, single-company base scope); additional document types, multiple font weights or families, multi-company deployment, and deeper localization work (extra languages, per-company branding, or bespoke typographic tuning) increase the quoted scope. You get a fixed quote after the scoping call, never a surprise on the invoice.