An import workspace should make the next action clear: what is arriving, which records are available and who is handling the next step?
Start with one shipment record
We recommend a shared record containing your internal reference, supplier, receiving customer, transport reference and expected arrival. Link the relevant files to that record rather than leaving the context spread across multiple email threads.
Separate documents from milestones
Document readiness and physical movement are different kinds of updates. Keep a document checklist beside the shipment timeline so your team can see both. DHL explains that a customs invoice is used to declare information for clearance. The records needed for a specific shipment depend on its route and goods; agree the checklist with the responsible carrier or broker.
Use a workflow that reflects your operation
- Create the incoming shipment record.
- Assign the responsible team and record expected arrival.
- Attach supporting document references and note pending items.
- Record arrival and subsequent handover updates.
- Prepare the final delivery note and connect delivery evidence.
Give customers the right visibility
A customer page can show the agreed milestones, delivery documents and outstanding actions. Internal notes and team assignments can remain in the operations view. These are proposed portal features, configured as part of your project scope.
Further reading: DHL: international shipping documents ↗
Built around your workflow.
Tell us how your team handles shipments today. We’ll help scope a portal for your delivery notes, updates and customer access.
Discuss your logistics portal