Parcel locker software
& integrations.
Choose the software around who deposits, who collects and what your team needs to know.
Self-service deposits
An authorised delivery user identifies the recipient through the selected interface, deposits the item and triggers a collection notification.
Managed mailrooms
A mailroom team records incoming items and allocates compartments, with collection events visible through the agreed system.
Internal and outbound handovers
Explore colleague-to-colleague transfers or a service collection process, with permissions and notifications configured for the workflow.
Connect to the systems
you already use.
Hublok can scope suitable interfaces with existing mailroom, identity or facilities platforms. API availability does not automatically mean every integration is included: the data flow, access permissions and responsibilities are agreed first.
Depending on the selected platform, hosting and management arrangements are defined during technical discovery.
Read more on Hublok ↗Access and notifications
Agree PIN, QR, barcode, card or other supported methods, and the relevant email, SMS or platform notifications.
Records and exceptions
Define what is logged, how administrators access it and what happens with faults or uncollected parcels.
Support ownership
Agree who supports the lockers, software and any third-party interface before handover.
Choose the workflow before the interface
| Workflow | What to agree |
|---|---|
| Managed mailroom | Recipient identification, parcel allocation, notifications and event records. |
| Self-service deposit | Authorised users, the deposit journey and the collection credential. |
| Multiple locations | How each location relates to the existing registration or facilities platform. |
| Internal transfers | Who may leave an item for a colleague, how it is recorded and who handles exceptions. |
Availability, hosting, credentials and integration scope are confirmed for each new system.
Software questions to resolve early
Which access credentials are available?
PIN, QR, barcode and access-card journeys can be explored according to the selected hardware and software. Confirm the required credential and notification method in the specification rather than assuming every option is included.
Does an API mean an integration is already included?
No. An API is one part of an integration. Recipient data, access permissions, transaction events, hosting, testing and support ownership still need to be agreed between the relevant teams.
Who supports a fault?
Agree the first point of contact and responsibilities for the locker hardware, software, network and third-party platform. The proposal should set out the support arrangement and any recurring charges.
Let’s find the right fit for your building.
Tell us about your space, your users and the way deliveries arrive. We’ll help you explore the options.