Exact duplicate rows
If two rows contain the same values across the uploaded columns, they can be identified as exact duplicates. CatalogEaze can remove those exact duplicates during cleaning.
Duplicate SKUs are different
Two products can share a SKU while still having different titles, prices, descriptions, or other values. That is not the same condition as an exact duplicate row, so the product treats duplicate SKU detection as a review item rather than automatically deleting one product.
Why the distinction matters
Over-aggressive deduplication can destroy catalog information. The safer rule is: automatically fix deterministic problems; warn when the correct action depends on business context.
Review after cleaning
Before exporting, compare the row count and change summary. The user should be able to explain why every removed row disappeared.
Frequently asked questions
Can I remove duplicates based only on product name?
The safer default is exact-row deduplication. Name-only matching can incorrectly merge legitimate variants or separately priced products.
Can duplicate SKUs ever be valid?
Yes, depending on the catalog's variant structure and business rules. That is why duplicate SKU detection is surfaced as a warning rather than treated as automatic deletion.