Portfolio Cargo Consolidator
Client cargo from declaration to truck — without “where is my cargo” calls
A system for a consolidation company: clients declare cargo and attach documents in their own cabinet, the warehouse takes it from expected to loaded, and the client hears about every step by email or Telegram — in their own language.
Project
Cargo Consolidator
- Client
- A consolidation company with its own warehouses It receives cargo from many clients — by courier, by truck, from other warehouses — and ships it out on consolidated runs.
- System
- Cargo, warehouse and trip records with a client cabinet Two panels: managers handle all cargo, clients see only their own — declarations, documents, statuses and messages.
- Our role
- Process analysis from the brief, design, interface and back end Plus notifications, reports, roles and access rights, testing, deployment and support.
- Technologies
-
- PHP
- Laravel
- Filament
- Livewire
- MariaDB
- Redis
- Control
- A change history for every cargo You can see who changed a declaration, documents, warehouse or trip and when — and what the client was shown.
Task
Many clients, cargo in parts, no overview
Cargo arrived from different sources, sat in several warehouses and left in parts on different trucks. Documents came by email and messengers, and clients asked every day where their cargo was and whether it had left.
A declaration with documents
The client should describe the cargo, where it comes from and where it goes, and attach the papers — and a customs plan cannot be accepted without them.
Cargo travels in parts
One consignment can leave on several trucks. Records must be in kilograms and cubic metres, not rows, and show how much is still on the shelf.
Deadlines running out
Customs document validity, free storage at the warehouse and the latest shipping date are three different dates, and none can be missed.
The client knows by themselves
Every client should learn about their cargo without calling a manager — and in their own language, not the office’s.
Solution
One cargo path for the warehouse and the client
A cabinet instead of email threads
The client creates a declaration, picks the source and plan from lists, attaches documents, and after submitting can still change the plan and add files — until the cargo is put on a trip. Every change from either side is written into the cargo’s thread.
The warehouse counts kilograms and cubes
A manager receives cargo with its actual weight and volume and splits it across trips. The system shows what remains on the shelf and derives the cargo’s status from its least advanced part.
Notifications at every stage
Accepted, documents submitted, at the warehouse, departed, arrived — the client gets an email or a Telegram message in their language, and a new declaration lands in the managers’ work chat at once.
Capabilities
Warehouse, trips and the client cabinet
01 · 4
Cargo
- Declarations by clients and by managers
- Lists of sources, plans and warehouses
- Documents travelling with the cargo and customs documents
- Warehouse photos of the cargo and a message thread
02 · 4
Warehouse and trips
- Receipt with actual weight and volume
- Trips with cargo split into parts
- Stock on the shelf in kilograms and cubic metres
- Arrival time entered by the manager
03 · 4
Deadlines
- T1/EX customs document validity
- End of free storage
- Latest shipping date
- Colour marks in tables and on the dashboard
04 · 5
Clients and control
- Several logins per client and several clients per login
- Email and Telegram — each user chooses
- Four interface languages
- Reports by period, client and trip
- Change history of every record
Result
Every cargo is visible — to the warehouse and to the client
Declarations arrive with their documents, the manager sees on the dashboard how much cargo is at each stage and which deadlines are close, and trips are built from what is actually on the shelf.
Clients learn about their cargo by themselves — by email or Telegram, in their own language — so “where is my cargo” no longer eats the working day.