KERONG Smart Lock Integration for Lockers, Cabinets and Self-Service Systems

We perform the analysis of the lock model, controller board, power requirements and feedback signals obtained from documentation.

The proof of concept includes checking the most important performance: getting the access to the needed compartment, the release request and the response obtained. We also define those parameters that cannot be evaluated by the hardware before they become part of the application.

We develop communication software for supported KERONG controllers using the documented protocol.

The work includes controller addressing, compartment mapping, command handling, response parsing and communication timeouts. RS485 describes the communication interface; the actual commands and message structure must come from the relevant controller documentation.

For networked installations, we connect the locker controller to an appropriate local computer or gateway.

The gateway can coordinate hardware commands, retain necessary operational state and communicate with the backend. We establish how it behaves during network interruptions and prevent controller interfaces from being exposed directly to the public internet.

We create procedures for compartment assignment, parcel storage, notification of recipient, pickup and return.

The system separates a booking and a parcel drop-off. Moreover, it deals with problems like a compartment breaking down, a door being open, or an unsuccessful pick-up attempt.

We build operator and customer interfaces for supported kiosk hardware.

The scope can include scanning a collection code, choosing a locker, displaying instructions and guiding the user through recovery. Session timeout, accessible instructions and protection of the kiosk’s administration functions are included in the design.

We create mobile applications for end users, delivery personnel, building staff, and administration.

Mobile functionality may include locker allocation, approved release requests, local access, and operation logging. The application distinguishes between a request and a process.

We assess supported KERONG NFC locks for cabinet, drawer and locker applications.

The work includes the authorized phone-to-lock interaction, credential lifecycle and permitted event collection. Phone compatibility, NFC behavior and the required power-transfer interaction are tested using the actual lock and target devices.

We integrate the access methods supported by the selected hardware and software interfaces.

These methods may operate at different layers. For example, a QR code may be validated by a kiosk or mobile app, which then instructs a controller to release a compartment. That does not mean the lock itself contains a QR reader.

We create dashboards enabling efficient management of locations, banks, compartments, users, and operational problems.

The access rights are managed on the backend side. The local operator must only manage the assigned locations, while central operators can get broader view. Remote release and other actions subject to logging are undertaken with an audit trail.

We connect locker operations with authorized external systems.

The scope can include orders, employee assignments, equipment loans, memberships or service requests. The design establishes which system owns each record and how updates are reconciled after a failure or interruption.

Where standard components do not meet the agreed requirement, we can scope custom gateway firmware or interface electronics for hardware the client owns or is authorized to modify.

This may involve communication interfaces, sensor inputs, power supervision or protected output stages. Electrical limits, wiring and power behavior are validated against the selected locks and controllers.

Our monitoring practices are designed around the signals that the equipment emits, for example, communication errors, latch feedback as well as sensor data.

Testing is done to check for wrong addressing, disrupted processes, recovery, and access boundaries. Handover could involve delivering the source code as per the agreement, files with configuration information, documents on wiring, test results, and maintenance techniques.

The firmware made by the producer, equipment guarantees, and licenses granted by third parties are kept apart unless stated otherwise.