Heatmaps
Color every product on the shelf by sales, margin, or any metric you track, so winners, laggards, and misallocated space stand out at a glance.
local_fire_department Heatmaps color each Position in a Plan by its value, from red for the lowest to green for the highest, through yellow. The colors can be changed for each heatmap.
Heatmaps in a Line Review
A heatmap turns a shelf into an argument. Whether you are proposing a reset or approving one, it shows what is earning its space before anyone opens a spreadsheet.
- Make the case for more facings. Color by sales, and a top seller squeezed onto a single facing stands out against slower items with more room.
- Find the bottom sellers first. Rank items to color the bottom 20%, then propose swap_horiz replacements before a buyer asks for cuts.
- Set a pass/fail bar. A fixed range, such as anything under $500 a week in red, shows at once which items miss your threshold.
- Use the account's own numbers. Load analytics Store Data to color by a retailer's or a store cluster's sales rather than national averages.
Using Heatmaps
Heatmaps are edit Customizable, and can be bound to any data or calculate Calculation, including catalog data, Dynamic Fields, or more granular analytics Store Data. To customize Heatmaps, click the edit button beside the dropdown.
Open the Heatmap panel from View → Heatmaps, and choose the current heatmap from the Heatmap dropdown. The panel shows the heatmap's statistics along its color gradient: Minimum, Average, Maximum, and a marker for the Median. Blue, which isn't on the gradient, means no value: the heatmap's value for that product isn't a number, or in a Store Plan, there are no products in that part of the bay.
You can also ask query_stats Smart POG for one, such as "Show me a heatmap of weekly sales." It colors your plan right away as an unsaved heatmap, which you can Save to keep or Discard.
In a Store Plan, a heatmap colors bays instead of individual products: slices
of each bay (12 in or 30 cm long, or as long as you set), or whole bays,
Aisles or sections, as Color by in the Heatmaps panel says. So its
expression must be an aggregate, such as Sum or Avg.
It is common to use a Heatmap in conjunction with edit_note Labels, so colors and numbers can be seen together.
Relative vs Fixed Ranges
A Heatmap's range may be Relative (default), or Fixed.
A Relative-Range Heatmap colors the item with the lowest value found the "Minimum Color" (default red), the item with the highest value found the "Maximum Color" (default green), and everything else in between.
A Fixed-Range Heatmap lets you set a lower bound, an upper bound, or both. Anything under or over the bounds gets the minimum or maximum color. Fixed-Range Heatmaps suit pass/fail metrics, for example identifying items performing under a set threshold, such as a number of turns or dollars per week.
Heatmap range can be edited in the Customize Heatmaps dialog, by clicking the settings_ethernet button, then checking the Min and/or Max checkboxes, and entering minimum / maximum range values in the inputs.
Ranking Items (e.g. Bottom 20% of Sellers)
To color items by how they rank rather than by their raw values, use the PercentRank Calculation function, which
ranks each item in the Plan from 0 (lowest) to 1 (highest). For example, an
expression of PercentRank(#Sales) with a Fixed Range
of 0.2 to 0.8 colors the bottom 20% of items with the minimum color, the top 20%
with the maximum color, and everything else in between.
Because ranks are relative to each Plan, every Plan will show roughly the same share of each color. Use raw values instead when comparing performance across Plans or stores.
Heatmap Colors
Heatmap colors may be customized by clicking the palette button in the Customize Heatmaps dialog. This lets you set custom colors for Minimum, Midpoint, and Maximum values. If a Midpoint color is not set, it is automatically calculated from the Minimum and Maximum colors.