COGS dashboard
Location performance
| Location | Brand | Sales KWD | Food % | Bev % | Waste % | Non-food % | Staff % | Source |
|---|
Sales by location
Upload sales mix
MC/POS export — all locations in one file. Upload by 9:00 AM for the previous day.
Expected columns: Location Name · Business Date · Menu Item Name · Major Group Name · Family Group Name · Sales Net VAT after Discount · Sales Count
Daily purchases entry
For the previous business day
Food in
Labour
QIRD register
| Doc no. | Date | Location | Type | Item | Severity | Status | Age |
|---|
Daily Oracle upload
Oracle "Daily Operations" report — one file, all locations, yesterday, by 09:00. Loads sales, guests and checks for every location.
End of day report
Sales, guests and checks load each morning from the Daily Oracle upload. Voids and returns pre-filled from Oracle — the store gives each a reason. Comps typed by check number. FOH and BOH sign-off.
Optional. Sales, guests and checks arrive automatically from the Daily Oracle upload (by 09:00). Upload a single-store System Financial or Serving Period Financial here only if you have Oracle access and want that store's own voids and day-part split. An all-locations file is refused here.
Quarterly budget
Sales and cost targets per location, per month — uploaded by Admin / Finance before each quarter starts. Every KPI is judged against these.
24 September updates
Street group · Support Kitchens · Sous Chef budget line · new MC usage groups. Preview first; nothing is written until you press Apply.
Cost imports
Oracle MC purchase, transfer and wastage reports. The file type is detected automatically.
One file covers every brand — purchase, transfer and Usage (wastage) alike. Each row goes to its own
location, read from the cost centre in the file. An old single-location Usage export (no cost-centre column) still works
and asks for its location. Re-importing a date range replaces it, so a line corrected in MC is never counted twice.
Validation never writes anything.
Coverage — what is actually stored
Import history
| Imported | Report | File | Covers | Rows | Value KWD | Warnings | By |
|---|
Brands and locations
Group → brand → location. Deactivate rather than delete — history depends on these records.
Brands
| Brand | Short | Group | Accent | Locations | Status |
|---|
Locations
POS name must match the Sales Mix export string exactly, or that location's rows are skipped on import.
| Code | Name | Brand | POS name | Enfinity dept | Revenue | MC source | Status |
|---|
Roster
Weekly schedule · drafts are private until you publish
Leave
Roster setup
Shift patterns, annual leave entitlement and public holidays
Designations
Employees
Manpower
Budgeted headcount against who is actually on strength, by location and position.
Budget
Headcount, rate and labour cost as a share of revenue. Restricted to corporate leadership.
Requisitions
Asking for a person, checked against the budget before it is sent. BOH approves up the chef line, FOH up the operations line — the two never cross.
Candidates
One board per vacancy, from applied to joined. Personal data — who sees a candidate is decided record by record, not by role alone.
Joiners
Offer to first shift. Two clocks, never blended: time to hire is ours, time to deploy is the ministry’s.
Adverts & job descriptions
One description per position, six ways to publish it. No advert ever carries a pay figure — the rate is shown once, on corporate approval.
Targets
Per-location KPI targets. Applied to dashboard status colouring.
| Location | Food cost % | Wastage % | Non-food % | Staff cost % |
|---|
Access control
Invite someone
The person signs in with this email and sets their own password. Nobody else ever sees it. Access applies automatically on first sign-in. No email is sent automatically — once issued, you get a ready-made message to copy, email or send on WhatsApp.
Linking means access is withdrawn automatically when they are marked as left.
Pending invitations
| Name | Role | Scope | Issued | Status |
|---|
Active accounts
| Name | Role | Division | Scope | Status |
|---|
Reference — valid values
Alerts
What needs you now — raised by the rules in Setup → Alert rules. Acknowledge stops the clock; resolve closes it.
Daily brief
The whole of yesterday, detailed but summarised — built at 06:00 for every location, brand and the group.
My scorecard
Your KPI score this month, each KPI with its figure, target and the records behind it.
Audits
QA quarterly · Operations monthly · Culinary monthly — uploaded from SafetyCulture PDFs.
Action plans
Every failed audit answer, on FSM 125: non-conformance, root cause, action, by whom, time frame.
Guest feedback
Compliments, complaints and suggestions entered in the EOD — by location, category, dish and source.
Food safety
Hygiene App records: completion, out-of-range readings, verification and weekly sign-off. PDFs for Baladiya.
Team scorecards
Everyone below you in the org chart — red, amber, green.
Org chart
Seats, reports-to, holders and acting cover. Decides where approvals, escalations and alerts go.
Hygiene setup
Per location: chillers, freezers, hot-holds, fryers, sections and stations — and staff PINs for the Hygiene App.
Checklist templates
Opening and closing checklists: master list → brand selection → Food Safety Manager approval → locked.
Alert rules
What raises an alert, who is told first, and how long before it goes up a level.
KPI settings
KPI weights per role (must total 100%), shadow month and freeze day.
System check
Confirms the rules, indexes, server jobs and settings are live — press Run after every deployment.
October updates
One-time setup for R2–R5: default settings, alert rules, KPI weights, checklist master list. Preview first.
Reference lists
Controlled values used across QIRD, feedback and voids.