Conflicts

3 conflict groups detected by comparing semantically-normalised values inside each conflict group. Each value keeps its own scope and source; nothing is averaged, merged or silently resolved.

These are not errors in the data map

A conflict means two captured representations assert different values for the same predicate. The dashboard reports both, with the conditions that explain the difference.

available_colourways_count

The merchant's own copy, selector and compare table disagree on the number of 31L colourways.

CONFLICT

PRVKE 31L V4

8F016
PDP · no conditions
MERCHANT_AUTHORED
7F019
PDP · description copy claim
MERCHANT_AUTHORED
7F020
PDP · Compare Products table (PRVKE 31L column)
MERCHANT_AUTHORED

available_sizes_count

Description copy says three sizes; the selector offers four (15L, 21L, 31L, 41L).

CONFLICT

PRVKE 31L V4

4F014
PDP · no conditions
MERCHANT_AUTHORED
3F018
PDP · description copy claim
MERCHANT_AUTHORED

rating_count

Different scopes: the Black / 31L product page review set versus the Global Catalog clustered UPID.

CONFLICT

PRVKE 31L V4

3068F153
PDP · rendered on product page
MERCHANT_AUTHORED
3068F156
embedded JSON · Black / 31L product page (Okendo)
PUBLIC_SHOPIFY
3068F157
JSON-LD · JSON-LD ProductGroup aggregateRating
MERCHANT_AUTHORED
3068F225
embedded JSON · Okendo app state
PUBLIC_SHOPIFY
21472F266
Global Catalog · Global Catalog clustered UPID
GLOBAL_BASE

Why only three groups?

The conflict detector normalises comparison semantics before comparing: availability booleans equal schema.org InStock labels, numeric strings compare as numbers, and cube-model lists compare as sets. Visibility differences caused by catalog filter defaults are recorded as scope, not conflict.

Colourway count: the selector offers 8; the merchant's own description and compare table say 7.
Size count: the selector offers 4 sizes; the description copy says 3.
Rating count: the Black / 31L product page reports 3,068 reviews; Global Catalog reports 21,472 for the clustered UPID.