PlanMaker 2026 · Data cleanup · Beginner

Remove Duplicate Rows in PlanMaker Without Losing Records

Remove genuinely identical rows in PlanMaker 2026 and distinguish whole-row duplicates from repeated IDs that hold different information.

Official documentation reviewed; native application verification pending · Updated 10 October 2026 · Editorial standards

A repeated SKU is not necessarily a duplicate row. If two warehouses carry the same item, both entries may be valid. In PlanMaker, the documented Remove duplicate rows operation compares the selected columns, so your selection determines what counts as a duplicate.

Practice file and expected result

Download warehouse records CSV. The six data records include two exact repeats. The correctly deduplicated table contains four distinct records.

SKU Warehouse Quantity Keep?
A1 North 2 Yes
B2 South 5 Yes
A1 North 2 No: repeat
A1 South 3 Yes: different warehouse
C3 North 7 Yes
B2 South 5 No: repeat

Remove only complete-row duplicates

  1. Save a backup. Removing duplicates changes the dataset, and a mistaken deletion may be difficult to reconstruct later.
  2. Select the full data area across SKU, Warehouse and Quantity, not just SKU.
  3. Use Data → Edit → Remove empty rows → Remove duplicate rows (ribbon wording documented by SoftMaker).
  4. Read any prompt asking whether to delete entire worksheet rows or only the selected cells. Deleting only a rectangular portion can misalign nearby columns.
  5. Verify that the record A1,South,3 still exists, while the repeated A1,North,2 and B2,South,5 are gone.

Why selecting just the SKU column is risky

Selecting only A1:A7 makes both A1,North,2 and A1,South,3 look alike by the chosen column, even though the full rows differ. If you actually need one row per SKU, first decide whether to sum quantities, select the newest record, or flag conflicts; simply deleting records can lose stock information.

Troubleshooting

  • A duplicate survives: invisible spaces, different letter case or a quantity stored as text can make entries unlike each other.
  • Rows are misaligned: undo; include all columns and choose whole-row deletion appropriately.
  • Two warehouses collapsed into one: restore the backup and de-duplicate the entire record, not only the identifier.

Related: Filter a sales table and create a pivot summary.

Verification: Input and four distinct expected records were checked using a separate data-processing script. Menu steps are referenced to SoftMaker’s documentation, not native PlanMaker execution.


Official documentation: Software manual or vendor release notes. This article is part of a staged content batch; confirm the interface and output in the stated software before public deployment.