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.
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:
Investigation walkthrough:
- 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
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:
Cross-connector reconciliation:
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.