Fifteen modules, all built. Yard devices have been tested without physical hardware. What is missing is listed under Technology and not here.
Checks are performed in this order. The first check that fails provides the text the carrier sees. An empty list triggers a call; a reason prompts booking another time slot.
Answers a single question: Which time slots can this carrier book on this day? Vehicle type, temperature zone, and dangerous goods determine which dock is eligible in the first place.
Booking and cancellation in the portal, in the form, and via the interface. Every appointment adds an entry to the history. To prevent double bookings, the check runs in the same transaction as creation.
Dedicated access for external users, separate from internal screens. Self-registration, approval by dispatch, and an overview of their own bookings.
Check-in by license plate. The status chain moves forward only: checked in, in the yard, called, at the dock, finished, checked out.
The daily overview for dispatch. Key figures, an occupancy strip per dock with a marker for the current time, and vehicles on site with their status.
A page for the driver’s phone, accessible via SMS link. No account, no password. Built as a Progressive Web App, it continues to work in dead zones.
Dispatch via SMS for five triggers. Creation and dispatch are decoupled so no message is lost if the gateway is temporarily unavailable.
A dedicated service running every 15 minutes. It marks no-shows and queues reminders 24 hours before the time slot.
Docks, carriers, vehicle fleet, opening hours. What the dock is called in the interface is set per site in the master data: dock, door or bay.
Four views, all calculated from bookings and yard appointment timestamps. CSV export, prepared for Excel with German settings.
Documents attached to each appointment, ten types. The appointment, not the file, is the entry point. Mandatory documents are defined per type, and the screen indicates which are still missing.
REST with a machine-readable specification. A rejection is not an error, but a successful response with a reason. Order import is repeatable. Each connected system receives its own key: read access suffices for reconciliation; those who need to book or cancel require explicit permission.
License plate readers, barriers, display boards, scales, and terminals can be connected via a dedicated interface. The reader reports what it detects and receives a decision: admit, wait, or reject, each with a reason. Without a booking, the barrier stays closed. The interface has not yet been tested against physical hardware.
Colors, fonts, and logo reside in a brand sheet; the grid is separate in a base stylesheet without a single color value. A second customer receives a brand sheet, not a second UI.
Portal, registration, driver page, and text messages support eleven languages, from Polish to Swedish. The selection reflects long-distance transport to Germany; French and Swedish were added for the first target markets. In the portal, users choose via a switcher in the header; for drivers, the appointment determines it: the carrier sets the language during booking. Internal screens are available in German, English, French, and Swedish.
All calculated from bookings and the timestamps of yard appointments. There is no separate aggregated metrics table that could deviate from its source.
We walk through the process on our test system with your docks, operating hours, and restrictions, plus status, roadmap, and the pilot offer.