The Resolution Layer  ·  Case Study in BriefEKOM

Athletic footwear specs.

A read of a global athletic footwear brand's US men's shoes category — where the product pages carry a deep product record, and in places that record disagrees with itself. One of a set of anonymized EKOM analyses — what surfaced, and where it leads.

Vertical
Athletic footwear
Method
The brand's own public pages, saved as a shopper sees them; nothing supplied
Issues surfaced
22 reported · 11 of 100 sampled shoes with self-contradicting specs
This pass
Read & diagnose
Lead finding  ·  launches told to search engines as in stock
All three "coming soon" shoes in the sample publish "in stock". None of their sizes can be bought.
The structured data search engines and AI assistants can read says in stock, while the brand's own stock data on the same page marks every size as pre-release. Search results and shopping ads can show these shoes as buyable before launch. The other 97 sampled pages were consistent — which points to one missing mapping, corrected once with the pre-order value made for this state.

Also surfaced

Specs that contradict the shoe's own page
An extra-wide shoe filed as regular fit, a nylon-and-suede shoe filed as leather, a baseball cleat on a tennis surface, and laced shoes with no closure — so the filters a shopper uses show the wrong shoe, or miss the right one.
Stack heights no comparison can use
Five of the 24 sampled shoes that publish stack height break the rule that drop equals heel minus toe — including zero drops on raised heels and one shoe with heel and toe reversed.
One shoe, two records
In four of five same-shoe colorway pairs, specs that should not change with color differ — so one colorway can show up under a filter while its twin does not.
Findings that did not survive
Of 58 raised, 29 were set aside — seven from EKOM's own collection, twenty as deliberate choices or normal behavior, two unsupported — plus four consistent patterns and three open questions, none counted.

How EKOM read it. An analyst browsed the store as a shopper would, signed out, one page at a time — no crawler, no credentials, no integration — and EKOM read the product data the brand embeds in its own pages. Every result was checked against the original pages and tested for whether it could be deliberate; where it could, it is not counted.

From diagnosis to channel-ready. Most of the twenty-two collapse into four likely mechanisms — the same fact stored twice and never reconciled, shoe-level attributes kept per colorway, measurements entered without a rule, and templates with an unguarded edge. Correcting the mechanisms corrects the shoes they produced, and stops them recurring with the next launch. Then the same intelligence holds the line at publish.

The Resolution Layer
EKOM
[email protected]  ·  ekom.ai
EKOM
Case study — client anonymized