The Resolution Layer  ·  Case Study in BriefEKOM

Handbag colorways.

A read of a direct-to-consumer handbag brand's complete public catalog — where every colorway is published as its own product, and the name is the only thing that tells two listings apart. One of a set of anonymized EKOM analyses — what surfaced, and where it leads.

Vertical
Handbags and accessories
Method
The brand's own public catalog and product pages, nothing supplied
Issues surfaced
35 reported · 344 products on 42 titles
This pass
Read & diagnose
Lead finding  ·  many colorways, one name
344 products share one of just 42 titles, and the page titles Google indexes repeat the same way.
Each colorway is its own product, but the title names only the family; the color sits only in the color choice on the product. The brand's signature bag appears as fifty-four products with one identical title. On 284 pages for products sold in a color, the color is not in the page title, so Google sees dozens of pages competing for one name and an assistant asked for a particular color finds none to match.

Also surfaced

Listings that describe another bag
Two charms described as the orange one (one has since left the feed), six addresses naming a color or material the product is not, and fourteen addresses that say "copy" — the trail of colorways made by copying the last one.
A product type that is not a category
Fifty-nine product types: bag families, size runs and blanks. Every shoe is filed as a size range, so any collection, filter or campaign built on this field misfiles it.
Checkout tools published as products
Shipping protection with 76 price variants, a return-coverage fee and a gift-card app sit in the public feed beside the bags, where shopping engines and AI agents read them.
Findings that did not survive
One finding was withdrawn, part of another, three were set aside as observations, and one was held after a live check showed the page was right. None is counted.

How EKOM read it. EKOM read the brand's whole public catalog and every product page — no file, no credentials, no integration — held each product against its own family, and had an analyst check every figure against the feed. A sample of the headline findings was re-opened on the live store before writing. Where a finding failed that check, it was withdrawn or held and says so.

From diagnosis to channel-ready. Most of the thirty-five collapse into six likely mechanisms — colorways named only for their family, new listings made by copying the last, facts kept as free text, checkout apps writing into the catalog, platform defaults never overwritten, and campaign and test residue never cleared. Correcting the mechanisms corrects the colorways they produced, and stops them recurring in the next drop. Then the same intelligence holds the line at publish.

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