Odoo in Qatar

Noor Digital implements Odoo, a business suite assembled from separate modules - sales, CRM, inventory, purchasing, accounting, manufacturing, HR, website, point of sale - sharing one database. Qatar companies choose it because you start with two modules and add the rest as the business grows.

• Community edition carries no per-user fee; Enterprise is paid
• Enterprise adds modules, mobile applications and vendor support
• Widely used, so support does not depend on one supplier
• Poor fit where a specific system is already mandated
• Poor fit where nobody internally will own it after handover

Noor Digital starts with the smallest useful set, normally two or three modules that fix something painful, and adds the rest once people are comfortable. Every extra module carries an ongoing cost even when it installs free, because somebody has to keep its data accurate.

• Trading company: purchasing, inventory and invoicing first, quotations second
• Services firm in West Bay: CRM, quotations, timesheets and invoicing
• Retailer or cafe: point of sale with inventory behind it
• Contractor: projects and purchasing costed against the job, not the month
• A module nobody maintains produces confident numbers that are wrong

Noor Digital makes both decisions during scoping rather than by default. Community is open source with no licence fee and a smaller module set; Enterprise is a paid per-user subscription adding modules, mobile applications and vendor support. Which is right depends on the modules you need, not on principle.

• Odoo's own hosted service is the least work and least flexible
• Their developer platform allows custom code with staging environments
• A server we manage gives full control and full responsibility
• Banks and government entities ask exactly where the database sits
• Under Qatar's Personal Data Protection Law, Law No. 13 of 2016, accountability stays yours

Noor Digital configures first, customises last, and says no to some requests. Fields, stages, approval rules, pricing rules and document layouts all change through the interface, and anything achieved that way costs nothing at the next upgrade. Custom code is a different, annual commitment.

• Odoo publishes a major version each year; custom lines need retesting
• Heavy customisation means paying yearly or stopping upgrading altogether
• The test: does this difference win business, or is it habit
• Custom work kept in separate modules, documented, and handed over
• Editing the core turns the next upgrade into a rebuild

Noor Digital tests Arabic in Odoo before promising it, because the interface and the printed output are separate problems. The interface supports right-to-left and staff each work in their own language against the same database. Printed templates are where the actual work sits.

• Quotations, invoices and delivery notes laid out for Arabic and proofed on paper
• Number alignment, table columns, logo position and trade licence line
• Decide early which master data field holds Arabic and which English
• Get it wrong and search stops working for half your staff
• Qatar localisation packages vary by release, so we check the current one