UnitOps Documentation
UnitOps gives restaurant and retail operators a daily, mobile-friendly, AI-assisted view of every store: sales and labor forecasts, dashboards, alerts, and a chat assistant grounded in your own data.
These docs are written as step-by-step instructions. Every setting described here can be configured from the UnitOps web app by following the steps on the page - no engineering ticket required.
Where to start
| If you are... | Start here |
|---|---|
| Brand new to UnitOps | Getting Started |
| An admin setting up a new organization | First-time setup checklist |
| A General Manager building your first forecast | Weekly sales forecast |
| Connecting Slack, email, or SMS | Connect your apps |
| Building analytics | Custom dashboards |
| Configuring alerts | Notifications overview |
| Looking up a term | Glossary |
What UnitOps does
- Sales forecasting - weekly projections at 15-minute resolution, generated from your history with selectable projection models, then reviewed, adjusted, approved, and published.
- Labor forecasting - a staffing plan derived from the published sales forecast and your labor matrix, with hours, headcount, cost, SPLH, and overtime, exportable to your scheduling system.
- Actuals and variance - enter or import actual sales and labor, then measure forecast accuracy day by day.
- Dashboards - built-in operating dashboards plus YAML-defined custom dashboards you can publish and embed.
- AI assistant - ask questions about your data in the app or from Slack and Teams, grounded in your KPIs and indexed documents.
- Alerts and notifications - rule-based alerts delivered in-app, by email, web push, Slack, Teams, or SMS, with role defaults, per-user overrides, and quiet hours.
Environments
| Environment | App | Docs |
|---|---|---|
| Production | https://unitops.datalakehouse.io | https://docs.unitops.com |
| Staging | https://dev-staging-unitops.datalakehouse.io | https://unitops-docs-staging.pages.dev |
Staging mirrors production and is the safe place to try a configuration change before you make it live. See Environments and deployments.