The most-used page on a logistics website is the tracking box, and it is usually the worst one
Most traffic to a logistics site is not new business. It is existing customers checking where something is, which makes tracking the most-used feature and usually the least cared for. The other half of the work is quoting, where price depends on route, weight, volume and service level.
A logistics website serves two populations that barely overlap. The first is customers who have already bought and want to know where their consignment is, several times a day, usually from a phone. The second is a prospect comparing carriers on coverage, price and reliability. The first group produces the traffic. The second produces the revenue, and is handed a contact form.
A freight company commissions a new website and treats tracking as a technical detail. It ships as a small box that throws the visitor out to a third-party page with different branding, no phone layout and a reference number that has to be typed exactly right. Customers visit that page again and again, and every visit is a reminder that the company is awkward to deal with. The quote request, meanwhile, is a message box, so every enquiry still needs a call before anybody can price it.
When this work makes sense
Questions worth asking any supplier
How will tracking behave on a phone, because it is the page existing customers see most often and it shapes whether they renew.
Can a usable quote be produced without a telephone call, because price depends on route, weight, volume and service level, and a message box collects none of those.
Which operational systems will the site read from, because a website that cannot see the TMS or WMS will always describe a business it is not connected to.
Are contract and one-off customers given different paths, because a manufacturer awarding a year of freight and a family moving house share nothing but a word.
How are coverage areas described, because a list of city names is not coverage, and a customer shipping somewhere wants to know what happens at that end.
Deliverables
Tracking built as a first-class page, fast and mobile-first, linkable, and tolerant of how references get typed
A quote tool collecting route, weight, dimensions, service level and special handling, returning something usable
Separate paths for contract business and one-off customers, with pricing, language and evidence suited to each
Integration with the systems that run the operation, so the site reflects the business instead of restating it
Coverage content describing what you do at each end, including modes, transit expectations and handover
Credibility material for somebody handing over goods, covering handling, documentation and what happens when things go wrong
Enquiry routing by consignment type and value, so a container programme and a single pallet do not queue together
Built with
Process
A logistics engagement starts with the systems rather than the site. We establish what your TMS, WMS or courier platform can expose, how a reference number reaches a customer, and how a quotation is genuinely produced today, including the parts done in somebody's head. That ordering matters because the two things this site lives or dies on, tracking and quoting, are integration problems before they are design ones. Design first and you end up with a handsome quote form that still ends in a telephone call.
The standard nine stages, discovery, strategy, UX/UI, development, content and SEO, testing, launch, measurement and continuous improvement, apply to every project. The paragraph above is what differs for this one.
What moves the number
Pricing depends on scope, functionality, integrations and content requirements. These are the factors that change it most:
Three ways to handle tracking on your site
Link out to the carrier or platform's own page
Fits: Small operators reselling somebody else's network with no development capacity
Limits: Your most-visited moment happens somewhere you do not control, and it flags who really carries the goods
Embed the provider's tracking widget
Fits: Operators who need something working quickly and can live with the widget
Limits: It rarely matches your site on a phone, and you inherit its speed, wording and error messages
Read the status feed and render tracking yourself
Fits: Operators who treat tracking as a retention tool rather than a utility
Limits: A real build with ongoing maintenance, and it fails visibly when the upstream feed does
Case studies
Nothing is published yet for this sector. There are no client case studies, no named operators, no consignment or enquiry figures and no ranking data, because we have neither permission to use them nor numbers anybody outside could verify. When a client agrees to be named, it will be published here.
MBGDesk operates from 4 offices in India, United States, United Kingdom, United Arab Emirates. We hold no industry certifications and do not imply otherwise.
Frequently asked questions
Why does tracking matter so much when those visitors have already bought?
Because logistics is a repeat purchase and tracking is where the relationship is actually experienced. A customer may deal with your salesperson twice a year and your tracking page twice a day. If that page is slow, badly laid out or hosted somewhere that looks nothing like you, it builds the case for switching.
Can we really quote online when every job is different?
Usually you can quote most of it, which is the part that matters. Standard lanes, common weights and familiar service levels can be priced or given an indicative range, while anything unusual routes to a person with the details already collected. Aiming to price every possible consignment guarantees nothing ever gets built.
Should contract and one-off customers share a website?
One site, two clearly separate paths. A procurement team awarding contract freight wants coverage, systems, compliance, references and account terms. A household moving across the country wants a price, a date and reassurance that their belongings are safe. Written together, the copy hedges so much that neither reader is convinced.
What convinces someone to hand over their goods to us?
Specifics about handling rather than adjectives about care. Who packs, what equipment is used, how items are documented, what tracking they receive and how claims are handled. What you may state about insurance cover, liability limits or licensing is a matter for your own legal and insurance adviser rather than for us.
How should coverage areas be written?
As descriptions of service rather than lists of names. For each place you genuinely serve, a reader wants to know what you run there, how often, what modes are available and who handles the final leg. A page naming many cities with nothing behind it reads as a claim rather than evidence.
Our operational systems are old and hard to integrate. What then?
You decide what is worth reaching for rather than abandoning the idea. Often a scheduled export of status data is enough to render tracking well, even when live access is impossible. Sometimes a small service sits between the old system and the website. Occasionally the honest answer is that a feature is not worth the cost.
Do we need a customer portal?
Only if contract customers are asking your staff for the same things repeatedly. Portals earn their keep when they remove real work, such as documentation, proof of delivery, consignment history and invoices. Built speculatively they attract very little use and a lot of maintenance. Look at what operations emails out weekly.
Services that connect to this
Talk to us about this
Tell us what you are trying to build and we will come back with scope, approach and an estimate.