Contact Info
What should a UAE trading company look for in an ERP?
A UAE trading company needs an ERP that separates free zone and mainland entities, traces re-export goods from inbound bill of lading to onward shipment, manages post-dated checks and letters of credit, applies the right VAT treatment per route and costs stock in dirhams. I map those flows entity by entity, test platforms against them and oversee implementation independently of any vendor.
Last reviewed by Vikas Saroj
General trading is a familiar license activity in the UAE, and I work remotely with many kinds of trading houses there: re-exporters moving goods through a free zone to Africa, the wider GCC and South Asia, mainland distributors selling locally, and family groups that run both side by side.
A UAE trading business has a shape few other markets share. Goods may land in a free zone, sit there with duty suspended, then either leave for another country or cross into the mainland where duty and VAT come into play. Customers often pay by post-dated check, suppliers are paid against letters of credit, and the books are in dirhams while purchases are in dollars, euros, yuan or rupees.
I map those flows entity by entity, then help you choose and implement an ERP that keeps stock, cost and documents straight across all of them.
Most UAE traders I speak with have outgrown Tally and a set of personal spreadsheets for checks, containers and bank facilities.
I map which license and entity buys, holds and sells each stream of goods, and how goods passing from the zone entity to the onshore one are documented and priced.
Goods received into a free zone and shipped onward are traced from the inbound bill of lading to outbound documents, so stock that never entered the local market stays clearly separated.
Post-dated checks received and issued, with maturity, deposit, clearance and bounce handling, linked to customer credit limits so sales see real exposure before releasing an order.
Letters of credit, trust receipt loans and bank charges recorded against the shipments they finance, with due dates visible to finance well before repayment pressure arrives.
Tax treatment for local sales, exports, re-exports and designated zone movements set up following your tax advisor's guidance and tested on real invoices, including bilingual layouts.
Scripted demos against your mixed shipments and entities, a documented fit-gap, then oversight of the implementer through UAT, migration from Tally or spreadsheets, and go-live.
An ERP for trading should make these numbers available without a spreadsheet. I design the data model and reports around them from the start.
Entities, routes and payment habits
Requirements and platform fit
Migration, testing and go-live
The first workshop with a UAE trader usually produces a diagram with more arrows than anyone expected. A container from China lands at Jebel Ali and enters a free zone warehouse. Part of it is sold onward to a buyer in East Africa, part to a customer elsewhere in the GCC, and part is moved into the mainland for a local distributor, sometimes through a sister company. Each route has different documents, a different customs position and a different VAT question.
If the ERP treats all of that as one warehouse and one company, nobody can say which stock is still in the zone, what duty was paid on goods that crossed into the mainland, or which sales were exports. I separate it in the design: entities as companies, free zone and mainland locations as distinct warehouses, transfers documented as intercompany sales or stock movements as your advisor prefers, and re-export shipments linked back to the inbound bill of lading.
Declarations themselves are normally filed by a clearing agent through the emirate's customs systems. The ERP needs to hold what the agent asks for, receive the declaration reference and charges back, and attach them to the right shipment. I capture all of this in process maps before platform discussions begin.
Credit control in UAE trading has its own habits. Many customers still settle with post-dated checks, collected when the order is placed or on delivery and deposited on their dates. Finance needs to know which checks are in the drawer, which fall due this week, which have cleared and which have bounced, and sales needs that picture before releasing the next order to the same customer.
Generic accounting setups often record a PDC only when it clears, which hides the real exposure. The requirements I write treat received and issued PDCs as documents with a lifecycle, link them to customer credit limits, and produce a maturity report for the treasury view.
On the supply side, importers often buy against letters of credit or finance stock through trust receipt loans. Each facility has a maturity, a margin and charges that belong partly to the shipment's landed cost and partly to finance cost. Kept in a bank officer's spreadsheet, repayments surprise the business. I make sure the ERP records each facility against the purchase it funded, so cash planning shows what is coming.
These are the scenarios I write into UAT scripts, because a vendor demo will rarely show them unprompted.
Because the dirham tracks the dollar under a fixed peg, USD supplier invoices rarely move margins. Purchases in euros, yuan or rupees do, and many UAE traders buy in several of them. I set AED as the functional currency, record purchases in the supplier's currency, and keep exchange differences out of item cost so margins reflect freight, duty and clearing rather than currency movements.
Landed cost for a UAE importer typically includes ocean freight, clearing charges, duty where goods enter the local market, port and handling fees, and local transport. Goods that stay in a free zone and leave again build up cost differently, and the ERP must not load mainland duty onto them.
VAT treatment varies by route: local supply, export, movements involving designated zones, and imports. I do not set those positions; your tax advisor does. I make sure each scenario has a tax code, prints correctly on the invoice and lands in the right place on the return. Customer-facing documents often need Arabic alongside English, so I test bilingual templates early. Corporate tax considerations for free zone entities are also an advisor topic, but they affect how entities are set up, which is why I raise them at design stage. More background is on my UAE ERP consulting page.
Many UAE trading companies keep the books in Tally or a similar package, with stock, shipments and checks in spreadsheets maintained by individual staff. The trigger for change is usually a second entity, a free zone and mainland split, or an owner who wants margin per shipment and per customer without waiting for month end.
For migration, the items that matter are open purchase orders and LCs, containers in transit with costs accrued so far, open PDCs received and issued with their dates, customer balances and credit limits, and opening stock per location at landed cost. Finished shipments can remain in the old system for reference.
Zoho, Odoo, ERPNext and Business Central all have trading users and implementers in the UAE. The platform fit cards on this page summarize my view. Being independent, I compare them against your flows rather than a partner's template, then work with the implementer you appoint. The trading ERPNext migration case study shows the approach in practice. See also the UAE overview, the main trading ERP page and distribution ERP if you run van or route sales. All of this is delivered remotely, with live sessions inside UAE working hours.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
Yes. Most mid-market platforms support several companies in one system with intercompany transactions and consolidated reporting. The design work is deciding how goods and invoices move between the entities, how each is taxed and which warehouse belongs to which license. I document those rules with your advisor before configuration so the setup matches how you actually trade.
As documents with a lifecycle: received, held, deposited, cleared or returned, and the same for checks you issue. Each should link to the customer or supplier, count against credit exposure while it is held, and appear on a maturity report. Some platforms do this natively, others need configuration or an add-on, which I check during evaluation.
In most cases, yes. Stock held in a free zone for onward shipment should sit in its own warehouse or entity, so it is not mixed with goods that entered the mainland and carry different duty and VAT positions. That separation also makes re-export margins visible. The exact structure depends on your licenses and your advisor's guidance.
The ERP can apply whatever tax treatment you configure, but deciding the right treatment for each route is a matter for your tax advisor. I list every route you use, agree the treatment with your advisor, create a tax code for each and test them on real invoices before go-live.
My work is delivered remotely: online workshops, requirement sessions, design reviews and UAT support, scheduled inside UAE working hours. Recorded walkthroughs help warehouse and branch staff who cannot join live. On-site sessions can be discussed by arrangement for specific milestones, but most trading projects run well without them.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.