Karim El KanfoudThe website shows an apartment as available. For a prospective buyer, that is a good reason to contact the sales team. But if sales has already reserved the unit, they first have to explain the contradiction before the conversation can move on. Everyone may well have done their part correctly. The change simply has not reached the website yet. A reliable apartment status therefore needs an agreed route from approval to the published display.
A managed website needs this route just as much as an automatic data feed does. In both cases the team has to attach the same meaning to each status and know which record applies when two views disagree.
First agree what "reserved" means
"Reserved" can mean different things in a sales process, from an internal commitment to a completed agreement with the buyer. The project decides which event triggers the publicly visible status and who may approve it. It also needs a rule for when a reservation ends and from which step the website shows an apartment as sold.
Once these rules are written down, sales and the people looking after the website work from the same basis whenever something changes. Each status comes with the triggering event, the person responsible, the moment of publication and the possible reversals. The wording on the website reflects exactly this meaning. Otherwise buyers read a commitment into a label that the actual process does not support. An explanatory note helps, but it does not replace agreement within the team.
Every change needs a clear route
One authoritative source means the team knows, for every item of information, where the approved version is kept. Prices, floor plans and project copy do not have to sit in the same application for that. Sales can own availability while the planners supply new floor plans. A short overview makes this split easy to follow: who maintains which field, where the valid version is kept and which channels it goes to.
A fixed apartment ID keeps the connections intact, even when the visible number of a unit changes. The building model, list, detail page and enquiry must still refer to the same apartment. Otherwise even a correctly recorded status ends up on the wrong unit. What matters most is clear responsibility for each item of information and its publication.
For the KMUseiten Project Website, the published scope is a managed website. Within Operation & Maintenance (CHF 290 per month from launch) we handle up to four changes per month, for example to prices or status. Valenne, a fictional demonstration project built by KMUseiten, uses the same apartment data for the building model, list, detail pages and comparison, so the information belongs together across the whole site. How these views work together for buyers is covered in the article on apartment selection on a project website. The project team decides who approves a change, passes it on to us and checks it after publication.
With a data feed, plan for interruptions too
If a website takes changes automatically from another system, two more questions arise: how often does the sync run, and what does the website show when it is interrupted? The STIMO case study describes such an external data feed. meinwohntraum.ch takes its listings from CasaSoft, new properties appear and sold ones disappear. How that implementation deals with reservations, how often it updates and what happens after a failed import is not stated in the case study. These details therefore cannot serve as a specification for another project.
For a new connection, the team clarifies among other things what a missing apartment record means. It can be a deliberate removal, but just as well an incomplete transfer. If the source delivers an unknown status, the interface reports a visible error instead of quietly showing the apartment as available. Rules like these let whoever looks after the website restore the correct state without having to guess at the sales situation.
Before launch, take one apartment through every step: available, reserved, released again, sold. The team checks the source and the website views along the way. In the end buyers see only the status label, and sales has to stand behind it. A clear meaning, one authoritative source and a complete route from approval to publication give sales the basis to do so.
