The yard and transport
Yard management
Vehicle statuses and slots on the warehouse grounds are visible in real time.
Home · Case studies · Logistics
Case study · Logistics, end-to-end process
From truck arrival to warehouse departure — in one process
Instead of a legacy corporate system — a platform that connects transport, the yard, cargo and documents. Statuses and slots are visible in real time.
8steps from arrival to departure
4connected services
SSCCreconciliation at pallet level
Legacy →New platform architecture
001
Why the legacy system could no longer keep up
The legacy corporate system kept operations siloed: transport, the yard, cargo and documents each lived in their own loop.
01
Siloed operations
Transport, the warehouse and documents were not linked into a single process.
02
Manual steps at the handoffs
Passing information between stages required manual work and phone calls.
03
Opaque cargo movement
The status of transport and cargo was hard to track in real time.
We designed a new architecture, rewrote the key business services, and migrated to PostgreSQL with a phased rollout of operational processes — without stopping the warehouse.
Solution
Eight steps — one connected process
From the trip plan to warehouse departure — the platform connects transport, the yard, cargo and documents into a single process.
TMS · trip plan
→
Vehicle arrival
→
YMS · yard
→
Queue and loading zone
→
Loading / unloading
→
Scan · pallet reconciliation
→
Docs · documents
→
Vehicle departure
A trip registry: status, slot, carrier and actions right in the row — call to the gate, start loading, check orders.
Specifics
Not a single service, but a connected system
Pallet and cargo reconciliation
SSCC scanning
Full traceability: it’s visible who scanned which code, and when.
Tariff files in the TMS
Trip tariffing
Carrier tariff terms are connected directly to the trip plan in the TMS.
A document catalog and search
Document workflow
Documents for the trip and cargo — in a single catalog with fast search.
In the interface
Discrepancies are logged, not lost
In the warehouse, the interface is built for operator speed rather than looks: plan, actual and remaining box count on one screen, SSCC reconciliation, and a separate button for closing with discrepancies — rather than a silent after-the-fact correction.
udev.tech · Logistics · Trip registry
On one screen
Plan, actual and remaining box count
SSCC reconciliation
Pallet-level accuracy
Operations log
Time to the second, employee ID, SSCC
Results
Legacy → new platform
We designed a new architecture, rewrote the key business services, optimized performance, and migrated to PostgreSQL with a phased rollout of operational processes.
Legacy corporate system
New platform architecture
Siloed operations
Interconnected services
Manual steps at the handoffs
Automated operations
Opaque movement of transport and cargo
A fully transparent digital process
Full traceability
Discrepancies are part of the process, not lost data: it’s visible who scanned which code and when, down to the application launch. There is a separate scenario for closing discrepancies, rather than a silent after-the-fact correction.
A connected process instead of siloed operations
The company got a unified platform: transport, the yard, cargo and documents — in one process, with full traceability and transparent statuses.