This scenario applies when products lack a persistent Product Id and are instead defined by feature combinations. It describes why standard product-level comparisons break down and how to establish comparability instead.
Data
Clear Product Ids are missing. An item is defined by a combination of features, options, or characteristics rather than by a persistent Product Id. Different configurations may therefore represent different commercial cases.
Why it Matters
SKU-based joins and "same product" history are not available. Comparability must be established from the configuration features, and naive product-level aggregation can produce misleading results.
Advice
-
Define which feature combinations make two configurations comparable.
-
Keep standard products and configured products distinguishable when both exist.
-
If a deterministic configuration fingerprint is available, use it as a comparison key without treating every configuration as a permanent product master record.