Head office decides once. Forty sites execute.
A store-open routine that comes back signed, a seasonal reset that lands the same week everywhere, and a request from site that goes somewhere other than a phone call. Choose Retail & Multi-site Operations at setup and all three are queued.
Default project tabs
Goals is on for per-site targets; Capacity is off — staffing here is a rota, not a project load.
Projects created on day one
- Store Operations
- Campaigns & Seasons
- New Sites
What changes, in the hours it actually changes.
Three moments from an ordinary week. Every one of them is a thing the product does, not a thing it could be configured to do one day.
06:15 — the store-open routine is already waiting
One written procedure runs at every site. Each step carries a tick and the name of the person who ticked it, so head office can see which stores finished the routine and which are still open — without ringing round.
10:30 — a request from site goes somewhere, not to someone
Intake takes it with a category and a priority — a failed chiller, a signage error, an IT ask — and it is triaged, assigned an owner and moved from new to done. Nobody's personal messages are the ticketing system any more.
Season change — the reset lands the same week everywhere
Recurring Tasks put the same job on the same date at every site, created, assigned and dated automatically. The Ledger says which fixture is where, and the KPI Dashboard says whether the week moved the number.
The three that do the heavy lifting.
Choose this industry during setup and its tools are queued for you. Review the list, drop anything you don't want, and the workspace initialises with the rest already working — or install any one of them on its own, later, from the marketplace.
Checklists & SOPs
Write the standard procedure once — store open, close, a safety walk, a seasonal reset — then run it at each site, ticking every step with a record of who did what.
- One written procedure, run at every site
- Every step ticked, with the person who ticked it
- A run per site, kept as its own record
- The record of the run is the proof
Intake
One front door for everything a site needs — maintenance, IT, signage, stock. Each request arrives with a category and a priority, and is triaged to a named owner.
- One queue for every request from site
- Category and priority on arrival
- Triaged to a named owner
- New → in progress → done, with the record kept
Recurring Tasks
Work that repeats — daily, weekly or monthly — creates its next occurrence on its own, so a seasonal reset lands on the same date at every site without anyone chasing it.
- Daily, weekly or monthly schedules
- The next task is created for you
- Assigned and dated on creation
- The same job, the same week, everywhere
How Retail & Multi-site Operations actually runs.
Each of these is a project in Noots — its own board, tab strip, meetings, calendar and members. They are not pre-built modules and we will not pretend they are: what the industry gives you is the right defaults around them.
These sit on top of the whole product.
- Announcements reach every site at once, pin when they matter and come back acknowledged
- The Ledger is a register of every fixture, device and licence — who holds it and where it lives
- The KPI Dashboard keeps the numbers that matter with a target and a trend as readings are logged
- Team Availability shows who is around and until when, before anyone is pinged
- Automations fire on a due date or a status change and post to the channel that cares
The honest edges.
- Noots does not connect to your EPOS, stock or workforce-management system. A site's numbers arrive because a person logs them or an automation posts them.
- A completed checklist is proof that a named person ticked each step. There is no photo verification and no location check behind it.
- Team Availability records what people post about their own week. It is not a rota engine and it does not build shift patterns.
- Noots holds no SOC 2 or ISO 27001 attestation and offers no uptime SLA.
Built for the way your trade actually runs.
The ones buyers ask first.
How do we know a store actually completed the routine?
Can the same job be scheduled across every site at once?
Where do requests from site actually go?
Does Noots talk to our EPOS or stock system?
Open a workspace that already knows Retail & Multi-site Operations.
Answer what your organisation does, review what gets installed, and start with the boards, meetings, chat and calendar already in the right shape.
Free to start · No credit card required