Portal User Guide

Docs · Portal User Guide · Duplicates

Reporting: Duplicate Finder

Duplicate Finder finds similar parts and surfaces them for human review. It does not automatically fix the catalogue. When two PartLogic SKUs are true duplicates, open the new / keeper part in /stock and supersede the old PartLogic SKU so searches for the old part redirect to the keeper.

Overview

Open Duplicate Finder from Reports Hub (catalogue reports sit alongside the operational reports covered in Reports basics). Treat every row as a candidate: confirm the match yourself, then supersede only when you intend the old PartLogic SKU to redirect to the keeper. Background on why codes fragment is in Product identifier fragmentation.

1. Open Duplicate Finder

Expand Reports Hub in the sidebar and open Duplicate Finder. The Dashboard may also surface duplicate-description signals under Needs attention—still open the full report to review and export candidates.

2. Review similar-part candidates

The results table lists each part alongside potential matches. Typical columns include:

  • Code — the PartLogic SKU for the row
  • Description — catalogue description
  • GTIN, URL, Manufacturer Code, Device Physical
  • Potential Duplicate Codes — candidate codes flagged as similar
  • Potential Dupe Desc — descriptions of those candidates
  • Duplicate Match Reason — why it was flagged (for example SimilarDescription)
  • Is Potential Duplicate — typically True for listed candidates

Compare codes and (where present) GTIN / manufacturer data. Open a candidate in Parts (/stock) if you need the full Summary and Site rows before deciding which code is the keeper.

Duplicate Finder results—similar-part candidates for review. Product descriptions are redacted in this guide screenshot.

3. Supersede the old code

Warning: Superseding is permanent and cannot be reversed. Before continuing, clear all inventory from every Device linked to the product. The portal will prevent the action while Device inventory remains.

To fix a confirmed duplicate, open the new / keeper part in /stock. Use Supersede another code, enter the old PartLogic SKU in the portal field Stock Code to supersede (literal UI label), and confirm. Searches for the old PartLogic SKU then redirect to the keeper.

  1. Decide which PartLogic SKU should remain the governed part (the keeper).
  2. Clear inventory from every Device linked to the product you will supersede (the portal blocks superseding while Device inventory remains).
  3. Open that keeper in Parts / /stock (search by part or PartLogic SKU). Use Include soft-deleted if the record is not in the default results.
  4. Choose Supersede another code.
  5. Enter the old PartLogic SKU under Stock Code to supersede and complete the action (or choose Cancel superseding to abort).

Do not assume Customer Site or Device records are transferred as part of superseding unless you have confirmed that in your environment. Whether historical transactions appear on the keeper after superseding has not been recently verified—confirm in your tenant if you rely on that behaviour.

Supersede another code—start superseding from the keeper part.
Supersede form—keeper PartLogic Part Number, Description (redacted here), and Stock Code to supersede for the old code.

Next steps

← Data qualityReports basics →