Product Price Sensitivity
Product Price Sensitivity scores how closely the quantity customers buy of a product moves with its unit price across your orders. A high score means orders at a lower unit price tend to hold more items.
How It’s Calculated
Each row is one product. The columns are:
- Product: the product’s name and image.
- Orders: the number of orders that include the product.
- Avg Unit Price: the product’s average unit price across those orders, before discounts.
- Price Stddev: how far those unit prices spread around the average. It is 0 for a product whose price never changed in the range.
- Sensitivity: the score, from -1 to 1.
- Level: High at a score of 0.35 or more, Medium at 0.15 or more, and Low below that.
For each order, the report takes the product’s unit price and the number of items bought. The Sensitivity score is the opposite of the correlation between those 2 numbers across all the orders.
A score near 1 means orders with a lower unit price held more items. A score near 0 means the 2 numbers aren’t related. A negative score means orders at a higher unit price held more items.
A product whose price never changed has no correlation to measure. It scores 0 and shows Low.
The unit price is the product’s price before discounts.
A product appears only if it has at least 10 orders in the date range. The table lists up to 500 products, with the highest score first, then the most orders.
What Counts
- Orders that were canceled, or whose payment was voided or expired, don’t count.
- Refunds and returns aren’t taken off.
- Dates follow your store’s time zone, and amounts are in your store’s currency.
- With a Segment picked, only orders from customers in that segment count. Sales Channel and Filters limit the report to matching orders.
This report has no Compare control, no chart and no totals row.
What Good Looks Like
There’s no target, and the score isn’t proof that a price change moves demand. It only describes your past orders. A product with a lot of price changes and many orders gives the clearest read.
Treat a High level as a reason to look closer, not as a result. Check Price Stddev first. A very small spread means the score rests on tiny price differences.
What to Do About It
- A High product: look at the orders behind it before you change its price. If the score comes from multi-item orders, it may say more about bundles than about price.
- A Low product with a wide Price Stddev: its price moved and quantities didn’t follow. It may take a price change without losing orders.
- A Low product with a Price Stddev of 0: the report can’t tell you anything yet. Test a price change, then run the report again.
Promotion Efficiency by Product shows how much of each product’s sales come from discounts.
Get AI Insight at the top of the report asks Copilot for a short read of it.
Where to Find It
- Product Price Sensitivity: open Reports and look under Products.