How to Choose a TMS for a Road Freight Operation in MENA: Five Questions to Ask

There are dozens of TMS platforms on the market. Most were built for European or North American freight markets, then adapted — sometimes loosely — for operators in the Middle East and North Africa. The pitch looks the same. The screenshots look similar. The pricing is in the same ballpark. But the platform that works for a German freight broker is not necessarily the platform that works for a Jordanian trucking company running twelve vehicles between Amman and Riyadh.

The questions below are not about features. They are about fit — whether the platform was actually designed for how road freight operates in MENA, or whether you would be spending the first year working around the gaps.

1. Does It Work in Arabic, French, and English?

This is not a nice-to-have. For any MENA road freight operation, it is a structural requirement.

Your drivers may not be comfortable operating in English. Your dispatchers might work in Arabic or French depending on the country. Your client-facing documents — invoices, delivery notes, shipment notifications — need to reflect the language your clients work in. A platform that forces all user interfaces into English, or that supports Arabic as a secondary skin without real RTL (right-to-left) layout, will create friction every day.

RTL support is not the same as language support. A platform that translates its labels into Arabic but keeps the layout left-to-right is uncomfortable to use for an Arabic-speaking team. True RTL means the entire interface — menus, forms, tables, document layouts — reflows correctly for right-to-left reading. Ask the vendor to show you the driver app in Arabic and the invoice module in French before you sign anything.

If a platform only supports English, that is a red flag for MENA operations. It means the platform was not designed with your market in mind, and that gap will show up in other places too.

2. Can It Handle Your Invoicing Compliance?

VAT rules across MENA are not uniform, and getting them wrong costs money.

Saudi Arabia applies 15% VAT on freight services. Jordan applies 16%. Morocco's standard rate is 20%, with specific exemptions that apply to international transport. UAE has its own VAT treatment. A platform that handles VAT correctly for one of these markets may handle it incorrectly — or not at all — for another.

The question to ask is not "does it support VAT?" The question is: does it pre-fill the correct VAT rate based on the transaction's origin and destination country, the service type, and the applicable exemptions? Or does it require your accounts team to manually enter tax parameters for every invoice, which is both slow and error-prone?

Good invoicing compliance means the platform knows your operating jurisdiction, pre-applies the rules, and produces a document that an auditor or client accountant can accept without follow-up questions. This is especially relevant if you operate across multiple MENA countries — you should not need a different invoicing workflow for every border you cross.

3. How Long Does Setup Actually Take?

This is where the gap between the sales conversation and reality is largest.

Many TMS vendors will describe implementation timelines of "a few weeks" in the sales meeting. What they mean by implementation is often: software configuration, data migration, custom integrations with your existing systems, and a training programme for your team. Each of those steps adds time and cost.

A platform that requires an "implementation partner" — a third-party consultancy that charges separately for deployment — is a red flag for complexity. It means the product is not designed to be used directly by an operator; it is designed to be deployed by a specialist. For a trucking company running ten to fifty trucks, this level of complexity is rarely justified.

A well-designed TMS for a MENA road freight operator should be live in days, not months. Your core operations — dispatch, driver assignment, trip tracking, POD capture, invoicing — should be functional within your first week. If the vendor cannot commit to that timeline, ask why not.

4. Does It Include Driver and Fleet Management, or Is That a Separate Product?

This is a gap that catches many operators by surprise after they have already signed.

A TMS handles the commercial and operational side: trip creation, load assignment, client communication, invoicing. But running a fleet also involves managing your drivers — tracking their hours, managing their licences and document renewals, calculating their payouts based on trips completed — and managing your vehicles — maintenance schedules, fuel tracking, tyre rotations, insurance renewals.

If the TMS you are evaluating covers only the transport management side, you will be back in Excel for fleet and driver management within a month of going live. That means two systems, two data sources, and the manual reconciliation between them that you were probably trying to get away from.

Ask specifically: is driver pay calculation included? Is fleet maintenance scheduling in the platform? Is fuel tracking built in or a third-party add-on? The answers will tell you how complete the solution actually is.

5. What Does Support Look Like After Go-Live?

The demo is not representative of day-to-day use. The test environment is not representative of a crisis at 02:00 when a driver is stranded and a dispatcher cannot figure out how to reassign the load.

Support quality is one of the most important and least-discussed factors in TMS selection. An async ticket system that promises a response within 24 hours does not work for a freight operation. Dispatch problems are time-sensitive. System errors do not wait for business hours.

Ask the vendor directly: if one of my dispatchers has a problem at 02:00 on a Friday night, what happens? Can they reach someone? How quickly? The honest answer will tell you more about the vendor's support model than any SLA document will.

WhatsApp-reachable support — direct messaging to a real person who knows the product — is not a low-cost workaround. For MENA freight operations, it is the appropriate channel. If a vendor finds this expectation unusual, they have not spent much time understanding how MENA freight teams actually work.

Picking on Price Alone

It is tempting to compare TMS platforms on subscription cost. But the subscription cost is rarely the largest financial variable.

The cost of a platform that delays your invoicing by two extra days per trip — across thirty trips per week — is a working capital cost that dwarfs most SaaS subscription fees. The cost of a platform that requires a complex setup phase of three months means three months of parallel operation: paying for the TMS and still doing manual work. The cost of a platform that does not support Arabic properly is measured in daily friction, errors, and the eventual cost of switching again.

Total fit — language, compliance, setup time, completeness, support — is what determines whether a platform pays for itself or costs you more than it saves.

---

Choosing a TMS is a decision you will live with for years. The questions above will not pick the platform for you, but they will quickly separate the platforms built for your market from the ones that merely claim to be. The difference is usually visible within the first thirty minutes of a proper product walkthrough.