Independent duplicate row reconciliation

Oopbuy Spreadsheet Duplicate Row Reconciliation

Use one row to produce a traceable keep-or-merge decision that another reviewer can reproduce.

Open the Oopbuy Spreadsheet resource Use the method

Current platform facts still require a live check; this duplicate row reconciliation preserves a traceable keep-or-merge decision without presenting changing fields as current facts.

Resource workflow Review workflow

Finish one duplicate row reconciliation before moving to another row

A reconciliation guide for duplicate-looking rows, with keep, merge, split, and unresolved decisions supported by field-level evidence.

  1. 01
    Candidate row pair Record field 1: candidate row pair must remain explicit in the saved record.
  2. 02
    Matching identity fields Record field 2: matching identity fields must remain explicit in the saved record.
  3. 03
    Conflicting fields Record field 3: conflicting fields must remain explicit in the saved record.

Quick FAQ

Short answers before saving the duplicate row reconciliation

Is a matching title enough to merge rows?

No. Compare final URL, item identity, visible options, and evidence context.

What if one row has a newer URL?

Preserve the redirect or replacement history before choosing the surviving row.

Why record discarded fields?

They explain what was reviewed and prevent useful context from disappearing silently.

Record fields

Four fields define this duplicate row reconciliation

For this duplicate row reconciliation, each field preserves a different part of the audit trail so a later reviewer can distinguish evidence from an unresolved question.

  1. Candidate row pair Record field 1: candidate row pair must remain explicit in the saved record.
  2. Matching identity fields Record field 2: matching identity fields must remain explicit in the saved record.
  3. Conflicting fields Record field 3: conflicting fields must remain explicit in the saved record.
  4. Keep, merge, split, or unresolved Record field 4: keep, merge, split, or unresolved must remain explicit in the saved record.

Review path

Move from source context to a traceable keep-or-merge decision

This path protects row identity first, then assembles a traceable keep-or-merge decision; the order makes a later source change visible instead of silently overwriting it.

  • Identify
  • Capture
  • Compare
  • Classify
  • Decide
  • Recheck

No current catalog size, stock, price, or outcome is asserted.

Decision states

Name the state instead of hiding uncertainty

Exact duplicate

Decision state 1: exact duplicate must remain explicit in the saved record.

Same item, different option

Decision state 2: same item, different option must remain explicit in the saved record.

Redirected replacement

Decision state 3: redirected replacement must remain explicit in the saved record.

Unresolved lookalike

Decision state 4: unresolved lookalike must remain explicit in the saved record.

Reusable output

The output is a traceable keep-or-merge decision

A second reviewer should be able to retrace the source, compare the saved fields, and understand why the decision remains settled or open.

Candidate row pair

Required evidence 1: candidate row pair must remain explicit in the saved record.

Matching identity fields

Required evidence 2: matching identity fields must remain explicit in the saved record.

Conflicting fields

Required evidence 3: conflicting fields must remain explicit in the saved record.

Keep, merge, split, or unresolved

Required evidence 4: keep, merge, split, or unresolved must remain explicit in the saved record.

Stop rules

Pause when the record would erase an important uncertainty

A narrow unresolved state is more useful than a confident field assembled from mismatched evidence.

  • Two rows share a title but not a final source.
  • Option or variant differences would be lost by merging.
  • One row has newer evidence but no change history.
  • The original source is unavailable.
  • The merge would discard a useful review date or open question.

Start the duplicate row reconciliation from the resolved source

Keep the a traceable keep-or-merge decision dated and tied to one exact row.

Follow the method