Top finding for the Finance Controller. SKUs whose unit margin has materially eroded in the last quarter.
At a glance
Top finding for the Fortune 500 Finance Controller. Per-SKU table of items whose unit gross margin has eroded materially (>20% relative drop) in the trailing 90-day window vs the prior 90-day window. The Pareto-cut intervention list, sorted by margin-dollar impact descending.
| What it counts | For each SKU with sales in both windows: margin_pct(this_window) minus margin_pct(prior_window). Items with relative drop > 20% (e.g. 40% margin compressed to 32% margin = 20% relative drop) flag. Annualised dollar impact computed by multiplying erosion rate by current 90D volume × 4. |
| Tax treatment | Net of tax. |
| Cost basis | Average Cost / Standard Cost per inventory-org configuration. |
| Shipping | Excluded from per-SKU margin (treated as separate freight income / COGS). |
| Refunds | Credit Memo lines reverse the original revenue + COGS, neutral to per-SKU margin. |
| Volume threshold | Default 50 units / 90D minimum to qualify (low-volume SKUs have noisy margin). |
| Currency | Reporting ledger. |
| Business Unit scope | Respects dashboard filter. |
| Time window | 90D vsP |
| Alert trigger | any SKU dropped >20% margin |
| Roles | owner, finance |
Calculation
Calculated automatically from your Oracle ERP Cloud data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US Fortune 500 outdoor-equipment retailer on Oracle ERP Cloud. 90D windows: this 14 Jan 26 to 13 Apr 26 vs prior 16 Oct 25 to 13 Jan 26. Top 6 margin-erosion alerts:| SKU | Description | Prior margin% | This margin% | Relative drop | 90D revenue (this) | Annualised impact |
|---|---|---|---|---|---|---|
| TENT-4P-EXP | 4-person expedition tent | 42.0% | 28.4% | -32% | $2,420,000 | -$1.32M / yr |
| BAG-DOWN-WIN | Down winter sleeping bag | 48.0% | 36.0% | -25% | $1,680,000 | -$0.81M / yr |
| BOOT-HIKE-WP | Waterproof hiking boot | 38.0% | 28.4% | -25% | $3,240,000 | -$1.24M / yr |
| JACK-FLEECE-MIDLAYER | Fleece mid-layer jacket | 52.0% | 39.0% | -25% | $1,420,000 | -$0.74M / yr |
| PACK-65L-EXP | 65L expedition backpack | 44.0% | 33.0% | -25% | $1,180,000 | -$0.52M / yr |
| STOVE-GAS-COMPACT | Compact gas stove | 36.0% | 27.0% | -25% | $640,000 | -$0.23M / yr |
- TENT-4P-EXP lost 32% margin (42% to 28.4%). Largest annualised impact at -$1.32M / yr. Two possibilities: vendor cost rose (check Average Landed Cost per Unit for this SKU) or competitive pricing forced a markdown.
- Five of the six are at exactly -25%. That pattern usually means a single vendor price increase across multiple linked SKUs (same supplier raised prices 25% on a product family, the merchant has not passed through to customer pricing). Check the supplier on each SKU; if all from same vendor, the renegotiation conversation is clear.
- Cumulative annualised exposure: $4.86M / yr. Four times current quarter, projecting forward.
- Action playbook:
- Pricing exception review for the top 3 SKUs (TENT, BOOT, BAG)
- Vendor cost negotiation for the supplier behind the cluster
- Update list pricing in Oracle Pricing module for the affected SKUs
- If the cause is competitive: consider retiring the SKU from full-margin assortment and moving to clearance
- Cross-reference Landed Cost Variance vs Standard: if landed cost is rising vs the standard cost, manufacturing is absorbing the variance until prices update.
Sibling cards merchants should reference together
| Card | Why pair it with Margin Erosion Alerts |
|---|---|
| Gross Margin Percentage | Aggregate margin; this card explains the per-SKU drivers. |
| Margin by SKU | The full per-SKU distribution this card filters. |
| Margin Compression | The aggregate alert; this card is the SKU-level worklist. |
| Average Landed Cost per Unit | Cost-side driver, often the cause. |
| Landed Cost Variance vs Standard | Whether costs are drifting from standard. |
| Top SKUs by Inventory Value | Which SKUs hold the most $; if a margin-eroded SKU is also a top inventory holder, the impact is doubled. |
| Dead Stock with Active Ad Spend | Margin erosion + ad waste = compound bleeding. |
Reconciling against the vendor’s own dashboard
Where to look in Oracle ERP Cloud:OTBI → Inventory Real Time + Order Management Real Time + Cost Management Real Time custom analysis Oracle Analytics Cloud (OAC) → Margin Variance Dashboard (if licensed)The OAC dashboard ships a pre-built variance view but at a default 30D window; this card uses 90D for noise reduction. Why our number may legitimately differ:
| Reason | Direction | Why |
|---|---|---|
| Volume threshold | Either | Card excludes low-volume SKUs to avoid noise. |
| Cost method election | Either | Average vs Standard treats cost moves differently. |
| Discount allocation | Either | Discount allocation method affects per-SKU margin if shared discounts exist. |
| Promotional period | Either | A 90D window straddling a major promotion captures distorted margin; configure exclusion windows in the field map. |
| Card | Direction | Notes |
|---|---|---|
| Commerce-platform product-margin views | Approximate | Commerce platforms use their own cost field which is rarely audit-grade. Trust this Oracle-side card. |
Known limitations / merchant FAQs
Why 20% relative drop, not absolute? A 5pp absolute drop is meaningful at 50% margin (10% relative) vs catastrophic at 15% margin (33% relative). Relative drop catches both ends. Configurable per workspace. Why 90D window not 30D? Margin moves on a quarterly cadence in retail (vendor pricing reviews, customer-pricing reviews); a 30D window picks up noise. 90D matches the quarterly business rhythm. A SKU launched 60 days ago shows up here. Real signal? Probably not. The card uses 90D windows; if prior period had no sales (item was not yet launched), there is no comparison. Default behaviour: exclude SKUs without prior-period sales; new launches surface on a separate watchlist. A clearance SKU shows up here, expected? Yes by design; clearance margins compress. If you want to exclude clearance items, tag them with the Item Master clearance flag and the field map will filter. Multi-currency, does FX cause false positives? Possible if the SKU is sold across currencies and the FX moved 5%+ in the window. Card normalises to reporting ledger but local-cost / local-revenue mismatches can create phantom erosion. Cross-check against FX Currency Exposure. RMCS deferred revenue impact? If revenue is deferred but cost is recognised, period margin compresses. The card flags this as erosion. Configure RMCS-affected SKUs to exclude in the field map for cleanliness. Standard Cost variances, where do they show? If your SLA rules route variances to a separate variance account, this card uses the standard cost (clean per-SKU view). If they route to COGS, the card sees the variance-loaded cost. Implementation-dependent. How does this differ from NetSuite’s equivalent? Same logic. NetSuite computes per-item margin fromtransactionLine.netAmount and transactionLine.estGrossProfit; Oracle computes from Cost Management’s actual + Receivables revenue. Vortex IQ’s view is consistent across both.
Auto-action available?
Margin erosion is a strategic decision, not an auto-action. Vortex IQ surfaces and prioritises; pricing / vendor / assortment decisions remain human.
Annualised impact calculation logic?
Erosion rate × current 90D volume × 4. Approximate; assumes volume is constant going forward. For seasonal items this overstates. Use the 90D dollar impact as the conservative figure.