Those who compare have already made an assumption
When a logistics director starts comparing Cargoclix and Transporeon, they’ve already made a pre-decision: that a time-window portal is the tool they need. That pre-decision is understandable. The providers are visible, the demos run smoothly, and the promises sound precise—booked slots, orderly yard, no congestion at the gate.
What rarely gets asked in that moment: Does a platform actually solve the problem I have?
What time-window portals deliver—and what their business model reveals
Cargoclix, Transporeon and comparable providers function as marketplaces. The model is straightforward: shippers and hauliers book time-windows on a shared platform. Value emerges through network effects—the more hauliers using the platform, the smoother the coordination. Architecturally, it’s cleanly designed.
For large shippers with a diversified carrier portfolio, multiple sites and standardised freight procurement, this model makes sense. Scaling happens across the breadth of the network.
For a mid-market plant handling 80 to 300 deliveries per day—perhaps 30 to 40 established carriers you know by name—the equation is different.
“We introduced the portal, but not everyone books anyway. And those who do still arrive whenever they want.”
This statement, in various forms, appears in countless evaluation conversations. It’s not a criticism. It describes a structural tension between what a platform can do and what a plant actually needs.
The booking fee and what it achieves
One observation from the industry deserves more attention than it typically receives: according to Cargoclix’s own research, haulier acceptance drops noticeably at a booking fee of around 1 euro. This is not a minor detail—it’s a signal of the friction the model creates.
Small hauliers, owner-operators, subcontractors from Eastern Europe: for them, platform registration is not a natural step. They have no fleet management software, no dispatch infrastructure to handle slot bookings. They have a smartphone.
Moreover: in that same study, around 50 % of users reported measuring no real process improvement. This isn’t a criticism of any one platform—it’s a signal that platform rollout alone is not a lever when adoption remains incomplete.
The structural gap: what happens between slot and gate
Let’s say your plant has a functioning time-window system. 60, perhaps 70 % of hauliers book regularly. The slot is locked in. What do you know at the moment the driver sets off in the morning?
Nothing.
A slot is a statement of intent, not real-time information. Between booking—often days earlier—and actual arrival lie 12 to 48 hours with no system in place. The driver is on the road. The subcontracting chain might be three tiers deep. The dispatch call reaches a busy phone or someone who can’t reach the driver themselves.
40 to 70 % of inbound deliveries in the DACH region run on FCA basis—meaning the supplier engages the haulier, the receiver has no contractual link to the carrier and therefore no direct access to the time-window portal. These drivers never appear in the system at all.
What remains is a phone call. Or none at all.
What actually happens in the morning
Picture a typical Tuesday. Plant opens at 06:00. The first drivers are already on site by 05:45—they want to finish early, before motorway traffic builds. By 07:30, around 40 % of all planned daily deliveries have already arrived or are inbound. The docks are occupied. A driver with an 08:00 slot is standing at the gate anyway by 06:55 because their customer sent them earlier. Another who booked 07:00 doesn’t show until 09:30—roadworks on the A3, no one reported it. Your dispatch team has made four calls by now, three without result. The shift supervisor at goods-in is allocating docks by guesswork. This isn’t an exception. It’s the norm.
This morning-peak dynamic—around 40 % of all daily deliveries in the first 90 minutes after plant opening—is not a planning failure. It emerges from driver logic, customer behaviour and traffic patterns. A slot system changes little when real-time ETA information is missing.
Platform vs. control: a category question
This is where comparing two portals stops being the relevant question.
Time-window portals answer: When should the driver arrive?
What mid-market plants actually need is an answer to: When is the driver actually arriving—and can I still intervene before they get here?
This isn’t an incremental improvement of the same tool. It’s a different category entirely.
Control means: you have information at the moment the driver departs. You can react—reschedule a dock, dispatch a forklift, position staff correctly. You can’t make every arrival perfect, but you can stop being completely blind.
Documentation means: you know afterwards what took how long. Yard-management systems and slot portals are, at their core, documentation tools. They’re valuable. They’re necessary. But they don’t control.
What this means for your evaluation
If you’re currently evaluating a goods-in time-window solution, ask two questions side by side:
- What proportion of my deliveries runs through carriers I can contact directly—and how much comes via FCA chains with no portal access?
- What do I want to influence: the booked time or the actual arrival time?
The answer to question one determines how large a blind spot a portal model has for your plant. If 50 or 60 % of your deliveries are FCA-organised, a portal structurally covers only the other half—and even for that half, the information ends at slot booking.
A quick calculation any logistics director can adapt to their own plant:
Say your plant receives 150 inbound deliveries daily. 40 % of those—60 trips—arrive in the morning peak between 06:00 and 07:30. For each driver whose actual arrival is unclear, dispatch and coordination takes an average of 10 minutes (call, callback, waiting time). That’s 60 × 10 minutes = 10 hours of effort in the morning peak—daily, at £25 per hour for dispatchers and fork-lift operators combined, that’s £250 daily, roughly £62,500 annually (over 250 working days). This isn’t a Heylog figure. It’s a calculation you need to adapt to your own plant—with your delivery volumes, your labour mix, your error rate.
Where Heylog fits into this picture
Heylog doesn’t address slot booking—that’s the domain of portals. Heylog sends the driver an automatic WhatsApp before they reach the gate. The driver reports their ETA without an app, without logging in, without anyone having to make a call. You see the information in the dashboard. No call. No guessing.
This doesn’t make Heylog a replacement for a time-window portal. It closes the gap between slot and gate—and for many mid-market plants, that’s the more expensive part of the problem.
Cargoclix, Transporeon and Heylog together?
Yes. For many plants, that’s the most honest answer. The portals structure booking. Heylog delivers information on arrival. Together they create an information flow that neither portal nor driver communication alone can provide.
So if you’re in comparison mode right now, asking which platform is better: that question is legitimate. But it’s incomplete until you’ve clarified what actually happens after booking—in the hours before arrival.
The question that remains
How many of yesterday’s deliveries did you know about 90 minutes before they arrived?
And how many only found out at the gate?
Frequently Asked Questions
What’s the difference between Cargoclix and Transporeon for mid-market plants?
Both providers operate as time-window marketplaces: hauliers book slots, shippers plan their yards accordingly. Transporeon targets large shippers with broad carrier networks; Cargoclix also serves mid-market facilities. For facilities with high FCA volumes, both models structurally cover only a portion of deliveries, since FCA carriers often lack direct portal access.
Why doesn’t a slot-booking system always deliver measurable improvements to goods-in?
According to Cargoclix’s own study, around 50 % of users report no measurable process improvement. A common reason: time-window control at goods-in ends with the booking—platforms don’t capture what happens between slot and actual arrival. Without real-time ETA data, you’re managing reactively, not proactively.
What does FCA inbound mean for time-window control at goods-in?
In FCA deliveries (Free Carrier), the supplier independently engages the haulier. The receiver has no contractual relationship with the carrier—and typically no direct access to time-window portals or tracking systems. Industry estimates suggest 40 to 70 % of inbound deliveries in the DACH region operate on FCA terms.