Retail Labour Banding: How to Allocate Hours Fairly Across Stores

Written by: Ben Flikkema | Content Specialist at StoreForce

Two stores each generate $50,000 in weekly sales. One opens for 60 hours, operates on a single floor, and receives two deliveries a week. The other opens for 75 hours, has a larger selling area, and handles a substantial volume of online pickups.

Giving both stores the same labour budget creates a problem. Their revenue is similar, but the work required to operate them is different.

Multiply that decision across a retail network, and small allocation errors become persistent problems. Some managers struggle to cover essential work. Others have hours available during periods when demand is low. Finance sees differences in productivity, while operations needs to understand what is driving them.

Labour banding gives retailers a structured way to group stores with similar operating requirements and set appropriate labour expectations for each group. It creates a common starting point for allocating hours, comparing performance, and identifying where a location needs closer attention. Retail Workforce Management Software

Bring Your Stores Together and Execute Better

Give your teams the workforce management tools to drive better results.

Speak to Our Team

What is labour banding in retail?

A labour band is a group of stores that share characteristics relevant to staffing. Those characteristics might include sales volume, customer traffic, operating hours, store format, or service requirements.

Each band provides a framework for setting labour hours and productivity expectations. A high-volume outlet band might have different standards from a group of smaller stores that provide appointment-based service.

The purpose is to make the reasoning behind labour allocations clear. Retail leaders should be able to explain why a store receives its hours, which assumptions support the allocation, and what would justify a change.

Banding also gives managers a more useful comparison group. A store can be reviewed alongside locations doing similar work under similar conditions. Retail Workforce Management Software

Choose store characteristics that explain the work

Sales volume is a useful starting point, but it rarely explains the entire staffing requirement.

A store selling higher-priced products may generate more revenue from fewer transactions. Another may serve more customers, process more units, and require more replenishment to generate the same sales.

Choose attributes that materially change the work stores need to complete.

Store characteristic

Why it matters to labour planning

Sales and transaction volume

Helps establish business scale and the volume of purchases the team supports

Customer traffic

Shows service demand, including visitors who need help but do not purchase

Operating hours

Determines how long the store must maintain coverage

Format and layout

Multiple floors, separate departments, and large selling areas affect deployment

Service model

Fittings, consultations, demonstrations, and appointments require associate time

Operational workload

Deliveries, replenishment, pickups, and returns add work beyond selling

Geography and wage environment

Affect the cost of staffing and the usefulness of comparisons between markets

Start with a manageable number of meaningful groups. If every store becomes its own band, maintaining standards becomes difficult. If one band contains stores with substantially different workloads, the comparison loses value.

Document exceptions so they can be reviewed. A temporary refurbishment, for example, may justify a short-term adjustment without changing the store’s permanent band.

Build the analysis from consistent data

Before comparing stores, agree on what the numbers include.

Are labour hours scheduled or actually worked? Do they include store management, training, and stock processing? Are sales reported consistently across markets? Are opening hours taken from the current trading calendar?

Those definitions affect the conclusions. A store that records delivery processing as non-selling time will look different from one that leaves the same activity unclassified.

Use a period that represents normal operations and review unusual weeks separately. A stocktake, store opening, major promotion, or temporary closure can distort the baseline.

Review these measures together:

  • Sales, traffic, and transactions to understand business activity.

  • Total labour hours and labour cost to understand investment.

  • Operating hours to understand the coverage requirement.

  • Selling and non-selling hours to understand how time is deployed.

  • Conversion and service observations to assess whether current coverage supports customers.

Hours and dollars answer different questions. Two stores can use the same number of hours and have different labour costs because of wage rates or role mix. Keep both visible.

Use SPH and PPOH to test labour expectations

Sales per labour hour and people per open hour help retailers examine productivity and coverage from different angles.

Sales per labour hour shows the relationship between revenue and hours

Sales per labour hour = Sales ÷ Labour hours

A store generating $50,000 from 250 labour hours delivers $200 in sales per labour hour.

If $200 is the agreed planning standard for a suitable band, a $60,000 sales forecast would imply 300 hours before other requirements and adjustments are considered.

