ฉบับเบต้า · เนื้อหาบางส่วนแปลด้วยเครื่องหรือแสดงเป็นภาษาอังกฤษ
ข้ามไปยังเนื้อหา
DEEPINGSOURCE
Back to blog
Guide2026-09-108 min

Queue and crowd analysis: when should store operations change?

Separate queue size, waiting time and people per unit of area. Compare defined zones and operating conditions before changing checkout or entrance staffing.

Author DEEPINGSOURCE

A busy checkout can have a long queue, a long wait, or too little room for people to pass. These are different operating questions. Define the zone and the unit of measurement first, then combine the signal with an on-site check before changing staffing or guidance.

Three measures that answer different questions

Queue analysis examines how people waiting for service and their waiting times change. Crowd density analysis examines how many people are present in a defined area relative to its usable space. Start by separating these measures:

  • Queue size: people waiting at a particular moment. Decide whether the person already being served and accompanying people count.
  • Waiting time: elapsed time from joining the queue to the start of service. Keep service time separate, and record what the system actually observes.
  • People density: people present at the same moment divided by the defined usable area. State the area boundary and unit, such as people per square metre.

A visitor count accumulated over an hour is not simultaneous occupancy. Likewise, dwell in a checkout zone may include browsing or accompanying someone. It does not automatically measure waiting.

Fix the boundary before comparing numbers

Draw the queue, the service point and the adjacent passage on the floor plan. Decide how to handle a shared queue serving several counters, people who leave before service, and a line extending outside the camera view. Mark unobserved periods as missing coverage, rather than an empty queue.

For a hypothetical density calculation, 8 people in a defined 20-square-metre area give 0.4 people per square metre. The same 8 people in a 10-square-metre area give 0.8. These values explain the denominator; they are not recommended limits or measured customer results. Neither average shows whether everyone is concentrated beside a narrow exit.

Keep the same area definition for comparisons. If a display or barrier changes the usable space, record the change and recalculate the denominator.

Read waiting records as well as averages

An average based only on completed waits leaves out people still waiting and those who left. Keep those groups visible in the reporting definition. Compare the number of observed waits, the spread of waiting times and the part of the period covered, not just one average.

Also record how many counters were open, interruptions, arrivals and changes in guidance. A shorter queue alongside fewer completed services may mean lower demand or people leaving; it does not by itself prove improved service. Confirm the explanation before describing a change as a result.

Turn a signal into an operating response

In an illustrative checkout review, staff first confirm that the people in the marked zone are waiting for service. They check which counters are operating and whether the queue obstructs a shared passage. The responsible person then decides whether to open another counter, change guidance or address an interruption.

After the change, compare a similar day and time window, record the operating differences and check adjacent areas. Moving the queue into the entrance is not evidence that the underlying problem has been resolved.

Choose alert conditions with the site's operating team, including who receives a signal, how long the condition must persist and what counts as resolved. A density value or alert is not a safety assessment. The UK's HSE crowd-management guidance, written for events, is a useful reference for explicit responsibilities and on-site risk review; it does not supply a universal retail threshold.

How saai care and saai insight support the review

saai care supports signals that prompt a current-condition check. saai insight supports analysis of activity and patterns over time. In a queue configuration, confirm the supported people, dwell and alert signals against the specific cameras and zones.

If automatic wait-time estimation or queue abandonment is required, confirm those outputs separately. Seeing a heatmap does not establish that a system measures either one. Staffing decisions and physical actions remain with the responsible people.

Define the queue, service point, passage and usable area.
Agree on who counts and when waiting starts and ends.
Mark missing coverage and incomplete waits explicitly.
Compare signals with open counters and on-site records.
Assign a response owner and check the result in adjacent areas too.

Use the visitor analysis guide to align visit counts with these time and area definitions before comparing them.

#queue analysis#crowd density#store operations
DEEPINGSOURCE

Considering privacy AI?

Talk to our team about a rollout plan for multiple stores and HQ.