How to Handle Conflicting Shop Data: Duplicate Names, Multi-store Brands, and Old Thread Variations
A single name can represent branches, multiple historical threads, or different pages from one shop. Instead of choosing a convenient value, keep a clear conflict-handling flow: verify, annotate, or hide.
Duplicate names: separate by official site and area context
Same-brand names do not always share the same terms. Confirm official domains, registered address, and whether it is the same operating brand before merging data.
Multiple threads: keep the latest and keep history visible
When multiple historical records exist, keep the latest valid thread as the primary record and use older versions for trend checks. A newer date does not automatically mean complete information.
Conflicting fields: use conservative labels and verifiable fields first
If price, hours, address, or area differs, do not average or guess. Prioritize verifiable fields and mark conflicts explicitly as “needs confirmation” or “official sources differ.”
Handling Long-Quiet Listings
When key official fields stop updating for an extended period, ranking confidence is reduced and users are prompted to re-verify. Historical records are not deleted immediately; they are flagged as requiring fresh checks.