The standard needs to reflect credible operating conditions. Review stores that achieve it while maintaining service and completing essential work. An unusually high result deserves investigation, especially if the team is missing tasks or struggling during peak periods.

People per open hour adds coverage context

PPOH = Labour hours ÷ Store opening hours

A store using 240 labour hours across 60 opening hours has a PPOH of four.

That average helps leaders compare staffing intensity across similar stores. It does not tell them how many associates are available at a particular moment. Pre-opening work, stockroom activity, breaks, and uneven scheduling can all affect floor coverage.

Use PPOH alongside the actual schedule. A minimum PPOH planning threshold can flag an allocation that needs review, while coverage requirements by time and role establish whether the store can operate as intended.

Work through a labour allocation before approving it

Consider this simplified illustration. Both stores have a $40,000 weekly sales forecast and an initial productivity assumption of $200 per labour hour.

Planning measure

Store A

Store B

Weekly sales forecast

$40,000

$40,000

Hours implied by the SPH assumption

200

200

Weekly opening hours

60

75

Illustrative baseline of three people throughout opening hours

180 hours

225 hours

Store B would need 225 hours simply to meet that illustrative coverage baseline. Its sales-based allocation provides 200.

That gap prompts a review. Does Store B belong in the same band? Is its opening schedule appropriate? Does the productivity assumption reflect its service model? What additional hours are needed before opening, after closing, or during peak demand?

These figures are a planning example, rather than a StoreForce calculation. A retailer’s model must define how baseline coverage, variable demand, and operational work fit together so the same work is counted once.

Investigate outliers before reallocating hours

Once stores are grouped, compare their results within each band. A location using substantially more hours than its peers may have an allocation issue, a scheduling issue, or a workload difference the band does not capture.

What stands out

What to investigate

Low SPH and high PPOH

Long opening hours, weak demand, additional workload, or hours placed in quieter periods

High SPH and weak conversion during peaks

Whether customer demand exceeds available service capacity

High non-selling hours

Delivery volume, processing methods, task requirements, and time coding

Similar weekly hours but different service outcomes

Shift timing, role coverage, associate experience, and task deployment

Repeatedly high hours across one format

Whether the band’s standard reflects that format’s operating requirements

Bring district and store leaders into this review. They can explain work that a report may not capture. Ask for evidence of recurring requirements so justified exceptions can improve the model.

A scatter chart can help locate unusual combinations of sales, hours, or productivity. The next step is to understand what produces the result.

Carry the allocation through to peak-hour scheduling

Labour banding establishes a framework for how much labour a store receives. Forecasting and scheduling determine where those hours land.

A store can have a reasonable weekly allocation and still leave Saturday afternoon undercovered. Once hours are approved, managers need to distribute them around customer demand, role requirements, breaks, and essential tasks.

Review performance after changes take effect. Did peak coverage improve? Did conversion hold or grow? Were deliveries and replenishment completed? Did actual hours stay close to plan?

Aesop introduced labour banding as part of a broader change to traffic-informed labour planning with StoreForce. It targeted 90% peak coverage and reported conversion increasing from 49% to 53%, while total labour hours remained flat year over year. Those results came from the wider labour strategy, including how existing hours were deployed. Read the Aesop case study. Retail Workforce Management Software

How StoreForce supports labour banding and planning

StoreForce includes labour banding within its labour optimisation offering. Retailers can use store performance and demand data to review allocations, identify locations that warrant investigation, and connect labour planning with scheduling. Explore StoreForce Labour Optimisation. StoreForce

That connection helps teams follow a decision through. Finance and operations agree on the allocation assumptions. Field leaders review exceptions with stores. Managers build schedules around demand, and leaders assess the coverage and performance that follow.

For a demo, bring a group of stores whose labour allocations are difficult to explain. Compare their sales, traffic, opening hours, and workload, then walk through how a revised allocation would affect their schedules.

Book a StoreForce demo to see how labour banding can support clearer labour decisions across your store network.

See How StoreForce Can Work for Your Stores

Book a quick chat with us today, to improve your retail operations tomorrow.

Speak To A Retail Expert