A free zone company and a mainland company
Sales, stock and staff are split across two licences while one team works on both, and the two sets of books are reconciled in a spreadsheet.
Odoo Dubai
Odoo Dubai · ERP for UAE trading groups
Azinove is an Odoo Partner working with entities in the Gulf: our engineering team is in Strasbourg, France, and the group is headquartered in Bahrain. A UAE rollout starts with the shape of the group: each licence as its own company and ledger, stock and landed costs followed across warehouses, and books in AED next to the currencies you actually settle in.
Talk to the engineers who would do the work
Tell us what you run today and what is not working. You get a considered answer, not a sales sequence.
How we frame the problem
Both are made when the database is created. Changing them after a year of postings is a data migration, not a setting.
The problem
A UAE group is often built as a single company in Odoo because the free zone and the mainland side share the same team, so sales between the two entities become internal transfers and freight and duty dissolve into a general expense account.
Our intervention
We map each licence to its own company, currency and ledger, decide what stays shared between them, and settle the costing method and the landed-cost rules before the first receipt is posted.
The intended result
Each entity reports its own stock and its own books, the group gets one consolidated view, and the cost of a shipment is known when it is received rather than when it is sold.
Let’s discuss the need
Odoo partner for the UAE
A Dubai group wants to know who the partner is and where it sits. These are the facts that can be checked.
The group’s headquarters
Azinove W.L.L
Flat 105, Building 1853, Road 1546, Block 815, Isa Town, Kingdom of BahrainCommercial registration CR 190436-1Office line and WhatsApp: +973 3329 9634Azinove is an official Odoo Partner. Its headquarters, Azinove W.L.L, is in Isa Town, Bahrain; its engineering team, Azinove SAS, is in Strasbourg, France. Forty-five projects and more delivered across the group.
We have no company or office in the United Arab Emirates. Dubai groups are served from Bahrain and Strasbourg, with on-site phases from Bahrain for the stock count, training and go-live.
Delivered in the Gulf
Bilingual public website for an owners-association manager in Bahrain.
Property platform and mobile app for the Bahraini market.
UAE configuration
Capabilities we set up in Odoo, not tax advice: how each licence is registered, and what applies to it, is confirmed with your tax adviser or auditor.
How these rules work, and how Odoo handles them, is in our guide Odoo for VAT and e-invoicing in Bahrain and Saudi Arabia.
When this service is useful
A UAE group rarely has one licence and one warehouse. That structure shapes the system long before anyone picks modules.
Sales, stock and staff are split across two licences while one team works on both, and the two sets of books are reconciled in a spreadsheet.
Availability depends on what sits in the free zone store, what has cleared customs and what is still at sea — and the same goods later leave on a different set of documents for re-export.
Freight, duty, insurance and handling are posted weeks after the goods, so the margin on a container is only known once it has been sold.
The system is operated in English because that is the language the staff share, while some customers, banks and authorities expect the document in Arabic.
Example scopes
Example scopes, not packages. What moves the effort is the number of licences and warehouses involved, and how much stock history has to come across.
Configure one company end to end: purchasing, multi-warehouse stock, landed costs, sales and books in AED.
Add the second licence as a company in its own right: its ledger, its stock, its documents and the flow of goods and invoices between the two.
Rebuild the warehouse model, the costing method and the landed-cost rules on an instance already in production, then correct the valuation it reports.
Capabilities
Four areas, arranged around the two things a Dubai entity has to get right early: how the licences are kept apart, and how goods are valued.
Scoping, configuration, data migration and go-live, across free zone and mainland companies alike.
Multi-warehouse stock, receipts, landed-cost allocation onto item cost, lot and serial traceability, and re-export flows.
Modules written in Python and OWL, plus API integrations with freight forwarders, customs brokers, banks and the tools already running.
EU or Gulf hosting, upgrades and support, with Odoo set up for the invoicing and tax rules each of your entities has to meet.
Possible deliverables
Every line names the entity and the warehouse it covers; the proposal says which ones are in scope.
Odoo in Dubai
No commitment · Clear scope · No specification required
Guardrails
Entity structure and stock valuation are the two subjects that hurt most when they are revisited after go-live.
Frequently asked questions
What decides the design of an Odoo in the UAE is the shape of the group and the way goods move through it.
One database, two companies inside it. Each keeps its own currency, chart of accounts, numbering sequences, document layouts and tax registration, with a consolidated view above them. What stays shared — items, contacts, users — and how sales between the two entities are recorded is decided during scoping, because it is hard to unpick later. Which entity invoices which customer, how each is registered for VAT, and what any e-invoicing requirement asks of the invoice itself follow your licences and your tax adviser; we configure what is confirmed to us.
Yes. Each warehouse carries its own locations and replenishment rules, and goods that have left the supplier but not yet arrived can be tracked and valued in a transit location of their own. Movements between the free zone store and the mainland warehouse become recorded operations with their own documents, instead of a quantity someone adjusts by hand. Re-export is handled the same way: the goods keep their origin, their lot and their reference from receipt through to the outbound document.
Odoo can spread those costs across a receipt by value, weight, volume or quantity. The configuration work is choosing the basis, handling the forwarder invoice that arrives after the goods, and deciding what happens when it arrives after the sale. The point of doing it properly is that margin can then be read per shipment, not only per item.
The company keeps its books in AED while purchases, sales and settlements are recorded in the currencies they are actually made in: pricelists, bank journals and the handling of exchange differences are configured around that. The rate source, how often rates are updated and how differences on open items are treated are agreed with your finance team and your auditor, then applied in the system rather than corrected in a spreadsheet afterwards.
The gap is hours, not days: our morning is your midday, so most of the work happens live rather than through overnight email. The project runs in English, the language your teams share, and Arabic is added where a document or a counterparty requires it. The phases where being in the building matters — the stock count, warehouse training, go-live — are scheduled in advance, with named contacts and written decisions in between.
Azinove is an official Odoo Partner headquartered in Bahrain (Azinove W.L.L, Isa Town, commercial registration CR 190436-1), with its engineering team in Strasbourg, France. We have no company or office in the Emirates; Dubai groups are served from Bahrain and Strasbourg.
Yes. The work runs remotely and live from Isa Town and Strasbourg, with on-site phases from Bahrain, an hour’s flight from Dubai, for the stock count, warehouse training and go-live. Documents are configured in English and Arabic, with the VAT positions your adviser confirms for each licence.
How the engagement runs
Dubai is a few hours ahead of Strasbourg, so most of the working day overlaps. What needs planning is the warehouse, not the calendar.
Licences, companies, currencies, warehouses and the movements between them are settled first.
The model is built on a test database, using your own items, suppliers and shipment documents.
Stock counts, goods in transit, opening balances and printed documents are validated by your finance and warehouse teams.
Cut-over happens in an agreed window tied to a stock count, followed by support with agreed hours.
Let’s discuss the need
Tell us about your licences, your warehouses, the currencies you settle in and how goods enter and leave. We will come back with a scope.
No commitment · Clear scope · No specification required
Talk to the engineers who would do the work
Tell us what you run today and what is not working. You get a considered answer, not a sales sequence.
Related capabilities
The core Odoo offer, the neighbouring Gulf market, and the bespoke work built around the system.
Odoo guides
Bahrain VAT, Saudi ZATCA e-invoicing, Bahrain HR and payroll, Saudi trading and distribution, Bahrain contracting, and what a compliant Odoo setup looks like, written by the team that configures it.
Bahrain’s 10 % VAT and NBR invoice rules, Saudi Arabia’s ZATCA Fatoora e-invoicing (phase 1 and the phase 2 integration waves), and how Odoo’s Bahrain and Saudi localizations handle them: taxes, bilingual invoices, QR codes, UBL XML, onboarding and go-live.
What a Saudi trading, wholesale or distribution company needs from Odoo: warehouses and routes, reordering rules, landed costs with customs duty and freight, FIFO or average cost valuation, purchases in dollars, euros or yuan with riyal accounting, B2B price lists and credit control, barcode picking and delivery batches, Arabic and English invoices cleared by ZATCA, and the reports that show margin per customer and ageing stock.
The partner decides more of an Odoo project’s outcome than the edition does. How to verify an official Odoo Partner, the ten questions to ask about localization, team, scope, migration, custom code, hosting, training, support, references and exit, and the red flags.
What a Bahrain employer needs from Odoo HR and payroll: employee files with CPR and work-permit expiry, Labour Law hours, overtime and leave, GOSI contributions for Bahraini and expatriate staff, the LMRA Wage Protection System file, work-permit fees and end-of-service rules, and what has to be built because Odoo ships no Bahrain payroll localization.
What a construction, MEP, fit-out or engineering contractor in Bahrain needs from Odoo: one project per contract with milestones and tasks, timesheets that carry real labour cost, an analytic account per site, progress invoices from milestones or percentage of completion, down payments, a clear way to book retention, subcontractor purchase orders with bill control, materials and equipment from stock, and a profitability dashboard the project manager and the accountant both trust.