Product and Modifier Performance

Overview

• Product Performance measures base Products and intentionally excludes modifier selections from Product quantity/sales to avoid double counting.
• Product rows include quantity, gross/net sales, discounts, refund quantity/value, average item price, and percentage of sales.
• Top Products can show recognised sales split across Store, Online, and Marketplace channel groups.
• Low sellers are surfaced separately.
• Modifier Performance tracks Modifier selection count, paid modifier sales, free selections, selection rate, and related top Products.

When to use this

• Use Product Performance for menu-item decisions and Modifier Performance for choices/add-ons such as bagel type, spreads, toppings, or paid extras.

Step-by-step

1. Set the report period and Store.
2. Review Product quantity and Net sales first.
3. Use refund/discount fields before concluding an item is strong or weak.
4. Open Modifier Performance to analyse option attachment separately.
5. Compare with Menu Profitability before changing the menu solely on sales volume.

Common mistakes

• Do not add Modifier paid sales to base Product performance without understanding the overlap.
• Do not interpret a high free-selection count as revenue.
• Do not remove a low-volume Product before checking margin, affinity, and strategic role.

Troubleshooting

• If a Modifier does not appear, confirm it was saved on eligible recognised orders in the period.
• If Product sales seem different from item-line totals elsewhere, check recognised-payment allocation/refund semantics.