Resolution Layer Case Study · Read & Diagnose
Safety & personal protective equipment.
A catalog read across protective eyewear, hearing protection, respiratory protection and first aid — for a hardware and home-improvement distributor, and in the one category where the specification is not a preference but the protection itself.
This is a real EKOM catalog analysis, with the client's identity removed. The client is a hardware and home-improvement distributor — Pyramex, Safety Works, Edge Eyewear, Forney, 3M and First Aid Only among the lines it carries. EKOM read one complete category of its public catalog, safety and personal protective equipment, and surfaced 21 flagged items, 20 of which are actionable catalog defects. The twenty-first was withdrawn before publication — it reported that certain product web addresses would break, and spot-checked against the live site they did not. The mismatch is still worth tidying; the breakage claimed for it was not. It is in no count here.
What makes this category different is what the buyer is actually choosing between. Nobody is comparing two objects they can hold. They are comparing a noise reduction rating, a lens tint, whether a lens is rated for UV, whether a mask is a respirator or a face shield. The specification is the protection. So the defects that matter here are not thin copy or a missing photograph — they are two fields on one product asserting incompatible things, on the attribute the product exists to provide.
In most categories a wrong attribute costs a click. In protective equipment it costs the wrong product — chosen on a number the record cannot stand behind.
One thing this study deliberately does not do. It reports every finding below as a factual inconsistency between fields on the same product — what the data shows, and all the analysis can establish from outside. Whether any of it carries a compliance consequence is a question for the business and its suppliers. No statute is named here, and none was named in the analysis.
Manufacturer and brand names are kept as they appeared, since on a distributor catalog they belong to the manufacturers rather than to the client. The client's own item numbers, product titles, specification key names and category taxonomy have been removed or generalized; field values shown in quotation marks are verbatim.
What's inside
- At a glance — the severity split, where the findings concentrate, and how the read was done.
- What a buyer runs into first — a hearing protector with three noise ratings, and a sibling whose dissenting number sits on the key a filter reads.
- The receipts — a record that disagrees with itself, four eyewear families each holding the other's lens color, and respiratory protection filed as fire equipment.
- Markers that outlived their meaning — a drop-ship sentinel on stocked, priced goods.
- Where it traces back, and what's next — the five upstream mechanisms most of these findings collapse into, each with the tell that proves it, and the order to fix in.
Nothing was supplied and no internal system was touched. Everything below was read from the public catalog.
20
Actionable findings
(21 flagged)
Where the 20 concentrate
Theme
What it is
Findings
Contradictory protection ratings
Three ratings on one product; a sibling whose dissenting number sits on the key a filter reads; a duplicated key; a description that stops before its rating
4
Lens specs exchanged
Four families where each product holds its sibling's lens color
4
Name contradicts spec
Anti-fog, frame and lens color asserted in the name and denied in the spec, plus a UV claim only the description makes
3
Filed as something else
Respirators under fire extinguishers, goggles under earmuffs
3
Fulfillment sentinels
A drop-ship price and weight marker on stocked goods
3
Vocabulary splits a filter
One brand answering Y/N where the rest answer Yes/No
1
No product photography
A placeholder where the product should be
1
A count contradicts the name
A kit named for 312 pieces and specified at 313
1
Every finding here is rated critical or high — a property of what this pass recorded rather than a clean bill of health. A single coherent category yields less low-grade noise than a mixed one.
How EKOM read this catalog
1
Read
The public catalog as any shopper, retailer or assistant sees it — no file handoff, no credentials, no integration.
One complete category, read end to end.
→
2
Profile
Infer what each field is for from how the catalog itself uses it, then hold every product to that.
The eyewear records share one spec convention and it holds — the only reason a swapped value is visible.
→
3
Analyze
Surface defects, rate severity, and bind each one to the products and values behind it.
20 findings, 8 themes, 5 causes.
These are machine-surfaced signals from a cold read, not a verified defect list. A share of any such read turns out to be intentional — a sentinel with a reason behind it, a vendor's vocabulary deliberately preserved. That is why every finding is shown with the value behind it, and why the ones needing a judgment only the business can make are kept separate.
What a buyer runs into first.
Three of the four contradicted-rating findings sit on hearing protection, where the contested field is the entire reason the product exists.
Critical · Hearing protection
One pair of earmuffs states three different noise reduction ratings across four of its own fields.
The product name, the description and two separate specification keys each state a rating. The four fields hold three different numbers. A shopper choosing protection for a job site has no way to know which the manufacturer stands behind — and neither does the record.
Field
Value
Rating
name
a foldable earmuff named for a 20 dB rating
20
description
states a rating of 24, in prose
24
a rating spec key, a letter missing from it
holds a bare integer
20
its correctly spelled twin
holds an NRR-prefixed string
27
This is one of only two findings in the analysis that propose no correction at all. There is no majority to fall back on and no way to derive the truth from the record, so EKOM raises it and stops. The right value comes from the manufacturer, not from an algorithm.
A third product in the theme fails the other way: its description stops partway through the rating, so a shopper reading that listing sees no completed number at all — not a wrong one, an absent one. Whether the text is cut at source, lost on the way to the page, or lost in EKOM's own reading of it is not settled from outside, and the study says so rather than guessing.
High · Hearing protection
On its sibling, four fields say 22 and one says 23 — and the dissenter is the one a filter reads.
The same product family, one size along. Here the evidence is one-sided: the name, the description and two specification keys all say 22. A single key disagrees. What makes it consequential is which — the correctly spelled half of a duplicated key pair, and the half a filter keyed on that spelling reads.
Three keys for one quantity sit on that single record: one carrying 22 dB NRR, one — a key with a letter missing from it — carrying a bare 22, and its correctly spelled twin carrying NRR 23.
A record that disagrees with itself.
The receipt device: no outside data needed. Each row is one product, and the product's own fields are the proof.
Critical · Protective eyewear
A pair of safety glasses is described as UV-protective and anti-fog, and specified as neither.
The most thoroughly contradicted eyewear record in the category. The name says anti-fog and gray. The description says the lenses will not fog and carry ultra violet protection. The specification block disagrees with all of it.
Field
Value
Says
name
a close-fitting Safety Works glass named for anti-fog gray lenses
gray · anti-fog
description
Lenses offer maximum ultra violet protection and will not fog up during use
UV · anti-fog
specifications
lens color black, anti-fog No, UV protection No
neither
Two of the three conflicts are correctable from the record: name and description both say gray and anti-fog, so the specification is the outlier. The third is not. Only two fields speak to UV at all, and they disagree with no third vote to break the tie — so EKOM holds it rather than correcting it. That is the difference between a finding the record answers and a question only the business can.
Critical · Protective eyewear
A gray-framed, gray-lensed product is specified as "Mirror" on both.
The name states the frame and the lens are both gray. Both specification fields hold Mirror — the same wrong value in two places, and a bare finish where the other lens-color values in this study all name a tint. Whether Mirror is even a permitted entry is one of the questions this pass hands back rather than answers.
Specifications that changed places.
Four separate eyewear families carry the same defect in the same shape: two products in a family hold each other's lens color. The name says one tint, the specification says the other — and on the sibling, the mirror image.
Family
The name says
The spec says
Pyramex Velar
Ice Blue Mirror
Gray
— its sibling
Gray
Ice Blue Mirror
Pyramex PMXTREME
Ice Orange Mirror
Gray
— its sibling
Gray
Ice Orange Mirror
Pyramex Highlander Plus
Gray
Sky Red Mirror
— its sibling
Sky Red Mirror
Gray
I-Form Helix
Clear
Smoke
— its sibling
Smoke
Clear
In every pair the two records are identical in every other specification attribute and hold exactly each other's lens color. Random corruption does not produce that shape. An exchange does — which means the correct values are not missing, they are on the wrong two records.
Frame color, anti-fog, UV protection and polarized are the same on both sides of each swap. Only one attribute moved, and it moved between the two records rather than away from them. A clear lens and a smoke lens are not interchangeable in the situation each is bought for: a buyer filtering for clear lenses to work indoors is shown a product the record describes as smoke, and the reverse. A fifth record carries one side of the same inversion with no partner among the findings, so unlike the four above it cannot be corrected by putting two values back where they belong.
Three findings, five products. Category assignment decides what a shopper can reach by browsing. Here it has placed respiratory protection under fire equipment, chemical splash goggles under hearing protection, and half-mask respirators under face shields.
Product
Where the catalog files it
Should be
An N95 face mask
four segments deep under fire protection, ending at a fire-extinguisher leaf
Respirator
A disposable paint respirator
the same path, byte for byte
Respirator
Replacement mask pre-filters
the same path, byte for byte
Respirator
Two half-mask respirators
a second path, under face and head protection, ending at a face-shield leaf
Respirator
Chemical splash goggles
a third, under hearing protection, ending at an earmuff leaf
Safety goggles
Three different respiratory products share a byte-identical wrong path, and two more share a second. Filed one at a time, mistakes scatter across the tree. A mapping collapses many products onto few wrong leaves — which also means it is fixable as a mapping.
Two further products break the catalog's own path grammar rather than its meaning: one is missing the root segment every other path begins with, and one carries an extra root from a different department. Both were detectable on shape alone, which is only possible because the grammar is otherwise consistent — four segments, one root, throughout the category.
That consistency is worth naming, because it is what makes this theme cheap to fix rather than expensive. The destination paths already exist on comparable products, so nothing has to be invented. And on every product re-filed here, the category leaf is wrong in exactly the same way the path is — the leaf is the last segment of the path, before and after — so re-filing is one decision rather than two that can drift apart later.
Markers that outlived their meaning.
The catalog uses sentinel values to mark items it does not price or weigh directly — a convention, and a sound one. The finding is not the convention. It is that the sentinels have reached products the convention was not meant for.
Critical · Price and fulfillment
Stocked items carry the no-price sentinel, which leaves them visible and — if the stock flag is right — unbuyable.
The catalog establishes a repdigit price as the marker for drop-ship-only items. It also sits on items flagged as stocked. Either the price is missing from something the business holds, or the fulfillment flag is wrong on something it does not — and from outside the record there is no way to tell which. This is one of only two findings in the analysis that propose no correction: a withheld price and a lost price look identical from here.
Critical · Weight and shipping
The same convention has leaked into weight, on items that are stocked and correctly priced.
The drop-ship weight sentinel sits on items carrying real prices — $8.99, $14.49, $22.99, $47.99 among them. Anything quoting shipping from that field is quoting against a placeholder. A third group has neither a weight nor the sentinel: the field is empty, which fails differently — a system expecting a number and receiving nothing errors rather than mis-quoting. Two of these also carry the no-price sentinel from the finding above.
A separate pattern in the same family: one brand answers the category's yes-or-no specifications with Y and N where the others write Yes and No. A facet reading that field builds two buckets that never merge, so a shopper filtering for anti-fog eyewear sees one brand's products or the others', never both. A separate oddity sits in the same specification block on one record — a key answered with its own name as the value — and is not counted as a finding, because nothing in the record says it is wrong.
None of the three is presented here as a defect to correct unattended. A repdigit price may be a deliberate "call for price" state. A placeholder weight may be a documented instruction to rate the shipment another way. A vendor's own vocabulary may be preserved on purpose, with the merging done at the facet layer instead. Each is a reasonable way to run a catalog — and each has to be a decision rather than an accident, which is the difference this pass can see and cannot settle.
20 findings sounds like 20 problems. The great majority of them collapse into five upstream mechanisms — and a mechanism can be fixed once and stopped from recurring. Each one below is admissible only because something in the data proves it.
One column exchanged between two records
The tell: the two products are identical in every other specification attribute, and each holds exactly the other's value in one. Nothing is lost — it is transposed. It produced four eyewear families holding each other's lens colors.
Two writers for one measurement, one misspelling the key
The tell: a specification key with a letter missing sits alongside its correctly spelled twin on the same record, and the two disagree — with the misspelled one holding the number that matches the product name. The same quantity is stored in three formats: a bare integer, an NRR-prefixed string, and one carrying dB inline. It produced the contradicted hearing-protection ratings, and a duplicate key no filter reads.
A fulfillment marker used as a value
The tell: the weight sentinel sits on records flagged as stocked and carrying real prices, so the marker has outlived the condition it marks. The same convention runs in price, where it leaves a stocked item with no price at all.
A mapping collapsing products onto one wrong leaf
The tell: three different respiratory products carry a byte-identical wrong category path, and two more share a second. A person filing by hand scatters; a mapping collapses. It produced respirators under fire extinguishers and splash goggles under an earmuff leaf.
A vendor's vocabulary passed through unnormalized
The tell: the divergent form is confined to one brand — its anti-fog, UV and polarized values read Y/N where other brands write Yes/No. It produced a filter that returns one brand's products or the others', never both.
Fixing findings one at a time fixes those findings. Fixing a mechanism fixes every product that has passed through it, and every product that will — and every one of the five is a property of how records are written rather than of what they describe.
38%
In a September 2025 survey of 1,000 U.S. consumers, 38% said they will abandon a site if they cannot easily find key features such as sizing and materials — and a further 39% said they will go find that information on a competitor's site instead. In protective equipment those key features are the rating and the tint: the attributes this study found stated two ways on one product.
Akeneo PX Pulse survey, conducted by Dynata, September 2025, n=1,000 U.S. consumers aged 18+
A catalog of this kind sells confidence as much as inventory. The question a buyer is really asking — how loud, how long, what is in the air, what is coming at the eyes — used to be answered by someone who had answered it a thousand times. Online the specification fields carry that alone, and these findings are what happens when that transfer is never explicitly designed. Nobody decided a misspelled key would hold the number that matches the product name; it was never anybody's job to check.
What this class of defect costs is not a sale — it is the wrong sale, and the trust that follows it. A shopper filtering safety glasses by lens tint is returned the other product, because two records hold each other's value. A shopper browsing respiratory protection never reaches five respiratory products and a pair of splash goggles, because those are filed under fire extinguishers, face shields and earmuffs. And a shopper comparing hearing protection on the number that is the entire point of the product finds one earmuff asserting three numbers about itself.
None of that is characterized here as a compliance matter, and this study will not do so: what the analysis found is fields on a product disagreeing with each other, which is a fact about the record, and everything past it is a judgment for the business and its suppliers to make. The commercial reading needs no escalation. In a distribution catalog one record does not appear in one place — it feeds every downstream surface that reads it, and it arrives on all of them at once with nobody standing beside it.
Three moves, in order. The first needs no new data at all — and one correction that looks easiest deliberately waits.
This pass read and diagnosed. The same structural understanding powers what follows — turning a diagnosed catalog into one a buyer can specify from with confidence.
1 · Apply the corrections the record already answers for itself
Put the exchanged lens colors back on the right records — the correct value is already in the catalog, sitting on the sibling. Re-file the protective equipment that is in the wrong branch, correcting leaf and path together so the two cannot drift. Restore the specification values that the name and the description jointly contradict. Approved as patterns, not product by product.
2 · Settle the questions that gate the rest — starting with the duplicated key
Renaming the misspelled rating key looks like the easiest fix here and is the one that must not be done first. If the two keys are one measurement, the rename de-duplicates. If they are two measurements deliberately stored apart, it destroys one — on a protection rating. That answer, and whether a repdigit price means "call for price", come from inside the business before any of it can be applied.
3 · Hold the line at intake
Keep ongoing intelligence where manufacturer data meets the distributor's own layer, so the next contradicted rating is caught as it lands rather than found later by a buyer choosing protection on it.
This is how EKOM moves a catalog from insight to impact —
and keeps every specification reading right as the business grows.