Real Estate Technology · InHome engineering note
How we deduplicate property inventory from Cyprus developers
A property data pipeline preserves source identity and sends probable cross-source duplicates for review before publication.
InHome Development · Limassol, Cyprus ·
The same property can arrive through different sources
Cyprus inventory may arrive from developer feeds, manual imports and owner submissions. Names, unit references, prices and media can differ even when two rows describe the same home.
The intake first records where a row came from and maps its fields into a common shape. A feed row is not automatically a new public listing, and a changed value is not silently treated as a verified correction.
Known identity is not the same as a probable match
Within one source, the documented canonical identity uses the source identifier and its source reference. Cross-source similarity is a different question: a probable duplicate needs review rather than an automatic merge.
This distinction protects provenance. It lets an operator compare records, resolve conflicts and retain the source of each fact before the public catalogue reads the canonical record.
Why this matters after publication
A single reviewed property record can feed search, map, AI-assisted discovery and enquiry capture. The buyer sees one coherent listing while the broker can continue from the property that prompted the request.
The business effect is fewer disconnected versions of a property and a clearer correction path. This describes the pipeline’s design, not a claimed reduction in duplicate rate or sales time.