A cargo
operations stack
for a German haulier.
Behind Rosy Logistik's public website sits the operations app we built for them — order intake, fleet dispatch, end-to-end shipment tracking, contract-logistics workflows, and customer quote requests, in German + English.
/01 THE BRIEF
Rosy ran their cargo operation on phone calls and forwarded emails. They wanted a single platform — for the dispatchers, the drivers, and the customers requesting quotes — that spoke German and integrated with their existing ERP.
We delivered the public marketing site, the customer-facing quote-request flow, and the internal operations console — a single Laravel app, two surfaces, one shared database.
/02 THE APPROACH
We started from the dispatcher's screen — the busiest, most error-prone surface in the operation — and built outward.
A unified order pipeline ties customer requests, dispatcher allocations, and driver status into a single view. The marketing site shares its design language with the internal console so customers and ops staff feel like they're on the same product.
We finally retired the WhatsApp dispatch group. Sleep returned.
A consistent visual voice across every surface.
Engagement, in four movements.
Sat in the dispatch office for a week. Documented every interruption.
Public site, customer portal, dispatcher console — single codebase, role-based views.
ERP integration, route planning, driver mobile capture.
Quarterly improvements driven by dispatcher feedback.
Built on opinionated infrastructure.
Have a brief like Rosy's?
We'll reply within one working day.
Start a project ↗