FAQ · Duplicate Row Reconciliation

Oopbuy Spreadsheet Duplicate Row Reconciliation FAQ

Keep each answer tied to the evidence needed for this duplicate row reconciliation, not to a broad product or service claim.

Identity questions for this duplicate row reconciliation

Is a matching title enough to merge rows?
No. Compare final URL, item identity, visible options, and evidence context.
What is an exact duplicate?
Two rows whose identity, selection, evidence source, and intended task are materially the same.

Conflicts questions for this duplicate row reconciliation

What if one row has a newer URL?
Preserve the redirect or replacement history before choosing the surviving row.
Should different variants be merged?
Only into a parent record that keeps each option distinct; otherwise retain separate rows.

Audit questions for this duplicate row reconciliation

Why record discarded fields?
They explain what was reviewed and prevent useful context from disappearing silently.
When should a pair remain unresolved?
When source identity, option mapping, or evidence timing cannot yet be reconciled.

Decision record

Separate known fields, missing evidence, and the next check

The record is useful when it shows both the current decision and the evidence boundary that could reopen it.

Known now

Decision column 1: known now must remain explicit in the saved record.

Not observable

Decision column 2: not observable must remain explicit in the saved record.

Conflict retained

Decision column 3: conflict retained must remain explicit in the saved record.

Next evidence

Decision column 4: next evidence must remain explicit in the saved record.

Carry unresolved details into the next live check

A static answer should never disguise a changing platform detail.

Use the method