Store staff
Turnover measured in months
Every site
Hundreds of sites, one way in
The problem here is not a regulator. It is scale, churn, and access nobody can withdraw centrally. Store teams, regional contractors and constant churn, governed from one place.
Retail & Distribution
Multi-site access control for retail and distribution
Hundreds of sites, thousands of joiners
Who is on your sites
Regional and roaming staff
Covering 10 or 20 stores, sometimes more
Distribution centre agency labour
Shift peaks, seasonal surges, high volume
Regional contractors
Refrigeration, cleaning, security, per region
What you are held to
Loss prevention · insurance · GDPR
- Know who can open which store, and be able to change it centrally the same day
- Withdraw access for leavers across every site they ever worked in
- Keep the record without holding more personal data than you need
Where it breaks today
- Store access runs on shared codes and keys. A leaver still opens 12 stores
- A regional contractor holds a credential nobody can revoke without visiting every site
- Opening or refitting a store means someone drives out to configure access by hand
Thousands of joiners and leavers a month across hundreds of sites. The cost is not a fine. It is the hours, the shared codes, and the lock changes you pay for when a contract ends.
Retail & Distribution
Scenario
A regional contractor loses the contract on a Friday
40 refrigeration technicians hold access to 220 stores across 3 regions. The new supplier starts Monday.
One call, one decision
The contract ends. The contracting company is closed in the platform. 40 people, and not 1 company.
Every store, at once
Access stops in all 220 stores that evening, whatever access system each of them runs.
The new firm onboards itself
The incoming supplier loads its own technicians and their certificates over the weekend, through its own login.
Monday works
The new technicians badge into the stores on their route, with access limited to the stores on their route.
What changes
- No lock changes, no engineer visits, no shared code circulating after a contract ends
- Store managers stop administering access, and stop being the reason it is out of date
- A new store opens with its access already defined by its format, with nothing configured on site
Compliance
The regimes behind this
Questions
Frequently asked questions
Can access be withdrawn across hundreds of stores at once?
Yes. Access is held against the contracting company as well as the individual. Ending a contract closes 1 record instead of several hundred, across every store and whatever access system each store runs.
Does this remove shared door codes?
It removes the reason for them. Shared codes exist because issuing an individual credential is slow. When issuance is automatic against the identity record, each person can hold their own.
How is a newly opened store configured?
By store format, with nothing typed in by hand. A new site inherits the access definition for its store format. Nobody has to drive out and configure it locally.
The first step
Start with 1 site and 1 population.
You judge something that runs on your own site. Your access systems and readers stay where they are. If it earns its place, we extend it site by site.
One siteOne populationYour readers stay