> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/verkada-cameras/analytics/vehicle-analytics/configure-lpr-zones-in-command.md).

# Configure LPR Zones in Command

LPR Zones provide an efficient way to manage vehicle flow and occupancy. This feature is ideal for parking lots, drive-throughs, and shipping/receiving yards. Each page provides a daily view of activity, listing every vehicle present within a defined area.

{% hint style="warning" %}
LPR zones are supported only on the CB52-E, CB62-E, CB53-E, CB63-E, CB52-TE, CB62-TE, CB53-TE, and CB63-TE bullet cameras.
{% endhint %}

{% hint style="danger" %}
You must be a Site Admin for the site where the LPR cameras are located to create and manage LPR Zones.
{% endhint %}

***

### Before you begin

Ensure your setup meets the following requirements:

* **Hardware:** At least one Verkada LPR-enabled cameras is required.
* **Calibration:** Cameras must be properly positioned and calibrated to capture license plates for both entering and exiting vehicles.

***

## Configuration

{% stepper %}
{% step %}
**In Verkada Command, go to Cameras.**
{% endstep %}

{% step %}
**In the left navigation, select Vehicles.**
{% endstep %}

{% step %}
**In the left panel, select LPR Zones >** <i class="fa-plus">:plus:</i> **Create LPR Zone.**
{% endstep %}

{% step %}
**On Select Site, choose the relevant site for this zone.**

{% hint style="danger" %}
LPR Zones can only include cameras from the same site or parent site.
{% endhint %}
{% endstep %}

{% step %}
**On Camera Selection**:

1. Select the camera(s) monitoring vehicles entering the area as well as the type of plate to detect on each entrance camera (front plate or rear plate).&#x20;
2. Select the camera(s) monitoring vehicles leaving the area as well as the type of plate to detect on each exit camera (front plate or rear plate).&#x20;

{% hint style="warning" %}
You can select the same camera for the entrance and exit detections but cannot use the same plate type (front/rear) for both the entrance and exit.&#x20;
{% endhint %}
{% endstep %}

{% step %}
**(Optional) On In-Zone Time Limit, define a custom timeout.**

{% hint style="info" %}
You can configure a zone timeout to automatically mark vehicles as departed if their exit was missed. Any vehicle that is present in the zone for more than the timeout period is assumed to have been missed at the exit. The system will therefore consider this record as invalid and discard it from the current occupancy count.
{% endhint %}
{% endstep %}

{% step %}
**(Optional) Enable Smart Plate Matching**&#x20;

{% hint style="warning" %}
In some cases, license plate recognition may occasionally misidentify similar characters (5 and S, O and 0, B and 8). To ensure that visits are as accurate as possible, we will match similar license plate records to prevent duplicate records caused by glare or character confusion. &#x20;
{% endhint %}
{% endstep %}

{% step %}
Click **Save.**
{% endstep %}
{% endstepper %}

***

## Analytics dashboard

The Analytics dashboard summarizes how vehicles move through the zone for the selected day. Use the top-level metrics for occupancy and flow at a glance, then use the vehicle table to review individual detections, status, and time in zone.

<div align="left" data-with-frame="true"><figure><img src="/files/Av1IrLMIEGb1nMRqIHyQ" alt=""><figcaption></figcaption></figure></div>

### Top-level metrics

* **Current Occupancy:** Real-time count of vehicles currently in the zone
* **Entries/Exits:** Total count of vehicles that have entered or departed
* **Unique Visitors:** Total number of distinct vehicles detected
* **Median/Max Time in Zone:** Statistical breakdown of how long vehicles stay on-site

### Vehicle table

The table is a live log of detections and includes:

* Plate thumbnail and plate string
* **Status** (Still In or Departed)
* Entry and exit timestamps
* Time in zone (current duration for active vehicles)

Use the following filters and search options to quickly find specific vehicles:

* **Status:** Toggle between All, Still In, or Departed
* **License plate search:** Search by full plate or prefix, with fuzzy matching for similar results
* **Time filters:** Filter by custom entry and exit time windows
* **Time in zone:** Find vehicles based on duration (greater than, less than, or within a range)
* **Invalid:** Toggle **Invalid Only** to show invalid records

### Plate Details

Click a vehicle row entry to open the **Plate Details** page, which includes the following information:

* Full plate string and thumbnail
* **Status** (**Still In** or **Departed**)
* Vehicle time in zone
* Associated **LPOI (License Plate of Interest)** lists
* A link to the vehicle’s history page.
* Entry and exit video clips

<div align="left" data-with-frame="true"><figure><img src="/files/aNOB3IIGCDfuMOcgqaAl" alt=""><figcaption></figcaption></figure></div>

***

## Invalid visits and edge cases

Some reads can be missed. When Command cannot build a valid entry/exit pair, the visit may be marked invalid. Invalid visits are excluded from aggregate time in zone metrics, so totals stay accurate.

* **Missed entry & detected departure:** If a vehicle is seen exiting without a matching entry, the event is logged but marked as **invalid** and shows **Unknown** for time in zone.
* **Consecutive entries:** If a vehicle has consecutive entry reads without an exit, the first visit record is marked as **invalid,** with an unknown exit and time in zone.
* **Manual override:** From [Plate Details](#plate-details), you can mark a vehicle as departed when you know it left, but the exit camera did not detect it.
* **Visit Timeout**: When using the in-zone time limit feature, any visit that exceeds the timeout duration value will be considered invalid and excluded from the current occupancy count. This feature is especially useful for zones where visits are expected to be short.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.verkada.com/verkada-cameras/analytics/vehicle-analytics/configure-lpr-zones-in-command.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.