From rate enquiry
to confirmed delivery.

A logistics website should explain what the operator moves and where. Maps support readable route information rather than replacing it. Complex cargo needs clear packaging requirements and enquiry fields. In the portal, a meaningful exception and responsible contact matter more than decorative moving vehicles.

During design, document representative screens and expected user actions. For each decision, identify what editors maintain, what comes from another system and who owns its freshness.

Acceptance check: A first-time mobile visitor can find the relevant service and next step.

The workflow connects these stages: Cargo details → Choose capacity → Validate constraints → Send to dispatcher. Each transition has an owner, inputs and a visible result. Before implementation, map the normal journey, correction, cancellation and repeated actions. Interface status must represent a confirmed state rather than a button click.

Acceptance check: Returns and retries preserve input without duplicating the result.

A request connects sender, recipient, stops, packages, weight, volume and delivery window. Validate weight and volume independently: free space does not imply sufficient payload capacity. Keep planned and actual events separate. Display agreed time zones and preserve route revision history.

Acceptance check: Reference data changes do not overwrite an agreed document.

Customers see their own shipments and permitted documents. Dispatchers allocate resources; drivers or subcontractors report events for assigned work. An address change after confirmation requires dispatcher review. Customer-facing status need not reveal internal notes, subcontractor costs or other customers in a consolidated load.

Acceptance check: A different organisation cannot retrieve a restricted file by direct URL.

Status may come from transport or warehouse systems, positions from an agreed tracking service and documents from accounting. Record source and time for each event. When data is delayed, show the last update time; repeated events do not create additional deliveries.

Acceptance check: An unavailable source never appears as a confirmed success.

For long operations, acknowledge receipt and retain the result identifier. Retrying after a connection loss must not create a second record. Separate user-correctable errors from cases requiring a specialist, preserving input under the agreed handling rules. Design empty, loading, forbidden and unavailable states before implementation rather than after launch.

Acceptance check: A repeated event does not apply an operation twice.

Build navigation around routes, transport services, cargo types and warehouses. Forms request parameters needed for quotation rather than relying on an empty description box. Separate estimated rates from confirmed offers. Connect acquisition data to enquiry quality and handling outcomes, not just button clicks.

Acceptance check: Search and filters lead to useful pages without endless duplicates.

The first release covers the complete journey from “Cargo details” to “Send to dispatcher”, supporting pages and editable fields. Test mobile views, roles, forms, documents and integration failures in staging. Save the previous state and define rollback before switching. Handover includes editor instructions, the exchange design and a checklist for future releases.

Acceptance check: Recovery has been tested on a copy, and editors can maintain fields independently.