Skip to content
HomeHome
DE
WhatsAppMailPhone
← All articles
Sold three weeks ago, the phone still rings: keeping property listings in sync instead of updating four forms by hand
Coding

Sold three weeks ago, the phone still rings: keeping property listings in sync instead of updating four forms by hand

To add visual value to my articles, I create fitting cover images with the help of artificial intelligence, matched to the actual content of the piece.

A prospective buyer calls about a flat that sold three weeks ago - one portal never got the memo. Why a listing is a copy, not a live view, what the German OpenImmo data standard actually solves, and how portals, your own site and Facebook Marketplace can all stay in sync from a single source.

Eric MengeAuthorEric MengeOwner & web developer at EMIT Solution
Published
Reading timeca. 10 min

In short

  • A portal listing is a copy, not a live view. Once entered, a major portal has no way of knowing about a later change at the source until someone manually comes back and updates it.
  • The risk sits in taking a listing down, not in publishing it. Properties get marked sold or reserved exactly when the notary appointment or handover takes priority - deactivating the remaining channels has no urgency in that moment, until the phone rings weeks later.
  • For the major portals, a data exchange standard already exists in Germany (OpenImmo) - but it only helps once your own listing data already lives in structured form inside a connected system, not in a spreadsheet or in your head.
  • A single structured record per property can be built without a full agency software suite: feed your own website straight from it, connect the major portals through their interface - and for channels without one, like Facebook Marketplace, exactly one deliberate manual step remains instead of four.

A prospective buyer calls about a two-bed flat from a listing that just caught their eye. It sold three weeks ago. The caller has no way of knowing, because the portal listing doesn’t know either - it still shows the flat as available, same price, same photos. For the agent, it’s the third call like this this week, and every time the same short, awkward explanation follows. The agent’s own website and the second portal had long since taken the listing down. Only one platform never got word that it had sold.

The property itself was never the problem. Sold is sold, the notary appointment is done. The problem is that this one fact lives in four different places online - and only three of them were updated.

With a completed sale, the mismatch eventually surfaces because someone calls. With a price cut, it slips through more quietly: for a week the listing sits at 349,000 euros on one portal and still at 359,000 on the other - both figures were correct once, just entered at different times. Nobody calls indignantly over that, but anyone who finds both listings side by side has every reason to wonder which number is real and how closely the listing is actually being maintained.

A listing is a copy, not a live view

List a property on a major portal - in Germany that typically means ImmoScout24 or Immowelt - and you type address, price, size and photos into a web form. What you create is a record inside the portal’s own system: not a view onto your own files, but a copy of them, frozen at the moment you typed it in. Change anything at the source afterwards - the price, the status, a new photo - and the portal has no way of knowing. There’s no line back to your own records. The copy stays exactly as it was until someone manually comes back and touches it again.

Across four channels - two portals, your own site, maybe a Facebook Marketplace post - the same fact now exists four times, independently of each other. Nothing holds them together except your own memory to update all four whenever something changes.

Multiple monitors on a desk Photo: rpnickson / Unsplash

Listing gets your full attention. Taking down doesn’t.

Publishing a listing almost always gets the care it needs: good photos, a considered description, the right price, every channel covered. That’s the moment you’re trying to win a new mandate - nothing gets forgotten.

The switch to reserved or sold happens under the opposite conditions: right when other things take priority - the notary appointment, the handover, the next listing that’s already waiting. There’s no signal in that moment reminding you that three more copies of the same listing are still sitting online somewhere. Miss one, and you won’t notice right away - you’ll notice weeks later, on the phone, when someone asks about a flat that’s long gone. Attention is maximal when listing, minimal when taking down, even though the risk sits in exactly the same place.

A checklist for the closing moment sounds like the obvious fix, but it only helps if it actually surfaces at the exact moment the status changes - and that’s precisely the moment when too much else is already competing for attention. A reminder you first have to remember to check isn’t a reliable reminder. What actually holds up is a chain that keeps running on its own once the one source has been updated - not one more line on a list that gets buried next to the notary appointment and the handover.

