Shipment tracking, customer portals and quote forms, what UAE logistics companies should build first

Home / Blog / What logistics companies should build first

Most logistics website briefs we receive in Dubai arrive in the opposite order. The brief opens with a customer portal, moves to live tracking, and treats the enquiry form as a detail to be finalised later. That sequence spends the budget on the features that take longest to build and produce the fewest enquiries. This article explains the order we recommend instead, what each feature actually involves technically, and how to decide what your business genuinely needs. If you already know what you want built, our logistics web development team can scope it directly.

What logistics buyers actually do on your website

Before deciding what to build, it helps to be honest about why anyone visits a logistics website at all. In our experience there are five reasons, and they are not equally valuable.

1. To check whether you cover their route or service. The first question is always eligibility: do you move this type of cargo, from here to there, at this scale.
2. To request a quote or a rate. The commercial action, and the reason the website exists.
3. To track a shipment they already booked. High volume, low commercial value, high service value.
4. To verify you are credible. Licence, certifications, facilities, years in operation, who else you work with. This matters most to procurement teams.
5. To find a phone number. Still, in 2026, a meaningful share of visits.

Notice that only one of those five produces revenue directly, and it is the one that usually gets the least design attention. Notice also that the most common visit, tracking, is a service interaction rather than a sales one. Build for both, but do not confuse volume with value.

Start with the quote request, not the tracking page

A logistics quote form has a harder job than a normal contact form, because a useful quote needs specifics and every extra field costs you submissions. The way through that tension is to ask only what determines whether you can quote at all, then collect the rest in the conversation.

What belongs on the form: service type, origin and destination, cargo type, approximate weight or volume, timing, and contact details. What does not belong: full dimensions of every carton, HS codes, incoterms, or a message box doing the work the fields should do. Those turn a two-minute enquiry into an abandoned one.

Four details separate a quote form that works from one that leaks enquiries:

• Route eligibility stated before the form. If you do not move cargo to a destination, say so on the page rather than letting someone fill in a form you will have to decline.
• Different paths for different cargo. A full container, an air freight pallet and a household relocation are different conversations. One generic form serves none of them well.
• A stated response expectation. Telling someone when they will hear back measurably reduces abandonment, and it costs nothing to add.
• Delivery that actually works. Test the form from a phone on mobile data and confirm it reaches a named inbox or your CRM, not a shared address nobody watches. Silent form failure is the most common problem we find on logistics sites.

Shipment tracking, the four ways it actually works

This is where logistics website budgets get misjudged in both directions. Some companies assume tracking is a simple page and discover it needs a system integration. Others assume it is a six-figure project and never build it. The truth is that there are four distinct approaches with very different effort levels, and most UAE operators need one of the first two.

Two things worth saying plainly. First, for many Dubai freight forwarders the right answer is the carrier API lookup, not a full system integration, and anyone quoting the latter without asking which carriers you use has not scoped the job. Second, the fourth option is not a compromise for a business moving twelve project shipments a month. It is the correct answer, and it costs a fraction of the alternatives.

Where tracking does need carrier connections, that is the same work as our shipping API integration service, and where it needs to read from your own systems it overlaps with ERP integration.

Customer portals, and when they earn their cost

A customer portal is the most requested and least used feature in logistics web development. Built well for the right business it removes a large share of routine email. Built for the wrong business it becomes an expensive login screen nobody visits.

The test is simple and worth applying honestly before you brief anyone. Can you name at least ten customers who would log in every week, and say what they would do once inside. If the answer is vague, you need better self-service on the public site rather than a portal.

Where a portal does earn its place, these are the functions that get used: shipment history and current status across all their consignments, documents such as bills of lading, delivery notes, invoices and customs paperwork, repeat booking from a previous shipment, rate visibility for contracted customers, multiple users under one company account with different permissions, and statements or outstanding balances.

That last point about users matters more than it sounds. A corporate customer is not one person. It is a logistics coordinator who books, a finance person who needs invoices, and a manager who wants visibility. A portal with one login per company gets shared, which creates exactly the access problem it was meant to solve. This is the same company-and-users structure we build in B2B portal development, and the authenticated side of it sits with our web application development team.

Discuss whether a portal is worth it for you B2B portal development

What integration actually involves

Every logistics website project eventually meets the systems the business already runs, and this is where timelines slip. Three questions decide whether an integration holds up, and they should be answered in writing before any code is written.

• Which system owns each field. If both your website and your TMS believe they own shipment status, you will have two versions of the truth and a customer looking at the wrong one. Name one owner per field.
• What happens when a message fails. Does it retry, where is it logged, and who finds out. An integration without defined error handling works perfectly until the day it matters.
• What the system can actually expose. Some TMS and accounting platforms have a documented API. Some have a scheduled export. Some have neither, and the honest answer is a different approach rather than a longer project.

Common connections on a UAE logistics build include TMS and WMS for shipment and warehouse data, accounting or ERP for invoices and statements, CRM so enquiries reach a named owner, carrier and shipping line APIs for tracking, maps and location services for coverage and route display, and payment gateways where customers settle online.

Build priority by logistics segment

The right first build differs by what you actually move. These are the priorities we would recommend, and the feature we would deliberately defer in each case.

The pattern across every row is the same. Information that proves you can do the job, then the commercial action, then the service features. Our logistics web development page covers the full scope of what each of these involves.

Five mistakes that cost logistics companies enquiries

1. Coverage is not stated anywhere. A visitor cannot tell whether you serve their route, so they leave rather than ask. Publish your trade lanes, service areas and cargo types in text, not in a brochure.
2. The capability is locked in a PDF. A company profile download is not a website. If your services, certifications and facilities only exist inside a PDF, search engines and buyers both struggle, which is the problem our B2B SEO work usually starts with.
3. No tracking entry point on the home page. Returning customers hunting for a tracking box generate support calls and a poor impression, and it is a half-day fix.
4. One generic contact form for everything. A quote request, a tracking question and a job application all land in one inbox, and the quote waits behind the other two.
5. Nobody owns the enquiry. The form works, the email arrives, and it sits because it reaches a shared address rather than a named person or a CRM record with an owner.

Get these five checked on your site Web development services

A phased build plan that does not stall

Logistics website projects fail more often from scope than from execution. Phasing keeps the site earning while the complicated parts are built properly.

• Phase one, get found and get enquiries. Service and trade lane pages, coverage and cargo types stated clearly, credibility content, segmented quote forms with delivery tested, tracking entry point even if it redirects to carriers, mobile and Arabic where relevant.
• Phase two, reduce the support load. Branded tracking through carrier APIs or your own system, document access, booking or repeat booking where the business supports it, CRM routing so every enquiry has an owner.
• Phase three, serve contracted customers. Customer portal with company accounts and multiple users, invoices and statements, contracted rate visibility, deeper TMS or ERP integration, mobile app if drivers or customers genuinely need one.

Most UAE operators get more commercial value from doing phase one properly than from a half-finished phase three, and that is the single most useful judgement in this article.

Frequently asked questions