ERP for GCC distributors: why UAE and Saudi businesses are replacing Excel with industry-specific systems

Distribution businesses across the UAE, Saudi Arabia, Qatar, and Kuwait have grown quickly, and a large number of them are still running on spreadsheets that were entirely adequate five years ago.

Excel does not fail loudly. It degrades. The point at which it stops being sufficient passes without an incident, and the business usually discovers it retrospectively: during an audit, a funding round, or a recall.

The four thresholds

We see the same four triggers, and it is usually two or three of them together rather than any single one.

Volume. Somewhere around the point where order lines exceed what one person can hold in view, reconciliation stops being a task and becomes a permanent condition. Someone is always fixing last week.

Multi-entity operation. Trading across the UAE and Saudi Arabia, or through a free zone entity and a mainland entity, multiplies the reconciliation rather than adding to it. Stock in one system, invoices in another, intercompany positions maintained by hand.

Compliance. ZATCA e-invoicing in Saudi Arabia and the UAE’s corporate tax regime both assume structured records generated by a system. Both are survivable in Excel, at increasing cost and increasing risk, and both have a phase-in schedule that removes the option eventually.

Investor or principal scrutiny. This is the one that usually forces the decision. A distributor bidding for a principal appointment, or raising capital, is asked to evidence inventory accuracy, margin by line, and traceability. “We can pull that together” is a different answer from showing it on screen, and the difference decides appointments.

Why industry-specific outperforms generic here

The instinct at this stage is to buy a large, well-known generic ERP. It is a defensible instinct and it is often the wrong one for a mid-size distributor, for a reason that is specific to how these implementations are priced.

A generic ERP arrives as a framework. Everything that makes it a distribution system, including batch and expiry handling, landed cost across import documentation, consignment stock, principal-wise reporting, and multi-currency against a pegged and an unpegged currency in the same group, is configured during implementation, by consultants, at day rates, over six to eighteen months.

You are paying for that configuration. So did the distributor before you, for the same thing, and none of it accrued to the product.

An industry-specific platform has those behaviours built in because it has no other market. Deployment becomes migration and training rather than discovery and construction. In our own deployments that is the difference between thirty days and a year, and the cost difference is larger than the timeline difference.

The trade is real and worth stating: an industry platform will not accommodate a genuinely unusual business model. If your operation does not resemble distribution as practised, you want the generic framework and the long implementation, and you want a vendor who says so.

What GCC distributors specifically need that generic systems handle badly

Arabic and English at parity. Not a translation layer. Invoices, reports, and interface, both directions, correctly rendered, including in printed documents, which is where most systems quietly fail.

Landed cost across import documentation. Freight, insurance, customs, and clearing allocated across a shipment down to line level. Distributors doing this in a spreadsheet are typically applying an average, which means product-level margin is wrong in a way that favours the wrong products.

Consignment and principal reporting. Stock held on behalf of a principal, reported in the principal’s format, on the principal’s cycle. This is contractual, it varies by principal, and it consumes an extraordinary amount of manual effort in most operations.

Free zone and mainland entity separation. Distinct entities with distinct compliance obligations, intercompany movements, and consolidated reporting on top.

Expiry-driven picking. For pharmaceutical and food distribution, first-expiry-first-out as a constraint rather than a report. This is the single largest recoverable loss in most of the operations we assess.

Sequencing the move

Do not attempt everything at once. The order that works:

Inventory and purchasing first, because that is where the money is and where the data quality problems will surface. Sales and invoicing second, aligned to whichever e-invoicing obligation applies to you. Finance integration third. Reporting and analytics last, once there is a quarter of trustworthy data to report on.

Attempting finance first is the most common sequencing error, and it fails because finance is downstream of the operational data that has not been cleaned yet.

The part nobody budgets for

Data cleaning.

Whatever exists in the spreadsheets contains duplicates, inconsistent product codes, customers entered three different ways, and quantities in units where the warehouse counts cartons. Migrating it accurately means migrating those problems accurately.

Clean it as a separate, priced, scheduled piece of work before migration begins. Every implementation that overruns, in our experience and everyone else’s, overran here.