In development · early-access list open
Keep recipes, procedures, tasks and handovers clear.
OneCount Ops is being designed to keep recipes, procedures, training, tasks and shift handovers in one operational workspace. It is not presented as available today.
Best for
Teams closest to this record.
- Chefs
- Supervisors
- Venue/operations managers
- Changing teams
What it owns
The record stays accountable.
This product is accountable for recipes, methods, photos, training, execution, tasks, handovers and operational events.
- Recipes and methods
- Training and sign-offs
- Tasks and procedures
- Handovers and operational events
Capabilities
Only the work this product owns.
Six or fewer verified capabilities keep the product boundary useful and easy to scan.
- Recipes and methods
- Photos and training
- Prep and production
- Daily tasks
- Procedures and execution
- Handovers
Mechanism / outcome
What changes for the team.
The work stays clear across the shift.
Representative preview
See the intended record shape—without pretending it is live.
OneCount Ops is in development. This labelled preview explains the intended workflow and does not claim a live customer surface.
Availability
What you can use today.
In development · early-access list open
- Web
- In development
- iOS
- In development
- Android
- In development
- Reviewed
- 2026-07-12
Limitations
Clear limits before the decision.
- In development; representative previews only.
- No live cross-product write is claimed.
- Completion remains a human action.
Integrations
Connection status, without the logo-wall theatre.
These are OneCount-managed integration states for context. How OneCount Ops reads any connected record remains in development.
Pushes supplier bills — line items and GST included — to Xero as review-first drafts your bookkeeper approves. OneCount never authorises a bill on your behalf.
LiveReads Square sales, read-only, so food cost reflects what actually sold — not just what was counted. Running in a sandbox environment until the first pilot venue goes live.
Pilot programConnects via Doshii, the POS-aggregation layer covering these systems, so sales data reaches OneCount without a POS-specific build for each one. Pilot via Doshii.
Pilot via DoshiiA partner application is underway with Toast. No connector exists yet.
Partnership in progressThe next direct POS build on the roadmap, after the Square pilot proves out.
ComingFamily connections
Keep the owner clear at every handoff.
These are representative boundary examples. Every connection below remains in development and no live cross-product write is claimed.
Representative connection · In development · No live write is claimed.
Ops keeps ownership of recipes, methods, photos, training, execution, tasks, handovers and operational events. OneCount keeps its own record boundary; any handoff requires a separately verified implementation.
Explore OneCountRepresentative connection · In development · No live write is claimed.
Ops keeps ownership of recipes, methods, photos, training, execution, tasks, handovers and operational events. Shield keeps its own record boundary; any handoff requires a separately verified implementation.
Explore OneCount ShieldRepresentative connection · In development · No live write is claimed.
Ops keeps ownership of recipes, methods, photos, training, execution, tasks, handovers and operational events. Trace keeps its own record boundary; any handoff requires a separately verified implementation.
Explore OneCount TraceDecision resources
Read the commercial and trust details.
Early access
Be first to know when Ops is ready.
OneCount Ops remains in development. Joining the OneCount early-access list records this product as your initial interest; it does not promise a release date.