Step 1: Define the question and reporting period
What to do: Decide whether you are investigating supplier price changes, SKU costs, outlet differences, or actual profit per menu item. Set a clear period and document which locations are included.
Success looks like: The team can state exactly what is being compared, for which dates, and across which outlets.
Caution: Do not describe a purchasing-cost comparison as dish-level profitability if sales and recipe data are not included.
Step 2: Gather documents from every included outlet
What to do: Collect supplier invoices, delivery notes, receipts, and relevant bank activity, keeping the outlet and document date identifiable. Confirm that the chosen period is not missing a location’s records.
Success looks like: Each record can be associated with a supplier, date, and outlet where those details are available.
Caution: Combining files without outlet labels can make later comparisons unreliable.
Step 3: Extract and structure supplier line items
What to do: Capture available product or SKU descriptions, quantities, unit prices, tax, supplier, and outlet details from invoices and delivery notes. Preserve the link to each original document as the records are processed.
Success looks like: The extracted rows show meaningful item-level fields and can be traced to the source file.
Caution: Do not assume every scan or handwritten description was read correctly; check ambiguous fields.
Step 4: Code transactions and reconcile related records
What to do: Organize transactions into the appropriate accounts and compare available invoice, payment, and bank information. Investigate duplicates, unmatched items, and differences in amounts or dates.
Success looks like: Exceptions are visible, assigned for review, and resolved or clearly documented.
Caution: A matching total does not prove that each extracted line item or outlet assignment is accurate.
Step 5: Review supplier, SKU, and outlet cost patterns
What to do: Compare costs across suppliers, products, or locations only when the relevant fields are present and configured consistently. Investigate apparent changes using the related invoices and delivery notes. A multi-outlet cost analysis can help structure that review.
Success looks like: You can identify which records support a cost difference and distinguish verified changes from data gaps.
Caution: Different units, pack sizes, or product descriptions can make an unnormalized price comparison misleading.
Step 6: Validate the conclusion before changing the menu
What to do: If you need profit by menu item, connect validated purchasing costs with relevant sales and recipe or ingredient mapping. Confirm that the period, units, and menu definitions align, then have a qualified reviewer examine exceptions and assumptions. For context, compare restaurant margin drivers with the underlying evidence.
Success looks like: The reported measure has a clear definition, usable inputs, and a documented path back to source records.
Caution: Do not make pricing, recipe, or menu decisions from incomplete sales, recipe, or supplier data.