Aglet

Triage duplicate product results before grouping variants

Several rows can represent one product family, distinct variants, or duplicate index documents. Triage the identity boundary before hiding or grouping anything. Compare canonical identifiers, variant choices, titles, images, and result context so a useful choice is not discarded as clutter.

Establish what is happening

  1. Capture row identity

    Record query, category, sort, parent ID, variant attributes, SKU, title, image, source index, and click outcome for representative rows. Include a family with meaningful choices and a suspected duplicate. Keep result position attached to each row.

  2. Compare choice value

    Ask whether each row offers a distinct decision, such as size, color, or region, or merely repeats the same product identity. Compare destination behavior and inventory context. Do not use matching titles alone to prove duplication.

  3. Set a grouping boundary

    State which rows may collapse, which variant details must remain visible, and what happens when identity is uncertain. Preserve an ungrouped control. Stop when another reviewer can tell whether grouping removes noise or removes a legitimate choice.

What to carry forward

The triage output is a grouping boundary with identity evidence, useful variant choices, and exceptions. Stop when duplicate representation and legitimate variation are distinguishable. If canonical identity is missing, keep rows visible and route the identity gap rather than guessing.

Technical background: Digital.gov guidance.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow