Case Zuco Logistics
A platform of its own, live in one afternoon
Zuco Logistics got the DA Logistics platform, with its own branding, its own server and its own fuel model.
Example with demo data
- Sector
- Transport, second client on the platform
- Languages
- NL
- Live since
- September 2026
Monday 14 September 2026
A new domain, a live platform 57 minutes later.
Zuco Logistics got the same platform as DA Logistics, with its own branding, its own server and its own database. This is how the afternoon went.
15:28
Domain registered
zucologistics.be, with DNS through our own AWS setup.
15:37
Certificate active
HTTPS on the domain.
16:25
App and API live
The platform in Zuco's branding, with a first backup.
15 September. A day later: fuel the way Zuco buys it, with purchases, FIFO and an excise export.
Three fuel models on one core
Every haulage company refuels differently. The platform follows the business, not the other way round. The screens are examples with demo data.
Own tank
Deliveries into the company's own tank, FIFO per delivery and Kader B with a report for customs. That is how DA Logistics works.
Depot
Litres bought in advance from a supplier, with an invoice. FIFO from purchase to refuel and an excise screen with export. That is how Zuco works.
Fuel card
Every refuel with litres, amount and a photo of the receipt. Ready for the next client.
Custom work for one client became a product for many.
Zuco does not refuel from a tank of its own. It buys litres in advance from a supplier and draws them down later. That calls for different fuel accounting, with purchases, invoices and an excise screen for customs, but otherwise the same planning board, the same fleet and the same driver app.
The platform we built for DA Logistics was full of choices that only applied to that company: the names, the tank, the number plates. Putting a second haulage company on it meant first separating the core from the client.
We did that thoroughly. The core no longer contains any client names, every client gets a profile with its branding, modules and language, and runs on its own server with its own database. Adding a haulage company is a profile, not a new project. Zuco was the first to go live this way. A day later, DA Logistics moved onto the same core too.
What Zuco got
- Own branding: Zuco's logo, colours and name, so drivers and office work in a platform of their own.
- Own data: a dedicated server and database, separate from every other client, with a backup every day.
- Shielded: the platform cannot be reached directly from the internet, only through a secured entrance.
- New versions without the drivers noticing, with a backup first and a way back.
The same planning in a profile of its own.
Zuco works with the same planning board, the same routes and the same driver app as DA Logistics. What differs sits in a profile of its own: the branding, the modules and the language.
You drag a driver onto a route, and add a temporary route for a week.
Also a haulage company?
Tell us how you refuel, plan and report. You hear back within 24 hours, with a proposal for a first call.
Rather get in touch right away?