Inventory Control
Catalogue, stock, warehouses, purchase orders, suppliers, sales, cycle counts and valuation, on one append-only movement ledger.
Next.js · TypeScript · PostgreSQL · Tailwind
Explore
From $649
TodayColleague1 / 6
Business OperationsRetailLive
Retail Store Ops
Head office sends tasks, stores do them, and nobody can prove either. This build gives each store one list, one cash-up and one stock check, and gives head office the answer without a phone call.
- From
- $649
- Function
- 22
- Roles
- 3
- Users
- Unlimited
Next.js · TypeScript · PostgreSQL · Recharts
Inside the app
What it does out of the box
22 connected functions on one schema, spanning three permission levels. Everything below is in the template before a line of customisation.
Dashboard for Sara
Riverside branch - 11 tasks today, 3 stock checks and yesterday's cash-up was short.
Tasks
What head office sent, what recurs daily, and who actually did it.
Stock checks
Counted blind, with variance that gets explained rather than absorbed.
Cash-up
Counted, declared and reconciled to the till. Variance needs a reason, not a shrug.
Branch sales
Against plan and against last year, by branch and by day part.
Labour
Hours scheduled against sales, so cover matches trade rather than habit.
Branches and templates
Which tasks recur where, and what evidence each one needs.
Audit log
Every variance, override and template change. Retained for seven years.
Permissions
Three roles, one build
A colleague sees one list for the day. A store manager sees the branch. An administrator pushes work to every branch at once. The point is that head office can prove what was asked and what was done.
Colleague6 functions
One list, one store, one day
- Today's tasks in one list, whatever sent them
- Complete checks with photo evidence
- Count stock blind, without seeing the system figure
- Run the cash-up and record a reason for variance
- Cannot close an unexplained variance alone
Store Manager14 functions
The branch, and where it leaks
- Everything a colleague can do
- Sales against plan and last year
- Shrinkage by branch and by area
- Approve stock and cash variances
- Match labour cover to actual trade
Administrator22 functions
What every branch does, and when
- Everything a store manager can do
- Push a task to every branch at once
- Set evidence requirements per task
- Define escalation when tasks are missed
- Read and export the audit log
The build
Every function in the box
22 functions, all of them live in the preview. Nothing on this list is a mockup or a roadmap item.
Access
- Sign in
In store
- Today
- Tasks
- Stock checks
- Cash-up
Branch
- Branch sales
- Labour
Administration
- Branches and templates
- Audit log
What you get
Delivered as a repository, not a login.
Multi-site retailers and hospitality groups running 3 to 300 branches.
- 9 production functions spanning three permission levels
- Full source code and PostgreSQL schema in your repository
- Role-based access control, enforced server-side
- Immutable audit log written on every change
- Responsive layouts, usable on a phone, not just resized
- CSV import and export on every core record
- Deployment configuration for your cloud account
- Twelve months of updates, and no per-seat charge ever
Access and evidence
Where retail leaks
Shrinkage rarely announces itself. It shows up as a cash-up that is quietly a little short, a stock check nobody counted properly, and a task marked done without evidence. Each of those has a control here.
- Stock counted blind, the counter never sees the system figure first
- A variance above threshold cannot be closed without a reason and sign-off
- The approver of a variance cannot be the person who counted
- Tasks requiring photo evidence cannot be marked done without it
- Cash-up runs daily on close, with expected reconciled to counted
- Branches behind plan and high on shrinkage are surfaced together
- Immutable audit log with seven-year retention and export
Related
Apps that pair with this one
Order Management
A full order management system: orders, customers, catalogue, stock, warehouses, shipping, returns, automation rules and integrations.
Next.js · TypeScript · PostgreSQL · Tailwind
Explore
From $699
Employee Hub
Announcements that require an action, tracked per employee, with reach reporting for managers.
Next.js · TypeScript · PostgreSQL · Auth.js
Explore
From $649
Questions
Retail Store Ops, in practical terms
Do I get the source code for Retail Store Ops?
Yes. The repository, application code, database schema, migrations, seed data and deployment configuration, is transferred to your organisation on delivery. There is no licence key and nothing that calls home.
How many branches can it run?
As many as you like, pricing is per application, not per branch or per colleague, which is the usual way store systems become expensive as you open sites. Every colleague can have their own login, which is what makes the audit trail worth anything.
Is this a till system?
No, and that is deliberate. It reconciles to your till rather than replacing it. Point of sale is a specialist, hardware-bound problem with payment certification attached; a fitted build integrates your existing till so takings flow into the cash-up automatically.
Does it work on a tablet behind the counter?
That is the intended device. The colleague screens are built for touch and work offline, because stockrooms and back offices are exactly where the signal drops.
Can Retail Store Ops be changed to match our estate?
That is the usual route. A fitted build sets up your branch structure, task templates, evidence rules, variance thresholds, till integration, branding and up to two integrations, and typically takes one to three weeks from a signed scope.
What does it cost to run?
Hosting only, paid to your own cloud provider, roughly $50 to $200 a month, rising with branch count and how much photo evidence you retain.
Want Retail Store Ops shaped around your process?
A fitted build adjusts fields, stages, roles and integrations to how your team already works. One scoping call, a fixed price, one to three weeks.
