A modifier is an option attached to something you sell — a shot of syrup in a coffee, cheese on a burger, a mixer with a spirit. The POS Order Modifiers report lists those choices individually, so you can see which options customers actually pick and what they add to your takings.
This article assumes you already know the basics of the Sharper reporting module — the Name, Token, Subtotal, column picker, and filter fields. For a full walkthrough of the reporting form itself, see the Sharper Reporting Reference Guide. This article only covers what's specific to Order Modifiers.
Why This Report Matters
Modifiers are invisible on every other report — they change what a customer pays but never appear as products in their own right. That makes this the only place to answer some genuinely useful questions:
Which options are popular enough to keep stocking, and which are never chosen
How much revenue paid modifiers actually add
Whether a modifier group is set up correctly, by seeing what comes through it
What free-text notes staff are adding to orders, which often reveals a missing modifier
How Modifiers Are Organized
The report exposes the full structure behind a modifier, which is more detail than most people expect:
Column | What It Shows |
Modifier Section | The broadest grouping the modifier sits in |
Modifier Group | The set of choices it belongs to — for example "Milk" or "Sides" |
Modifier Prefix | The qualifier applied, such as "Extra" or "No" |
Modifier Name | The choice itself |
Modifier Full Name | Prefix and name together, as it reads on the ticket — usually the most readable column to group on |
Grouping on Modifier Name alone merges opposites — "Extra cheese" and "No cheese" both have the name "cheese" and will be counted together, which is exactly backwards for stock planning. Group on Modifier Full Name so the prefix is included and the two stay separate.
Counting Modifiers
There are two count columns, and they answer different questions:
Modifier Count — how many of this modifier were applied to the item
Modifier Ext Count — the extended count, taking the quantity of the underlying item into account. Three coffees each with an extra shot is three shots, not one.
For stock planning — how many shots of syrup you actually poured — Modifier Ext Count is the one you want.
Building an Order Modifiers Report
Go to Reports → Point of Sale → Order Modifiers in the left sidebar.
If a shipped report is close to what you need, use the ⋯ menu → Copy first — shipped reports can only be edited by the Sharper team.
Otherwise click + New and give it a Name, such as "Modifier Popularity."
Add the columns below from the Available panel.
Set Subtotal to Modifier Ext Count or Modifier Price.
Turn on Summarize Report for a ranking rather than every individual modifier.
Click Save, then Get Report to set a date range and run it.
Other Useful Columns
Field | What It Shows |
Modifier Price | What the modifier added to the price. Zero means it is a free choice rather than a paid upgrade. |
Order Item Name | The item the modifier was applied to |
Order Item Quantity | How many of that item were sold on the line |
Order Item Note | Free-text notes staff typed on the item. Reviewing these regularly is the best way to find requests common enough to deserve a real modifier. |
Product Name, Product SKU, Income Account | The underlying product and where its revenue posts |
Order, Order Date, Order Time, Order Hour | The order and when it happened |
Order Status, Voided By, Void Reason | Whether the order completed — include the status on anything you total, since voided orders are present |
Register Name, User Display Name | Where and by whom the sale was rung |
Customer Name, Cust Type | The customer, where the sale was attached to an account |
Useful Filters
Most popular options: group by Modifier Full Name, subtotal on Modifier Ext Count, completed orders only.
Revenue from paid modifiers: Field Modifier Price, operator >, value 0, subtotalled on Modifier Price.
Free choices only: Field Modifier Price, operator =, value 0 — useful when reviewing whether something should be chargeable.
One modifier group: Field Modifier Group, set to the group, to see how the choices within it split.
Notes worth turning into modifiers: Field Order Item Note, set to is not empty.
Modifiers on one product: Field Product Name, set to the product.
The notes filter is the one most operators find unexpectedly useful — a request that keeps appearing as typed text is usually one worth adding as a proper modifier, which speeds up service and captures the revenue.