Head office decides once. Every store answers back.
The job went out by email, most sites replied in some form, and nobody can say which ones never opened it at all. Store puts the return leg on the record: every rollout carries a per-store receipt, and seen it and done it are two different facts that the roll-up refuses to add together, because a store working on it needs a different phone call from a store that does not know the job exists. It gives the shop floor a route upward that lands as a real card on the head-office board, turns a district manager's walk into photo-attached corrective actions with owners and dates, and puts the whole estate side by side with the silent stores named. Choose Retail & Multi-site Operations at setup and the Store tab, the routines, the request queue and the shift patterns are queued for every site.
9 apps queued at setup - untick any of them before you finishDefault project tabs
Gantt replaces Timeline - a store opening and a seasonal reset are dependency chains ending on a date that cannot move - and Goals carries the 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 opens on what head office actually asked for
Head office's own list sits on the store's tab, under From head office: what this store has been asked to do, and what it has already sent back. The manager presses Seen it, and later Done here with a line about what happened, or Cannot do it with the reason. Those are separate facts and they stay separate: a store that acknowledged on Monday and has not finished is working on it, and a store that has acknowledged nothing may not know the job exists. Alongside it the written store-open routine runs as a checklist, every step ticked with the name of whoever ticked it, and the five minutes before the doors open are kept as this shift's huddle.
11:40
the chiller is broken, and the shop floor can say so
Tell head office is the lane most estates simply do not have. A member of store staff raises it once, with photos, and it becomes a real card on the head-office board titled with the store's own name, not a note in somebody's phone. It cannot be closed as resolved or declined without a sentence saying what happened, and the person who raised it is told. Separately, Intake is the front door for the ordinary asks - a signage error, an IT request, a maintenance job - each with a category, a priority and a named owner.
15:20
the walk ends in owned fixes, not in a report nobody reopens
A visit or an audit runs its checklist line by line, and anything found is photographed, dated and given a severity. A finding that needs fixing becomes an ordinary board card with an owner, a due date and a priority that follows the severity, so next month's walk does not re-find it in a document. Across the estate then reads every store on the same jobs side by side: how many have acknowledged, how many have finished, how many are blocked, and by name, the ones that have said nothing at all.
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.
Store
One tab per site: the store profile, what head office has asked for and what came back, the lane for telling head office what is broken, visits and audits, shift huddles, and the whole estate side by side.
- Per-store receipts, with seen it and done it kept apart
- A route from the shop floor to the head-office board
- Visits and audits that end in photo-attached corrective cards
- An estate roll-up that names the stores which said nothing
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
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.
- The Store tab is the site itself: store number, region, manager on duty, staffing and seasonal hours; the address with a link that opens it in whichever maps app is on the phone; who is on shift and in what role; and the planograms, campaign packs and manuals filed against it, narrowed to the campaign you are running
- Store updates is the store's own channel rather than a second message store, so what happened here reads newest first, notifies the people on it and is searchable with everything else
- Recurring Tasks put the same job on the same date at every site, created, assigned and dated automatically, so a seasonal reset lands the same week everywhere without anyone chasing it
- The Shift-Based Scheduler compiles the rota from patterns - early, late, the doubled weekend - and the availability checker, Autopilot and the presence dot all read it; Team Availability is the board where people post leave and part days on top of it
- Announcements reach every site at once, pin to the top of everyone's home screen when they matter and come back acknowledged by name; the Policy Library holds the store standards with an effective date
- The Ledger is a register of every fixture, device and licence - who holds it and where it lives; the Goals tab on every project carries the per-site targets side by side, and Hoot draws a chart or a whole dashboard over the boards when you ask for one
- Gantt is the default plan tab, because a store opening and a seasonal reset are chains of dependent jobs ending on a date that cannot move, and Hoot can draft one from a description you type before anybody drags a bar
- Shift handovers, store walks, supplier calls and team huddles each get their own steer on the recorder, and the actions land with an owner and a real start and due date taken from what was said
- Offered at setup, one tick each: the Hard-Dependency Gantt so a slipped fit-out moves the launch behind it, the Vendor & Client Register for suppliers and their contract dates, the Content Calendar for the campaign, Expense Claims, Budgets and the Corkboard for the staffroom wall
- Automations fire on a due date or a status change and post to the channel that cares
The honest edges.
- Acknowledgement and completion are recorded because a named person pressed a button in Noots. There is no photo verification and no location check behind either of them, and a checklist run proves a named person ticked each step and nothing more.
- The Store tab reads from cache when the connection drops and every control says plainly that a write needs one. The offline write queue in Noots is the construction variant's daily log, not this one.
- There is no merchandising module. Planograms, signage and campaign packs are files in the store's documents bin, narrowed to the folder whose name matches the campaign, and a shift huddle is a checklist rather than a recorded meeting.
- The store's location card shows the address and a link that opens the place in your own maps app. A drawn map is off until somebody turns it on, and the OpenStreetMap option says in the setting itself that it sends that store's position to openstreetmap.org on every render.
- 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.
- The Shift-Based Scheduler compiles a rota from block and rotation patterns an admin sets. It does not clock anyone in or out, hold leave balances or feed payroll, and Team Availability on top of it records what people post about their own week.
- 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 which stores actually did the job?
What happens to the stores that ignore it?
Can store staff tell head office something is wrong?
What does a store visit produce?
Does it work in the stockroom with no signal?
Does Noots talk to our EPOS or stock system?
Does it do the rota?
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