Exception reports

Exception reports highlight data that is not following rules already established in the Rules page.

Review these reports to see the exceptions before running optimizations. If many exceptions exist, it may be costly to bring a specific category in line with the desired optimization rules. You can re-review the reports post-optimization to troubleshoot abnormal price changes.

For example, the Size rule is added to the Rules page stating that larger sizes must be priced 5% higher than smaller sizes while larger sizes must be a 5% better value on a per unit basis. The Size Exceptions report will show those products in Size Family/Class relationships which are not adhering to the rule.

If you want to make changes to items in the reports, it is best to make the changes in the relevant informational report, such as the Brand Class and Family report. If changes are made within an exception report at the SKU/Store level, the change will apply to only the SKU/Store and will not be propagated to the entire zone (creating another exception). You would aggregate the informational report at the Line/Zone or SKU/Zone level (if store level uniqueness does not exist).

Note: Exceptions will only display if corresponding rules have been set to Active in the Rules page (for example, no data will be displayed in the Size Exceptions report if the Size rule is not set to Active in the Rules page).

These are the exception reports:

  • Brand Exceptions - Use this report to view or edit products that fall outside the Brand rules that you created. Exceptions will only appear if the Brand rule is active and spans the correct group.

    A "gap" column will be highlighted in yellow if product exceptions exist in the Brand classes compared in the Brand rule. The gap is the relationship between the products in the first and second classes in the rule. For example, Price % GAP is calculated as:

    [ Price(1) - Price(2)) / Price(2) ]

    The specific gap column (such as Price % Gap, Price $ Gap, Eq Price % Gap, Unit GM Gap($), Unit GM Gap(%), GM% Gap) is based on the parameters used in the Brand rule definition. For example, if the Brand rule is set with the $ range and retail price, the Price $ GAP columns will be highlighted if exceptions exist with the retail price gap between Brand classes specified in the Brand rule; if the Brand rule is set with the % range and retail price, the Price % GAP column will be highlighted in yellow if exceptions exist. The columns are available at the SKU/Store, SKU/Zone, and SKU/Chain aggregations.

  • Current Comp Retail Below Cost Exceptions - Use this report to view or edit products with competitive prices that are below cost. The Comp Profit column shows the difference between the retailer's cost for the product and the competitor's price (Comp Profit = Compl/Comp Price - Unit Cost). The report is filtered based on this column, and is set to show values that are less than zero by default.
  • Current Retail Above Comp Retail Exceptions - Use this report to view or edit products that are currently not competitive, since the current prices are above the competitive prices. This report is filtered based on the Cur to Comp Price Diff % column, and is set to show values greater than zero by default.
  • Current Retail Below Cost Retail Exceptions - Use this report to view or edit products that are currently selling below cost. The Current to Cost Diff$ column shows the difference between a product's cost and current price (Current® to Cost Diff$ = Current Price - Unit Cost). The report is filtered on this column and is set to show values less than zero by default.
  • Custom Relationship Exceptions - Use this report to view products that fall outside the Custom Relationship rule that you created. Exceptions will only appear if the Custom Relationship rule is active and spans the correct group.

    The retail price for an individual product or the group price for the Custom class will be highlighted in yellow to indicate the exceptions, based on how you defined your comparison in the Custom Relationship rule.

  • Line Exceptions - Use this report to view or edit products whose prices do not match the rest of the products in the line group at a single store. This report lets you run a pre-optimization diagnostic analysis of line exceptions for active products. Exceptions will only appear if the Line Price rule is active and spans the correct group.
  • Other1 Exceptions - Use this report to view or edit products that fall outside Other Class 1 rules that you created. Exceptions will only appear if the Other Class 1 rule is active and spans the correct group.

    The Price % GAP column will be highlighted in yellow if exceptions exist with the retail price gap between Other 1 classes specified in the Other Class 1 rule, and the Eq Price % GAP column will be highlighted if exceptions exist with the equivalent price gap between Other 1 classes in the rule.

  • Other2 Exceptions - Use this report to view or edit products that fall outside Other Class 2 rules that you created. Exceptions will only appear if the Other Class 2 rule is active and spans the correct group.

    The Price % GAP column will be highlighted in yellow if exceptions exist with the retail price gap between Other 2 classes specified in the Other Class 2 rule, and the Eq Price % GAP column will be highlighted if exceptions exist with the equivalent price gap between Other 2 classes in the rule.

  • Product or Line Relationship Exceptions - This report displays results of products in product-pairs, or line groups in pairs whose base or current prices did not conform to the Product or Line Relationship rule. Chain level summary information is included. Exceptions will only appear if the Product or Line Relationship rule is active and spans the correct group. The existing Product to Product Relationship Exceptions report in Scenario Results show the exceptions to the Product or Line Relationship rule after the scenario exceptions.

    The aggregations in the report are the following:

    • Line to Line - Zone
    • Line to Line - Store
    • Product to Product - Zone
    • Product to Product - Store

    The Product or Line Relationship rule sets the price of the second product/line group in a pair based on a multiplier or relative value applied to the price of the first product/line group, as shown in these equations:

    Price of UPC(2) = Price of UPC(1) x Multiplier Value

    Price of UPC(2) = Price of UPC(1) + Relative Value

    Prices in Line(2) = Prices in Line(1) x Multiplier Value

    Prices in Line(2) = Prices in Line(1) + Relative Value

    You can modify the Product or Line Relationship rule, or modify the products and values in the Data Maintenance Product or Line Relationship report.

  • Size Exceptions - Use this report to view or edit products that fall outside the Size rules you created. Exceptions will only appear if the Size rule is active and spans the correct group.

    The Price Per UOM % GAP column will be highlighted in yellow if exceptions exist with the retail price per unit of measure (UOM) gap between Size classes specified in the Size rule.

  • Unit GM$ Compliance Exceptions - Use this report to view products that fall outside the Unit Gross Margin$ rule that you created. The exceptions will be created if the Unit Gross Margin$ rule conflicts with other compliance rules. Exceptions will only appear if the Unit Gross Margin$ rule is active, the rule is set as a compliance rule, and it spans the correct group.
  • Zone Exceptions - Use this report to view or edit products that fall outside the Price Zone rules you created. Exceptions will only appear if the Price Zone rule is active and spans the correct group.

To see information about multiple types of exceptions, navigate to Data > Export and select Data Maintenance Exception Summary - SKU/Zone from the Report drop-down menu. The exported spreadsheet contains counts of each type of exception in your chosen categories.

For individual exception reports, navigate to Data > Export and select Data Maintenance Exceptions - SKU/Zone. This will export a zip file with an exception report for each selected category. See Exporting data for more information on exporting reports.

Note: Information found in the exported Data Maintenance Exception Summary - SKU/Zone report can also be viewed within the product interface as a scheduled report. To set up this scheduled report, navigate to Admin > Task Scheduler and create a new task. Select Scheduled Reports in the Task Type drop-down menu and Data Maintenance Exception Summary Report in the Task Definition drop-down menu.