10 Logistics Website Examples: Quotes and Shipment Tracking
A transport company website has two different purposes: helping a new customer choose a shipment service and helping an existing customer understand their cargo status. A reference collection should cover both journeys. A callback button does not answer someone who already has a shipment number.
This article reviews ten delivery, freight forwarding and logistics websites checked on 8 October 2026. We examine public entry points to quotes, tracking and services. It is a set of design references, without carrier rankings or conversion promises. International operators and regional carriers have different scales; borrow the journey that fits your business.
For a general visual brief, see our corporate website collection. The focus here is an industry workflow: identify a shipment service, provide cargo details and retain access to an order after dispatch.
What we compare across carriers
| Carrier website criterion | What the visitor needs |
|---|---|
| Service selection | Distinguish parcels, groupage, a dedicated vehicle and other available services |
| Pricing | Understand which path calculates a rate and which requests a specialist’s quote |
| Tracking | Find an entry accepting the correct shipment identifier |
| Customer help | Find locations, documents, restrictions and the appropriate contact |
| Returning visitors | Return to an order or the relevant account portal |
We reviewed labels and structure on the listed source pages. We did not test calculations for real cargo, tracking responses, authenticated accounts or companies’ enquiry handling. The review does not establish foreign services’ availability for Russian shippers.
10 examples: from a new enquiry to an existing order
1. DHL — tracking and pricing as separate actions
On DHL’s US page , the entries identify shipment tracking, service selection, a quote request and a business account. Documents and parcels, business shipments and freight logistics have separate directions. Visitors get several clear ways to start.
Separate “I want to ship” from “I have already shipped”. Tracking accepts an identifier; pricing takes shipment parameters. Explain whether the output is an estimate, an individual rate or a specialist conversation. Do not transplant DHL’s international rates or coverage into your product.
Brief requirement: two independent entry points with an unambiguous purpose for each action.
2. UPS — useful actions after dispatch
UPS highlights shipping and tracking, along with delivery management, My Choice and billing journeys. It is a useful reference for returning visitors: the shipment purchase is complete, but work with the order continues.
List allowed actions for each stage: view status, request a change, obtain a document or report a problem. Rescheduling or changing an address depends on your actual operating process. Do not show a change button if the dispatch system cannot accept the request.
Brief requirement: order states, available actions and explanations of limitations.
3. FedEx — price, status and locations together
FedEx identifies Rate & Ship, TRACK and LOCATIONS. The tracking field explains which number it needs, while location search starts with a place. Three different questions have their own entry points.
This structure suits a carrier with terminals. A shipper may need a nearby drop-off point before asking for a rate. A branch page needs an address, opening hours, acceptance restrictions and contact details. If services differ at one location, show those differences; a map marker alone does not explain cargo acceptance terms.
Brief requirement: a current location directory and independent pricing and tracking journeys.
4. Maersk — identifiers and routes stay distinct
Maersk labels its tracking field for B/L, container or parcel numbers. B/L means bill of lading, a transport document used in ocean shipping. Separate origin-to-destination and office searches appear alongside it. These actions require different inputs.
A forwarder should name accepted identifiers on its own site. A customer enquiry number, consignment number and container number are not always interchangeable. Explain where to find the required number. Distinguish route search from pricing: a matching route does not itself establish a confirmed rate.
Brief requirement: identifier types and separate route and status journeys.
5. DSV — clear access during system changes
DSV offers quotes, booking and tracking. At review time, it showed separate entries for myDSV users and former DB Schenker Connect users. Visitors choose according to their existing account.
This is useful during a site migration or service merger. Existing customers must understand where their credentials work. Do not replace familiar links with a universal login before verifying account migration. Explain the transition, retain relevant routes and measure login failures after launch. An ordinary site without a migration does not need two portals.
Brief requirement: old and new entry mapping, transition support and access verification.
6. Kuehne+Nagel — pricing starts with transport mode
Kuehne+Nagel offers air, sea and road quote entries, specialist contact, tracking and myKN. Visitors choose a transport mode before moving into the relevant task.
For multimodal logistics, create input sets appropriate to each service. Air freight, container shipping and a dedicated vehicle have different constraints and pricing inputs. A common form can switch relevant fields while retaining entered details. If your company does not provide instant prices, call the action a quote request and explain what a specialist will clarify.
Brief requirement: transport modes, fields for each journey and rules for retaining data when switching.
7. C.H. Robinson — shipper and carrier journeys differ
C.H. Robinson identifies quote requests and tracking alongside a separate load-board entry for carriers. A logistics intermediary serves both the shipping customer and the partner performing the movement.
If your business uses contracted transport, separate shipper and carrier enquiries. They provide different information and enter different processes. Visitors should recognise their role before a long form. There is little reason to build a separate public partner section if all partner work takes place in another system.
Brief requirement: visitor roles and routing for each enquiry type.
8. CEVA Logistics — service boundaries before an enquiry
CEVA Logistics shows Track & trace, Get a Quote and myCEVA. Its contact journey explicitly states that it handles shipments for companies. Services are separated into air, ocean, ground, contract and project logistics.
If a carrier accepts only certain cargo or works only with organisations, explain this before form completion. Clear limits help visitors choose a suitable route and prepare information. Do not hide exclusions in a long document revealed after submission. Terms should reflect actual cargo acceptance policy and change with it.
Brief requirement: eligible customers, accepted cargo types and visible explanations of exclusions.
9. Delovye Linii — quotes and order management
Delovye Linii provides origin and destination fields, a calculation-and-order action and a separate order-number input. Help is segmented for individuals, businesses, manufacturers, online stores, importers and exporters.
A regional carrier can begin with two main audiences rather than many segments. Preserve the route when a quote becomes an enquiry. An existing order needs its own journey without forcing visitors through pricing again. Help should address the segment’s task: cargo acceptance, documents, delivery terms or recurring shipments.
Brief requirement: route retention, order-number access and substantive help sections.
10. PEC — operational actions in navigation
PEC explicitly presents pricing, tracking, payment, documents, questions and a branch map. Its services cover different transport types and warehouse scenarios. Navigation combines starting a shipment with actions for existing cargo.
Use this principle for a short working menu: quote, status, locations, documents and help. A detailed service catalogue can sit alongside it without replacing these tasks. Each document needs a clear purpose and current version. Payment requires verification of order state and payment outcome; a button alone does not complete the process.
Brief requirement: persistent access to operations and outcome checks for each action.
Choose references for your scale
| Website scenario | Useful references | What to include first |
|---|---|---|
| Small carrier serving selected routes | DHL, Delovye Linii | A route-based quote request and clear services |
| Delivery with terminals | FedEx, PEC | Locations, acceptance terms and tracking |
| Forwarding across transport modes | Maersk, Kuehne+Nagel | Mode-specific fields and identifier types |
| Working with contracted carriers | C.H. Robinson | Separate roles and partner enquiries |
| Recurring business customers | UPS, DSV, CEVA | Order access and clear account rules |
Writing requirements for pricing and tracking
First choose what the site can provide: an estimate or an individual quote request. An estimate needs verified rates, surcharges, restrictions and an owner for the rules. A request needs enough information for a manager to prepare an offer. “Get an exact price” is misleading if the result is only an enquiry acknowledgement.
Define minimum inputs: route, cargo type, weight, dimensions, number of packages, requested date and additional services. Fields depend on the shipment type. Make related recalculations explicit when units change or a package is added. Preserve entered details after a submission failure.
For tracking, define the status source, accepted identifier and messages for three situations: shipment found, identifier unknown and data source unavailable. A missing system response must not appear as a missing shipment. If updates are delayed, explain the last update time. Public results should expose only the agreed shipment information.
Acceptance should cover enquiry parameter retention, sales handoff and duplicate prevention after repeated clicks. Our article about website integration with CRMexplains the data handoff. Document pages, data sources and checks using the technical specification template. These materials support a corporate website development based on concrete shipment journeys.
FAQ
Does a small transport company need a calculator?
If stable rate rules cover its main shipments, a calculator may help. If each rate requires manual agreement, start with a short request containing cargo parameters. Explain the output of either option honestly.
Can tracking work without an account portal?
Yes, if a suitable public status and reliable data source exist. Define which details an identifier may reveal and which require authentication. Order history and financial documents need separately agreed access rules.