Name the parties
Record shipper, consignee, forwarder, broker, carrier and customer references.
Workflow blueprint
A Mauritius forwarding file needs a clear boundary between uploaded documents and decisions made by carriers or authorities
A page-specific review aid, not a universal product or compliance claim.
Keep local shipment messages, package details, commercial documents and unresolved customs or delivery questions in one dated handoff file.
TL;DR — Keep local shipment messages, package details, commercial documents and unresolved customs or delivery questions in one dated handoff file.
Build the file
Attach package, document edition, booking request, message channel and response clock.
Open the exception
Separate customs, payment, cargo, insurance, warehouse and delivery questions.
Assign the next step
Name the party expected to answer and the evidence still missing.
Page-specific decision aid
Mauritius forwarding handoff file
A shipment party, package, document edition, booking change, carrier response, authority question, customer notice and next-owner field.
- ✓Party responsibilities stay distinct
- ✓Upload is not clearance
- ✓A delay retains its response source
Scope first
What Codeblix would confirm before implementation
This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.
- ✓Party and shipment identity
- ✓Package and document lineage
- ✓Response and exception history
- ✓Named local operations owner
Relevant Codeblix foundations
Review the existing product areas that support the proposed workflow.
Use the related planning tools
Run the operational calculation, save the result in the URL and share it with your team.
Map this workflow to your operation
Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.
Discuss your workflow