The brief: parcel collection across a campus
Hublok manufactured, delivered and installed locker units at 20 locations across a technology campus in the Netherlands. The original project account describes a requirement to deliver accountable items to people working in open workspaces or partly from home.
Integration with the existing inbound process
The locker locations were connected to the campus’s existing inbound registration system. The customer feedback published with the original story identifies several requirements: no separate app or registration for the end user, and a platform that did not depend on a third-party cloud-hosted service for that particular deployment.
The feedback also describes bespoke configurations across the campus buildings and Hublok’s own installation team carrying out the on-site placement and installation. These details relate to this delivered configuration; they are not a claim that every Hublok software option uses the same hosting or registration model.
What this demonstrates
A multi-building project needs a consistent parcel process while allowing the furniture and placement to suit individual spaces. The useful evidence here is the 20-location scope, the connection to the existing registration process and the stated end-user requirements.
When planning a comparable campus, map the users, inbound process and collection access at each location first. Then agree how the locations will be administered and what happens when a parcel cannot be collected. The archived story does not publish utilisation figures or quantified staff-time savings.
Requirements, software capabilities and service arrangements are confirmed for each new project.
Back to projects & insights