There’s already an interface for this - just not for everyone

The real estate industry solved this problem years ago, just not for every office. Germany has an established data exchange format for it called OpenImmo, an XML standard that ImmoScout24, Immowelt and mainstream agency software have supported jointly for years. It lets listing data and status changes pass through machine to machine, without filling in a form a second time. It carries more than just price and status - the whole listing travels through it: size, year built, energy certificate figures, photos, the description itself. Run a full agency software suite, and you change the status once in your own system; the portals pick it up automatically.

The catch: this route assumes your own listing data already lives in structured form inside such a system - not in a spreadsheet, not in your head, not scattered across an email thread. That’s exactly why the interface goes unused at plenty of smaller offices: full agency software suites bundle client management, commission accounting and scheduling that a solo agent often doesn’t need - but force your entire workflow into their shape, just to get access to that one interface.

A laptop showing a website Photo: zulfugarkarimov / Unsplash

Where the one truth can actually live

Solving the underlying problem doesn’t require a full agency software suite - just one structured record per property: address, price, status, the handful of facts every channel needs. How much that one record needs to hold depends on how many properties you run - a smaller office is often well served by a single well-kept table with one row per property and a last-changed date. What matters isn’t the tool behind it, but that there really is only one of it, instead of a copy sitting in every portal account. From there, the connection to each channel looks different, because each channel works differently.

Your own website is the easiest case, because you’re in full control: it can read the listing data straight from that same source, with no second manual step at all. For the major portals, a lean integration - sized to your actual number of listings, not a whole suite - can pass status changes through the interface described above. Facebook Marketplace has no comparable interface for property listings; that stays a manual step. But just one, triggered by the same status change, instead of one of four you have to remember under time pressure.

One source, every channel - built around your listings

How many properties you run at once, which portals actually matter, whether your own website can display the data directly, and whether an integration with ImmoScout24 or Immowelt pays off - all of that differs from office to office. Which is exactly why I build this tailored to the office in question rather than selling off-the-shelf agency software: one person who designs and understands the integration themselves, no agency overhead and no software you first have to adapt your workflow to.

If you want to know what a single source of truth could look like for your listings and your channels: I’m Eric Menge of EMIT Solution, reachable at info@emit-solution.com and via emit-solution.com. The first conversation costs nothing and simply clarifies whether the effort is worth it for your portfolio.

FAQ

Why doesn't a portal automatically know when a property has sold?+

Because a portal listing is its own record inside the portal's system, created through a form you filled in once. There's no technical link back to your own files that would pass a later change through automatically. If the status only changes at the source, the listing sits there unchanged until someone updates it by hand.

What is the OpenImmo standard, and does it help smaller offices too?+

OpenImmo is an XML-based data exchange format used in Germany to pass listing data and status changes between agency software and the major portals such as ImmoScout24 or Immowelt. It only helps once your own listing data already lives in structured form inside a connected system - it does nothing for a spreadsheet or a set of loose notes.

Do I need a full agency software suite to keep everything in sync?+

Not necessarily. Large software suites bundle client management, commission accounting and scheduling that a solo agent often doesn't need, while forcing your entire workflow into their shape. For the specific problem - one source feeding every channel - a lean, tailored connection to the same interfaces is usually enough.

Can Facebook Marketplace be kept in sync automatically too?+

There's no interface for property listings there comparable to the major portals, so that stays a manual step. The difference is that it becomes the only remaining step, triggered by the same status change at the source - instead of one of four you have to remember under time pressure.

Where should a property's status be changed first?+

Always at the one structured source, never in whichever portal happens to be open. Only if the status lands there first can everything else - website, portals, the last manual step - reliably follow from it. Change it here one day and there the next, and you're straight back to the same drift that caused the problem.

Want to know more?

In a free intro call we discuss how you can use these topics for your company. Not a sales pitch, but an honest assessment.

Book a free intro call