On this page
KPI import brings in data HQ already receives, so owners log less and the rollup reflects what happened.
How imported values are used
Each objective’s metric definition has a source: manual check-ins, or an import. Imported values arrive as check-ins marked as coming from an integration and flow through the same path as everything else:
- They update each unit’s assignment status against the met, at-risk and missed conditions.
- They feed the KPI baseline, current value and change in the rollup.
- They appear on the owner’s priority with the source labelled, so the owner can see where a number came from.
Imports carry unit-level aggregates only, such as a unit’s average ticket for a period, or its repeat-customer rate. SignaUnit doesn’t import per-employee rows, staff rosters, shift data or anything that would rank individual employees.
CSV import
CSV import is part of v0.1. It’s designed to be run by HQ from data it already has, rather than asking each owner to upload a file.
- Upload a CSV export from your reporting, POS, CRM or accounting system.
- Map columns. Tell SignaUnit which column holds the unit code, the period or date, and the value for each metric. Mappings are saved so the next import is one step.
- Preview (dry run). SignaUnit validates every row and shows what would be saved: matched units, values, and any rows it can’t use, with the reason (unknown unit code, a date outside the period, a non-numeric value).
- Confirm. Only then are values saved. The import is recorded with counts of rows saved and rows skipped, and who ran it.
Uploaded files are read for the import and are never kept in a code repository.
Tips for clean imports
- Use the unit code from your roster as the key. Names drift; codes don’t.
- Include a period column (a month, or a date range), so re-importing the same period updates values instead of duplicating them.
- Import a baseline period before launch, so KPI change has something to compare against.
- Keep one metric per column. Percentages as numbers (for example 72.5), not text.
QuickBooks Planned
A QuickBooks connector is planned for the release after v0.1. It’s for profitability priorities: revenue and margin measures at the unit level, pulled on a regular cycle once an owner or HQ connects the account. It removes the need to export and re-import financial figures.
Field-service / operations connector Planned
One field-service / operations connector is planned alongside QuickBooks, chosen with the first brands we work with based on what their units use. It covers conversion and customer follow-up measures, such as close rate and repeat-customer rate, as unit-level aggregates.
It will not pull staff rosters, individual calendars or per-employee performance. Those are inputs, not outputs, and they belong to the owner.
How connectors will work
Planned connectors follow one pattern:
- Connect with OAuth or an API key. Credentials are held in a secrets manager and never stored in the database in plain text.
- Pull on a regular cycle, and through webhooks where the source supports them, for a defined time window.
- Map source fields to a priority’s metric once, then run automatically.
- Show the source on every imported value.
For connectors beyond these, including lead sources and call tracking, CRMs, POS, reviews and P&L, see the Integrations roadmap.
Manual check-ins as a fallback
Manual check-ins stay available for anything that isn’t in a system yet, like confirming that an offer launched. When a metric can come from an import, prefer the import. Weekly recurring priorities are only available for imported metrics, so owners are never asked to fill in a weekly form.