Find ASIN Margin Leakage with Net PPM

Run an Amazon Standard Identification Number (ASIN)-level Net PPM comparison, rank each negative rate contribution, then decompose the largest drags into shipped COGS/PCOGS, CCOGS, and sales-discount pressure where the connected report exposes those fields. The ranking is Kuudo-derived, not an Amazon metric. Amazon's dashboard identifies products driving profitability up or down after costs, funding, and discounts.

That answers my question: "Our Vendor Central revenue looks fine but margin is sliding. Which ASINs are actually dragging down our pure product margin?" Revenue cannot show which equation term changed. The report must answer materiality first, then cause where the component fields support it.

The rate-leakage proxy and driver tests are Kuudo-derived from the sourced equation. Amazon does not name these fields.

A plain ChatGPT and Claude chat hits three walls: No access to your data, No way to take action, and Generic knowledge, not Amazon's. Selling Partner MCP supplies vendor-account context, a Skill produces the repeatable report and review queue, and Amazon Agent Atlas supplies the metric definitions, access rules, exclusions, and timing caveats. Without those pieces, the work stays disconnected, generic, and manual, which ships silent mistakes.

The Net PPM dashboard identifies products driving profitability up or down

The Net PPM dashboard identifies products that raise or lower profitability. It lives in Amazon Retail Analytics, which Amazon's reports index separates from Brand Analytics. An ABA customer or search dashboard is not the source.

The retrieved Amazon Retail Analytics and Reports Overview defines Net PPM around cost of goods, vendor funding, and sales discounts. That keeps the Skill focused on profitability instead of treating revenue as a margin answer.

The report renders its executive answer instead of hiding it in a notebook:

Only the connected run populates those values. When a component field is unavailable, the executive answer keeps the ASIN ranking and marks the driver analysis incomplete.

Net PPM separates revenue, PCOGS, CCOGS, and sales-discount pressure

Net PPM separates four signed components, so each available ratio's direction supports a first-pass driver flag. The normalized equation is:

Net PPM =
  (shipped revenue
   - shipped COGS [PCOGS]
   + CCOGS
   - sales discounts)
  / shipped revenue

The Amazon Retail Analytics Metric Glossary defines Shipped COGS as Amazon's item procurement price, also called Product Cost of Goods Sold (PCOGS). Contra-COGS (CCOGS) is vendor funding collected for agreements tied to purchases, customer sales, or marketing.

CCOGS includes Vendor Allowance, Quick Pay Discounts, and Discretionary COOP, but excludes display-ads Contra-COGS. One glossary rendering says "shipped CCOGS" in the subtraction term. The report normalizes it to shipped COGS/PCOGS because CCOGS is separately defined as the added funding term.

The run records a material-move threshold and a residual tolerance. Those are operator inputs, not Amazon thresholds.

Each component effect is signed: a negative value reduces Net PPM. Its pressure magnitude is max(-component_effect_pp, 0). A single-driver label requires exactly one pressure magnitude greater than or equal to {{material_ratio_move_pp}} percentage points, and that magnitude must be the largest. Mixed requires two or more pressure magnitudes to clear the same threshold. Unclassified covers a missing component, no magnitude that clears the threshold, or an absolute residual greater than {{residual_tolerance_pp}} percentage points. The output records both inputs beside every label so another run can reproduce the classification.

A rate-leakage proxy ranks material ASIN deterioration before investigation

Holding current revenue constant and multiplying it by a negative Net PPM rate change prioritizes ASINs with material sales and worsening margin. A large swing on a tiny ASIN cannot automatically outrank a larger drag.

Kuudo-derived calculations, not Amazon metrics

net_ppm_delta_pp
  = current_net_ppm_pct - prior_net_ppm_pct

current_margin_dollars_proxy
  = current_shipped_revenue * current_net_ppm_pct / 100

rate_leakage_dollars_proxy
  = current_shipped_revenue
    * max(prior_net_ppm_pct - current_net_ppm_pct, 0)
    / 100

pcogs_ratio_delta_pp
  = current_pcogs_ratio_pct - prior_pcogs_ratio_pct

ccogs_ratio_delta_pp
  = current_ccogs_ratio_pct - prior_ccogs_ratio_pct

discount_ratio_delta_pp
  = current_discount_ratio_pct - prior_discount_ratio_pct

pcogs_effect_pp
  = -pcogs_ratio_delta_pp

ccogs_effect_pp
  = ccogs_ratio_delta_pp

discount_effect_pp
  = -discount_ratio_delta_pp

component_pressure_magnitude_pp
  = max(-component_effect_pp, 0)

explained_delta_pp
  = pcogs_effect_pp + ccogs_effect_pp + discount_effect_pp

residual_delta_pp
  = net_ppm_delta_pp - explained_delta_pp

Holding revenue constant isolates rate deterioration from volume. The dollar fields are prioritization proxies, not booked loss, reimbursement value, or Amazon-calculated fields. Rounding and unavailable components can prevent reconciliation.

The report sorts rate_leakage_dollars_proxy descending and fills five rows from the connected periods. The bindings contain no sample ASINs or percentages.

I would not hand operations a rank-only table. The same rows continue into the causal review and ownership queue:

If components are unavailable, the rank still ships, the driver reads Unclassified, and the queue requests the missing evidence rather than fabricating a cause.

Manufacturing-view access and Warehouse Deals exclusions define the report boundary

ARA access does not guarantee Net PPM access. All vendors have Sourcing views; manufacturers also receive a Manufacturing view for ASINs they manufacture. Amazon displays Traffic, Net PPM, and Forecasting only to manufacturers. If an eligible manufacturer cannot see Net PPM, contact retail partners or open a Contact Us case.

Amazon's wording says Brand Analytics, including ARA, excludes Warehouse Deals because vendors do not collect the proceeds. Retail-partner tools may include those sales, so a vendor-facing and internal number can legitimately differ.

Amazon aims to update weekly reports within 72 hours, but reports can take up to a week after period close. The report records its period and as-of status instead of calling the data instantaneous.

The provenance footer records exact evidence instead of counts:

It also records Atlas collection amazon_vendors, corpus version 794a9c3de8380dfa, connected periods, run timestamp, and the exact titles Amazon Retail Analytics and Reports Overview, Amazon Retail Analytics Metric Glossary, and Vendor Reports and Analytics Overview. Derived prioritization fields remain labeled as non-native Amazon metrics.

What happens next

Turn the ranked report into an investigation queue, not an automatic commercial decision. Review the top ASINs and, where PCOGS, CCOGS, and sales-discount fields are exposed, confirm the largest component effect. When they are not, preserve the rank, mark the driver unclassified, and request the missing evidence. Then assign an owner. Run the workflow on closed, comparable periods and preserve the as-of status.

If Warehouse Deals or an internal retail-partner scope explains a mismatch, flag the row for reconciliation instead of rewriting the vendor-facing metric. Amazon did not supply remediation thresholds or an automatic action policy in the retrieved material, so the operator reviews the evidence before changing terms or escalating.

The Amazon Agent Data layer combines Amazon Ads MCP, Selling Partner MCP, Amazon Agent Atlas, and Skills so the report can be grounded, rerun, reviewed, and handed to an operator as one workflow.

Revenue can stay stable while ASIN economics deteriorate; a sourced Net PPM decomposition turns that ambiguity into a ranked investigation queue.

Next, use the same evidence-first pattern when disputing PO on-time accuracy chargebacks.