Skip to main content
On this page you will learn about all the metrics and KPIs available in Delicious Data. We explain how each metric is calculated and what insights it can provide for your business. By the end, you’ll understand which metrics to use for different business questions and how to interpret them correctly.

Units

For currency based metrics (Revenue, Cost of Goods Sold, etc.), the currency is defined in the global settings and applies company wide to all locations. For count based metrics (Sales No., Planned No., etc.), the unit is the same as in the source system. For example:
  • If the item is sold in pieces and Sales No. = 12.0 then 12 pieces were sold.
  • If the item is sold in kg and Sales No. = 3.2 then 3.2 kg were sold.
Sometimes integration specific unit conversions are necessary. Check out our integration documentation for more details on your integration.

Transactional vs. Aggregated Sales Data

There are two ways we can process sales data:
  1. Daily Aggregated: Summary of your daily totals per item and location
  2. Transactional: Detailed data for every single sale including time, items and locations
Most features work fine with aggregated data, but processing transactional data allows us to generate more powerful insights and metrics in your BI dashboard.
Check out our integration documentation to see if your ERP system offers transactional data or if an additional POS integration would be required.

Sales Metrics

All metrics related to sales coming either from the POS or the ERP. Sales metrics can be grouped & filtered by Location, Location-Tag, Item Offering Groups, Item, Item Groups, Item-Tag, Time (down to hourly level for transactional data, otherwise daily).
The total gross revenue generated from sales.
The total number of items sold.
The average price per item sold.
It is calculated on the fly for the chosen aggregation level in the report and does not reflect a reference or valuation price of the item:Ø Price = Total Revenue / Total Sales No.
The total number of transactions processed.When filtering or grouping by Item, Item Groups or Item-Tag this metric will only reflect the number of transactions which included the respective items.
This metric is only available with transactional data.
The average revenue generated per customer transaction.When filtering or grouping by Item, Item Groups or Item-Tag this metric will only reflect the average revenue per transaction of transactions which included the respective items.
This metric is only available with transactional data.
All metrics related to menuplanning. Menuplanning metrics can be grouped & filtered by Location, Location-Tag, Item Offering Groups, Item, Item Groups, Item-Tag, Time (daily level only).
The planned number of portions or items to be produced for a specific menu item or dish.
The forecasted quantity of portions needed, calculated using predictive analytics and historical sales data.
Cost of Goods Sold represents the direct costs associated with producing menu items, including raw materials and ingredients.
The Cost of Goods Sold expressed as a percentage of the selling price. This metric helps evaluate profit margins and pricing strategies for menu items.

Food Waste Metrics

All metrics related to returns, write-offs and depreciation. Returns and depreciation metrics can be grouped & filtered by Location, Location-Tag, Item, Item Groups, Item-Tag, Time (daily level only).
The quantity of items that were marked as depreciated or written off.
The monetary value of all depreciated items.
The quantity of items that were returned.
The monetary value of all returned items.
Depending on the configuration this is the percentage of items that were returned relative to
  • total delivered items or
  • the total sold items.
This is the return amount rate weighted by the value of the items.
This metric is recommended over the return amount rate as it weighs expensive items more heavily than cheap items when aggregating over different items.
For the “value” metrics typically a reference or valuation price is used from the ERP system, but sometimes the average price is also used. Check out our integration documentation to see which case applies to you.