This guide covers what to record in a Menu Item Costing Register, why a spreadsheet eventually falls over for this kind of tracking, and how to keep the data reliable as the list grows.
What you record
Fields in the Menu Item Costing Register
Every record in this register captures the fields below — 3 of 5 are mandatory, and a record can't be saved until they're filled in.
-
Menu item
Required
- Margherita Pizza
-
Ingredient cost ($)
Required
- 3.20
-
Sale price ($)
Required
- 16.00
-
Food cost (%)
- 20
-
Last reviewed date
- 15/01/2026
Where spreadsheets break down
How spreadsheet registers fail
None of these need malice — just a busy team and a file with no safeguards built in.
-
✕
No change history — there's no way to prove a row wasn't edited after it was first entered.
-
✕
Incomplete records — a row can be saved half-filled, and the gap often isn't caught until you need it.
-
✕
Version conflicts — two people work from different copies, and the "final" file quietly drops recent changes.
-
✕
Silent formula errors — a dragged formula or broken reference changes data without anyone noticing.
-
✕
No access control — anyone with the file can edit or delete any row, with no record of who did it or when.
-
✕
Lost institutional knowledge — the person who maintained it leaves, and the file (or how to read it) goes with them.
Launch this register
No setup, no configuration required. TidyRegister ships with the Menu Item Costing Register ready to go.
Common questions
Frequently asked questions
Who normally maintains the Menu Item Costing Register?
Supplier invoices and the point-of-sale system.
Can I import my existing spreadsheet into the Menu Item Costing Register?
Yes — upload your CSV and its columns are matched to this register's fields automatically.
Can I export my data out of the Menu Item Costing Register?
Yes, at any time, as a CSV — there's no lock-in.
What does the Menu Item Costing Register cost?
TidyRegister is $3/week per register, with unlimited records, users and sites.