LUKE 1977
A consistent view of footfall across different store formats.
The SUS article describes Luke's UK store network across high-street, shopping-centre and flagship formats. It does not publish a branch list, installed-device count or exact rollout dates.
Project at a glance
Customer
Retail · UK fashion estate
Deployment scope
See the installation account below
Measurement focus
Scope or reporting capability, not a verified uplift
Delivery partner
Published SUS deployment account
The initial problem
The account addresses a multi-store question: how can head office compare stores fairly while local teams respond to their own hourly trading patterns? A busy entrance, a strong sales total and effective staffing are different measures, so the reporting needs to connect them rather than treat them as interchangeable.
Read the published account ↗What SUS installed
SUS installed overhead 3DPro2 devices with Power-over-Ethernet cabling, calibration and test counts. SUS describes starting with pilot stores and expanding after refining configuration standards and dashboards, with staff-exclusion rules and sales-data integration.
Read the published account ↗How the reporting was used
The article describes using hourly traffic patterns to review breaks, fitting-room cover and cash-desk staffing. It also sets out estate benchmarking and campaign comparisons as uses of the platform. No particular branch-level staffing change is asserted on this page.
Read the published account ↗The operational change
The deployment provides a shared measurement approach across Luke stores. The article explicitly says its numerical outcomes are examples that can be replaced with Luke's real numbers. Consequently, none of its conversion, productivity, campaign or revenue percentages is presented here as a measured Luke result.
Read the published account ↗What the evidence supports
SUS Luke installation article, published 11 December 2025; checked 19 September 2026. Deployment is supplier-reported. Numerical outcomes are explicitly presented as examples, not verified Luke results.
Sources, approvals and measurement standard
Standard for newly validated outcomes
A future result will be labelled “Measurement record available” only when its KPI definition, baseline, comparison period, site scope, counting exclusions, calculation and source records have been reviewed and publication approved. This is the acceptance standard, not a claim that every existing figure has passed it.
Legacy figures and qualitative accounts
Previously published supplier figures remain labelled as such, with missing measurement details stated. Installation facts, reporting capabilities and qualitative operational changes are not commercial uplift. None of the figures here is presented as independently verified.
Need consistent footfall reporting across your store estate?
Tell SUS what you need to understand, where you need coverage and which decision better data should inform. Send it through the SUS enquiry form and mention this customer story.
Book a free 20-minute footfall review ↗Calculate likely ROI →