Understanding Lock Code Statuses

Every lock code in SuiteOp has a status that tells you where it is in its lifecycle — from creation through to expiration or deletion. Understanding these statuses helps you quickly diagnose issues and know when to take action.

Code status reference

Here are all the statuses you may see on a lock code, along with what each one means:

Pending: The code is queued for installation and will be pushed to the device.
Scheduled: The code is scheduled for installation at a future time.
Awaiting Code: Waiting for a code value to be assigned before installation.
Installed: The code has been pushed to the device but the time window has not started.
Active: The code is active and can be used to unlock the device.
Expired: The code's time window has ended and it is no longer usable.
Failed: The code could not be installed on the device.
Pending Deletion: The code is queued for removal from the device.
Failed Deletion: The code could not be removed from the device.
No Access: The reservation does not grant access to this device (e.g. the guest's access is restricted).
No Locks: The property has no locks assigned, so no code can be installed.
Unknown: The code status could not be determined.

Normal code lifecycle

A reservation code typically moves through these statuses in order:

Pending — SuiteOp has generated the code and queued it for installation. The code will be pushed to the lock automatically based on your configured lead time (typically 24 hours before check-in).
Installed — The code has been successfully pushed to the lock hardware. It is on the lock but not yet usable because the reservation’s check-in time has not arrived.
Active — The check-in time window has started. The guest can now use this code to unlock the door.
Expired — The checkout time has passed. The code is no longer usable and will be cleaned up automatically.

Problem statuses

If something goes wrong during the code lifecycle, you will see one of these statuses:

Failed — The code could not be installed on the lock. This can happen if the lock is offline, unreachable, or has reached its maximum code capacity. See Troubleshooting Smart Locks for steps to resolve this.
Pending Deletion — SuiteOp is attempting to remove the code from the lock. This is a temporary status that typically resolves within a few minutes.
Failed Deletion — The code could not be removed from the lock. The code may still work on the physical lock even though SuiteOp has marked it for removal. Contact support if this persists.
Unknown — SuiteOp cannot determine the current status. This usually happens during lock transitions or when codes exist on the lock from an external system. See Transitioning Legacy Locks for more details on Unknown codes during migrations.

Special statuses

Awaiting Code — The system is waiting for a code value to be assigned. This occurs when the code generation strategy requires external input (for example, importing a code from your PMS).

Code types and their lifecycles

Different code types follow slightly different patterns:

Code type	Lifecycle
Reservation	Pending → Installed → Active → Expired (automatic, time-windowed)
User	Pending → Installed → Active (stays active until the user is removed or code is changed)
Backup	Pending → Installed → Active (stays active until used, shared, or cleaned up)

When to take action

In most cases, SuiteOp handles code management automatically. You should only intervene when:

A code shows Failed status close to or after check-in time — try syncing or re-installing the code
A code is stuck in Pending for more than an hour — the lock may be offline or unreachable
Multiple codes show Unknown — this may indicate a lock integration issue

Troubleshooting Smart Locks — fix failed or stuck codes
Automatic Backup Code Replacement — how backup codes work
Setting Up Smart Locks — initial lock setup and configuration