Retail Turnover Rate: Formula and Worked Example

Short answer

Retail employee turnover rate is departures during a period divided by average employee headcount for that period, multiplied by 100. The result is only useful when its scope is explicit: voluntary and employer-initiated departures, seasonal contract completions, internal moves, worker type, location, and time period can all change the number.

The retail turnover formula

Use this basic formula:

Employee turnover rate (%) = employee departures during the period / average employee headcount during the period x 100

For a stable workforce, a simple average can be adequate:

Average headcount = (opening headcount + closing headcount) / 2

For a retailer that hires heavily for holidays, tourism peaks, or a new-store launch, the opening-and-closing average can conceal a large mid-period change. In that case, average the weekly or monthly headcount observations across the full measurement period. Use the same frequency for every store being compared.

The public introduction to the CIPD turnover and retention factsheet connects understanding departures with choosing retention initiatives. The calculation and worksheets below provide a practical method; the member-only sections are not reproduced here.

A fictional worked example

Consider a fictional retailer, North Street Home, measuring one calendar quarter. Its average monthly headcounts are 124, 132, and 134.

Average quarterly headcount = (124 + 132 + 134) / 3 = 130

During the quarter, 18 employees leave the measured workforce:

The figures are invented and rounded to one decimal place. They illustrate the method, not a retail benchmark.

The 13.8% total answers, “What share of the average measured workforce left during this quarter?” It does not answer why people left, whether every departure was avoidable, or whether the rate is healthy. The split immediately makes the result more useful: a planned seasonal completion is a different operating event from a resignation by a permanent store supervisor.

Set the counting convention first

Write a short measurement note before extracting the data. It should answer these questions:

1. What is the period: month, quarter, rolling 12 months, or calendar year?
2. Which population is included: employees only, or also agency and contingent workers?
3. Which locations, functions, and employment types are in scope?
4. Which events count as departures?
5. How is average headcount calculated?
6. Are rates reported separately for voluntary, employer-initiated, and planned seasonal departures?
7. How are transfers between stores treated?

Apply that note to both numerator and denominator. For example, do not count agency worker departures in the numerator when agency workers are absent from headcount.

Voluntary and employer-initiated departures

Report employee resignations separately from layoffs, dismissals, and other employer-initiated exits. A combined rate is still useful for workforce flow, but it should not erase the distinction.

The US Bureau of Labor Statistics JOLTS programme defines quits as employee-initiated separations and layoffs and discharges as employer-initiated separations. Its JOLTS definitions also place events such as retirement, death, disability, and transfers to another location of the same firm in “other separations.” Your internal convention may classify an internal transfer differently, so document the difference before comparing your result with JOLTS.

Seasonal workers

Seasonality is part of retail workforce design, not a data-cleaning nuisance. A planned fixed-term completion may indicate that hiring matched demand. Combining it with unplanned resignations can make a store look unstable when it operated as intended.

Use two complementary views:

• All-worker turnover: includes every in-scope employee departure, including planned seasonal completions.
• Core-workforce turnover: excludes the defined seasonal-worker population from both departures and average headcount. Keep the same worker scope in the numerator and denominator.

Keep the all-worker figure visible so the organisation can still plan recruitment, payroll, induction, and offboarding workload. Label the core view clearly. Do not change the definition after seeing which version looks better.

Internal moves

A transfer from Store A to Store B can be a loss for Store A without being a departure from the company. Track it as internal mobility at company level and, if operational continuity matters, as an outbound store move in a separate location-level measure. Calling it employee turnover in one report and mobility in another makes comparisons unreliable.

Compare rates without creating false precision

External data can provide context only when definitions, periods, populations, and denominators align.

The US JOLTS definitions describe a monthly flow of separations. National monthly estimates are not directly comparable with North Street Home's fictional quarterly rate or an employer's annual leavers-over-average-headcount calculation. Check the observation period, departure categories, worker scope and adjustment method of an external series before using it. Multiplying one monthly rate by 12 gives, at most, a simple annualised illustration under unchanged conditions. It does not measure actual annual departures or average headcount, and seasonal patterns can make it misleading.

For UK analysis, avoid confusing employee turnover with retail sales turnover. A directly comparable official UK retail employee-turnover series was not identified in the official sources reviewed for this article. Use an internally consistent series for store decisions, and treat any external survey as context only after checking its sample, period, population, and definition.

A useful comparison set is usually closer to the decision:

Investigate a high rate carefully

A turnover rate is a prompt for investigation, not a diagnosis. Start by testing the measure itself, then combine operational data with employee accounts.

• Reconcile departures and headcount with payroll or HR records.
• Check whether a store opening, closure, acquisition, outsourcing change, or seasonal peak changed the population.
• Segment by role, contract type, tenure, location, and departure type, while suppressing or combining groups that are too small to interpret responsibly.
• Review scheduling, vacancies, overtime, training completion, absence, pay changes, and manager changes on the same timeline.
• Read documented exit reasons cautiously because response coverage and coding can vary.
• Invite voluntary, structured conversations with current employees and give them a route outside the line manager where appropriate.
• Record hypotheses as hypotheses until multiple sources support them.

Suppose the fictional North Street Home result is concentrated among new sales assistants in two stores. That association would justify checking recruitment expectations, induction, shift allocation, local labour conditions, and manager support. It would not prove that a particular manager caused the departures. Interviews or group discussions may add context, but they should not be used to score an individual's likelihood of leaving.

Turn the measure into a review cycle

Assign each agreed action an owner, an evidence source, and a review date. A small worksheet keeps the analysis connected to decisions:

This cycle keeps action proportionate. It also helps teams learn when the original hypothesis was wrong.

What to do next

Calculate the rate using a written convention, publish the departure breakdown beside the headline number, and compare like with like. Then investigate material changes with employees and operational teams before choosing an intervention.

If the pattern points to inconsistent day-to-day support, use the frontline manager enablement guide to scope the work, capture practitioner knowledge, and define what managers should be able to do differently.

When the figures point to a question about daily work, Lontra can support a focused employee conversation campaign and a manager brief for follow-up. For example, ask which first-week tasks lacked practical support, then agree who will respond. Explore employee conversations with Lontra.