Direct answers before you choose a path.

OneCount is the product owner for hospitality inventory, catalogue, stock-count, supplier-invoice, pricing and costing records. The web path prepares the workspace and exposes available review surfaces; the public site does not claim that count entry or invoice capture begins there.

No. Ops, Shield and Trace are in development. Their public pages use representative previews and one OneCount early-access list; they do not present store downloads or live cross-product workflows.

OneCount owns inventory, catalogue, pricing and costing. Ops owns recipes, training, tasks, execution and handovers. Shield owns compliance evidence and audit. Trace owns labels, batches, shelf life, custody and recalls.

The pricing page is the canonical public source for available plans, inclusions and amounts. Other pages link to it instead of copying figures that could drift.

The integrations page is the current status source and separates live, pilot, partnership and planned connections. A named integration is not treated as live unless that page explicitly says it is.

No. Counts, invoice details, item matches, pricing changes, task completion, compliance sign-off and label decisions retain a human owner. Assistance prepares context; the responsible person makes the decision.

Start with organisation and venue structure, roles, a catalogue starting point and locations, then confirm the supported entry or capture handoff for one real workflow. Timing depends on data quality and scope, so OneCount does not publish a universal setup-time promise.

Use the public Support or Contact route. OneCount publishes its support channel and incident process, but does not publish a response-time SLA.