Selçuk Aker · Web Design

Logistics Web Design: Separating New Offer and Existing Shipment Tracking

Prepare different paths for the customer looking for service on logistics and port sites and the user looking for operational information.

By Selçuk Aker · Published · 3 min read

Logistics Web Design: Separating New Offer and Existing Shipment Tracking — Selçuk Aker

Consider two separate visitors in the logistics company website design: the business asking for a transportation quote for the first time and the customer checking his existing shipment. It may be unnecessary to put both of them through a long company introduction. The main navigation should clearly separate these tasks.

Explain the scope of service clearly

The type of transport, lines served and operating conditions influence the visitor's decision. Explain the limits of that service rather than the same general introduction on every page. A sample partial transportation page can explain which load information is required for the offer and which team the request will reach.

If you use maps, be careful that a decorative world map does not create the impression of a real service network. Show only verified locations and operational information; Determine the update responsible for the changed scope.

Prepare the offer form together with the operation

The operations team must determine which fields such as origin, arrival, load type and dimensions are required for first contact. Requiring information that the user does not yet know may break the application. Explain the units next to the field; for example, do not lump weight and volume into one vague “quantity” field.

Once the form is submitted, it should be understood that the request has been received. Do not present a date or price that has not yet been confirmed as a firm offer. Web design brief makes it easy to define the scope of this flow.

Show the status of data on the tracking screen

Not finding a query result is not the same as a connection error. Incorrect tracking number, unauthorized access, and temporary data outage require different explanations. If the update time is shown, it should be clear which record it really represents. Port announcements and tariffs should also include the validity date and the last update.

These screens and API error states can be planned in UI/UX design work with Selçuk Aker. Development of a live tracking system and data security requires separate expertise and responsibility.

Frequently asked questions

Do every logistics site require live tracking?

It determines the current operating system and customer need. The actual communication and tracking method should be explained rather than a non-functioning query field.

Should port information be publicly available?

The institution must determine which information is public and which is specific to the authorized user. The interface makes this access distinction visible.

Does the quote form have to give an automatic price?

No. Book aggregation and automatic price calculation are different scopes.

Related articles

Have a design project in mind?

Let’s agree on your requirements, deliverables and timeline. Work directly with Selçuk Aker.

Request a design proposal ↗