Loading
Because takings, purchases and rotas are three systems that meet in the management accounts six weeks after the period. Food cost percentage for March is genuinely useful in March and merely interesting in May.
By then the supplier price rise, the portion drift or the over-staffed Tuesday have each had a full quarter to compound.
Takings arrive daily from your till, purchases post from bills as they are entered, and wage cost comes from Nest's rosters and attendance. Each is a cost centre per site.
So food cost and labour cost against revenue are current within the week, per site, rather than reconciled in arrears.
It is not a till, a table-booking system or a recipe-costing tool. Recipe-level costing needs a spec, and Books holds purchases and stock rather than portions.
And it will not fix a bad week. It will tell you about it while there is still something to do.
Sites are branches on one set of books, so comparing them is a query rather than an assembly of seven files. A supplier price rise shows up as margin movement in the week it lands.
GST reports and bank reconciliation read the same transactions, so the compliance work is a check.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
Your till, daily, through the API or as a summary.
Yes, from Nest — rostered and actual hours, per site.
Yes, branches are cost centres on one set of books.
Half an hour on your own numbers is usually enough to say whether Books is the right place to start.