Product ID Field Relationship Patterns

⚠ Active Anomalies — Missing Core Product ID (sibling variants have it populated)

These 3 active Apollo hardware products are missing Core Product ID, yet their ESS/STU sibling carries it. This breaks family-level rollups and Core-based reporting. Also: 1 record has no Product ID at all (SKU: LUNA-UPGRADE, $1,626 booked).

APX8G2-ESS — $135,667 booked — sibling APX8G2-STU has Core "APX8G2" APX4G2-ESS — $102,297 booked — sibling APX4G2-STU has Core "APX4G2" APTXQG2-ESS — $85,919 booked — sibling APTXQG2-STU has Core "APTXQG2" 710TF — $10,719 booked — SKU truncated to "710", no Core

Data Analyst Findings

SKU Naming Convention Split

Apollo/Satellite hardware uses long-form descriptive SKUs (UAD-2-APOLLO-...). Volt, MIC, GPS/GPM Pedals use short-form or exact-match SKUs. These are two distinct naming systems — joins on SKU across product families will fail without normalization.

Core Product ID Coverage Gap

31 active records (SKU_EXACT_NO_CORE) are bundles/subscriptions with no Core ID — expected. But 3 high-value Apollo ESS variants ($324K combined) are missing Core while their STU/ULT counterparts have it. This is a data entry inconsistency, not a system rule.

Refurb Shared SKU Pattern

All 12 refurb products share their parent's SKU ID but carry a "-REFURB" suffix in Product ID. Only 6176-REFURB has a Core Product ID populated. The other 11 refurbs are invisible in Core-level rollups — a silent undercounting risk.

Pedal Product Consistency

GPM and GPS pedal families are the most consistent: Core = Product ID (exact), SKU = readable [NAME]-PEDAL format. Zero anomalies across 20+ pedal SKUs. This family serves as the gold standard naming pattern.

Shared Core Variants

6 Core IDs are shared across multiple Product IDs (e.g., APTXDG2 → ESS+STU, APX16G2 → ESS+ULT). These represent product tier variants. The Core ID is the reliable rollup key for "base model" analysis — but only where it's populated.

Missing Product ID Row

One record ($1,626) has a blank Product ID with SKU "LUNA-UPGRADE". This record cannot be attributed to a product family, territory rollups will work but product-level reporting will lose this revenue. Needs data correction.