The Resolution Layer · Case Study in BriefEKOM
Irrigation & sprinkler parts.
A cold read of the sprinkler category of an online irrigation-supply retailer — where one part is sold singly, by the bag and by the case, and a buyer chooses it by its numbers rather than its looks. One of a set of anonymized EKOM analyses — what surfaced, and where it leads.
Lead finding · single units and packs the record cannot keep apart
A single spray body and its case of fifty share one part number.
The two are distinct items, and the case is priced at almost exactly fifty times the unit — so the prices are right and only the identifier collides. Every other case of fifty on the listing carries the catalog's own pack suffix; this one does not. Anything keyed on part number — inventory, purchasing, a supplier feed, a pick ticket — sees one item where there are two, fifty times apart. It is not alone: a bag of twenty-five nozzles is priced at about twenty-five times its family, and a case of twenty-five has no part number at all.
Also surfaced
"Was" prices from a different unit of sale
Nine packs — cases of 50, 25, 20 and 10, and bags of 10 — carry a compare-at price on a single unit's scale. The price charged runs from six to thirty-five times the struck-through figure, so the saving is suppressed or shown as a markup on the listings contractors buy in volume.
Filters that answer the wrong question
Height and inlet tags sit on the product while the specification varies by variant. Every body on two listings is tagged 4-inch, the 2, 6 and 12-inch ones included, and twelve side-inlet heads are tagged as not side-inlet. One listing in the same catalog already tags nearly every height and both inlet values — the convention exists in-house.
Specifications a contractor would act on
Five nozzles publish a "full" arc of more than 360 degrees. One spray-body line states a minimum operating pressure higher than its maximum. Two specification lists stop mid-line at the same character, and a 1-inch swing joint is sold under a 3/4-inch model's copy and size tag.
Filled in is not the same as right
Unavailable parts tagged in stock, and shipping weights that do not look like measurements — whole lines at zero, a single body and its case of fifty at the same flat pound. A completeness check scores every one of these fields at a hundred percent.
How EKOM read it. The engine read the retailer's own public product feed cold — no file, no credentials, no schema — archived it on the day, and checked the analyzed table against those bytes field by field. It profiled what each field is for from how the catalog itself uses it, then held every variant against its siblings: the pack against its single unit, the listing against the one that gets the same thing right. It inferred the catalog's own pack conventions from the records themselves and reported where they break; the review found that two of them compete.
From diagnosis to channel-ready. Most of the 64 findings collapse into six upstream mechanisms — pack variants inheriting from the single unit, variant specifications filed on the product, listings built by copying a sibling, characters lost between source and storefront, a static tag doing the job of a live field, and defaults standing in for values. Fixing the findings fixes the findings; fixing a mechanism fixes the records it produced and every one added after. Then the same intelligence holds the line at intake, so the next pack added on the wrong scale is caught as it lands, before a contractor orders from it.