Choose where to investigate a pricing issue
7 min
choose where to investigate a pricing issue use this page when a pricing manager needs to decide whether a margin drop, competitor gap, promotion result, or export exception should be investigated in price reports, price management, promo analytics, or exports first where should i investigate this pricing issue first? start with the question behind the signal do i need to find the affected pricing outcome, explain the regular pricing decision, evaluate a promotion, or resolve an outbound handoff? choose one module first, then move to the next only when the evidence points there choose by the issue you see attribute price reports docid\ cudlursgmvcrrubq3grudprice management docid\ rs0z8lfkdpage86wko0qcpromo analytics docid\ pkwefzyh06ygitzc9iepmexports docid\ ayu6zunb35nqkubun3bpf start here when you need to locate the affected products, categories, or zones you need to investigate or change regular pricing governance you need to assess a promotion's outcome or forecast you need to investigate a pending, completed, or blocked outbound handoff main evidence new price, current price, difference, margin, cost, reference price measures, and sales price rules, price strategy, locked product status, product architecture, and projected impact uplift, cannibalization, sales history, impact profiles, and simulations export content, thresholds, mandatory columns, row limits, and export impacts best first response to a margin drop find where the margin changed and compare it with price, cost, and sales explain whether a rule, strategy, lock, or architecture setting drove the regular price outcome use when promotion activity may explain the change use when the movement is limited to a specific export best first response to a competitor gap confirm the gap by product and zone using reference price measures and reference price index review applicable pricing constraints after the gap is confirmed use only if a promotion caused the gap review the export's reference price index impact before release typical outcome a prioritized list of products or categories to investigate a justified regular pricing governance change, or confirmation that no change is needed a promotion decision based on incremental value rather than revenue alone a reviewed, released, canceled, or traced export route your investigation start in price reports docid\ cudlursgmvcrrubq3grud when you need to find the problem open price reports first when the signal is broad a category margin decline, a competitor position concern, an alert, or an unexpected difference between current price and new price use category list to determine whether the issue is concentrated in a category or subcategory switch from an aggregated view to a by zone view when a zone may be masking the result then use product list , filters, or product chart to isolate the products with material price, margin, cost, or reference price movement for a suspected demand driven issue, use sales history to separate regular sales, standard promo, and multibuy sales use price index history when the concern is a sustained reference price index movement rather than a one time gap when a recommendation appears surprising, review model insight to interpret detected signals used by the optimization algorithm rule of thumb start here when you do not yet know which products or scope explain the issue start in price management docid\ rs0z8lfkdpage86wko0qc when you need to explain or change a regular price decision open price management when you already know the affected product or category and the question is why the platform proposed its new price, or whether its regular pricing governance should change review price settings and the applicable price rule or price strategy remember that multiple rules form a rule intersection; if constraints do not overlap, the highest priority rule wins and the new price is chosen as close as possible to the others also check for a product level exception, locked product status, manual price, product architecture, or size architecture use impact overview before changing a category level setting use history tracking with the rule change log when a margin drop appears to follow a prior governance change review regular prices for the product level, by zone comparison of current price, new price, margin, cost, and reference price index rule of thumb start here when the issue is with a regular price recommendation or the rules that bound the optimization algorithm start in promo analytics docid\ pkwefzyh06ygitzc9iepm when the issue is promotional open promo analytics when the margin drop, competitor gap, or sales movement occurred during a promotion, or when you need to decide whether a future promotion is commercially worthwhile use individual promotions to compare past promotions and switch to including cannibalizations when sales shifted from other products in the category may change the result use product impact profiles to distinguish products that drive margin, revenue, or neither use product sales history to compare regular sales with standard promo sales around the past promotions timeline for a proposed activity, use promo simulation to compare during promo with without promo under pessimistic, mean, or optimistic assumptions for multibuy decisions, check quantity in baskets first choose thresholds near natural quantity in basket breakpoints rather than applying a tier without demand evidence rule of thumb start here when the question is whether a promo price or mechanic created incremental value after cannibalization, not whether a regular price was correctly governed start in exports docid\ ayu6zunb35nqkubun3bpf when the issue is in the handoff to downstream systems open exports when an issue is tied to a pending release, an unexpected export result, missing export rows, or confirmation of whether a price set became effective review export content for row level new price, current price, difference, margin movement, cost, and reference price measures this is the appropriate place to review controlled export price edits and recalculate prices before release use export impacts to assess category level profit, revenue, quantity, margin, and reference price index movement for the specific export if expected rows are absent, check minimum price change , export size limit , newly listed product protection , and mandatory columns in the export template use open exports for in progress lifecycle tracking and exported history to confirm completed standard exports that represent the effective current prices check canceled exports before assuming a planned handoff proceeded rule of thumb start here when the question is what was sent, what will be sent, or why a proposed change was excluded from the outbound handoff recommended investigation paths margin drop with unknown cause start in price reports docid\ cudlursgmvcrrubq3grud to find the affected category, products, and zones move to price management docid\ rs0z8lfkdpage86wko0qc if the issue follows a regular pricing change; move to promo analytics docid\ pkwefzyh06ygitzc9iepm if promotion activity explains the period competitor gap start in price reports docid\ cudlursgmvcrrubq3grud with reference price index and by zone view move to price management docid\ rs0z8lfkdpage86wko0qc to assess the applicable price rule, price strategy, or product architecture use exports docid\ ayu6zunb35nqkubun3bpf if the gap is in a pending outbound price set export exception or unexpected store price start in exports docid\ ayu6zunb35nqkubun3bpf confirm the export status and content, then use price reports docid\ cudlursgmvcrrubq3grud or price management docid\ rs0z8lfkdpage86wko0qc only if the exported new price itself needs commercial investigation weak promotional result start in promo analytics docid\ pkwefzyh06ygitzc9iepm check uplift and cannibalization before attributing a margin or revenue change to regular price performance common pitfalls treating a promotion period margin drop as a regular price problem without first separating regular sales, standard promo, and multibuy sales changing a price rule before confirming the affected products and zones in price reports reviewing only the aggregated view when a competitor gap or current price difference may be limited to one zone assuming every new price reaches stores; export thresholds, mandatory columns, protection periods, size limits, or cancellation can prevent the outbound handoff using a manual price to correct a recurring governance issue instead of investigating the applicable price rule, price strategy, or product architecture