Automated real estate listing feeds from one database

A feed is a file with a list of listings that a portal downloads from a link on a regular schedule. For each unit it contains the address, size, price, photos, description and status. The developer doesn't have to post listings by hand: you give the portal the link once.

Smart plan builds that file from your project data. The project, phases and units are set up once, and the site plan, availability chart and CRM all run on the same data. So a sold unit can't stay on a portal at the old price: by the next export it is gone.

Exporting listings automatically from your CRM saves more than time. It removes a whole class of errors where a buyer calls about a listing, the unit is already sold, and the sales rep spends the call apologizing instead of offering a similar option.

• Open "Modules" → "Export to portals" and select a project.
• Click "Feed" and check the portals you want.
• Copy the link and paste it into your portal account.
• If needed, edit an individual listing by hand.
• From then on prices and statuses update on their own: once a unit is sold, its listing comes down with the next export.

Each portal has its own feed format and required fields. Smart plan builds the right format for each one from the same data, so you don't have to maintain a separate file per portal by hand.

Six portals are live today. A few more, including 2GIS, VK, OLX and Domoplaner, are planned, and we don't promise them as ready.

You don't have to connect every portal at once. You can start with one or two where buyers look for your type of property and add the rest later; the price of the export does not depend on the number of portals.

A plot feed is a common headache for communities selling plots for private homes: there are hundreds of similar plots, and they sell fast. Taking sold plots off three portals the same day by hand is next to impossible. With Smart plan the listing comes down on its own as soon as a plot is reserved or sold in the system.

For an apartment complex, what matters is that no apartments stay on the portals at the old price after repricing. The price in the new-build feed comes from the same database as the availability chart on your website.

What you need to fill in for the feed to pass. For a plot: size, the community's address or coordinates, permitted land use, price and photos. For a new-build apartment: building, floor, number of rooms, size, floor plan and completion date. For a house with a plot: house and plot size, building material, floor plan. Each portal requires a different set of fields, and Smart plan takes the feed data from the unit and project records.

If something is missing from a record, the portal may reject the listing or rank it below others. So before the first export it's worth going through the project and adding photos and descriptions: after that they work on your website, in sales proposals and on every portal at once.

The general rule is simple: a feed needs a single source of truth. The fewer places where price and status get edited, the fewer errors buyers and portal moderators will see.

Most portal problems come not from the format itself but from feed data that doesn't match reality. Here is what comes up most often.

• Sold units stay listed. A buyer calls, and the unit is gone. The fix is to take the status in the feed from the same database where the sales rep marks the reservation.
• The portal price doesn't match the website. Usually this means the price list was changed in one place and forgotten in another. In Smart plan there is one price, and if you need a separate price for a portal, you set it explicitly.
• Empty fields in the listing text. Lines like "Promotion: —" look sloppy. Smart plan doesn't put empty promotions into a listing.
• Duplicate listings. They appear when the same property is uploaded to a portal from two sources. Keep one feed per portal.
• No photos or floor plan. A listing without a picture loses to the ones next to it. Photos come from the unit record, so upload them once to the project.
• Wrong property type. A plot exported as a house, or the other way around, may fail the portal's checks. The unit type is set in the project and carried into the feed.

You can set a separate price for each portal: a premium, a discount or a promotion, and decide whether to show the project's promotions there. This helps when you compete on price on one portal but not on another. The price adjuster is enabled on request.

If you already track inventory in another system, Smart plan can pull it from a Yandex Realty or Domoplaner feed link and refresh it every hour. Then you don't have to enter units twice.

Portals decide on their own how often to pull the feed and how long to review new listings. So it makes sense to avoid sharp price changes an hour before an important showing and to schedule promotions in advance with a start date. That way listings are updated on every portal by the day you need them.

You can post listings by hand or build the feed with a separate tool. The difference shows up the moment a unit sells or a price changes.

Listing export is part of one system. Units are uploaded from Excel or from another system's feed, sold through the site plan and availability chart on your website, and reservations are managed in the Smart plan CRM or in yours: Bitrix24 and amoCRM connect in a few steps. When a sales rep moves a deal to reservation, the unit is reserved and taken off the listings.

Website leads go to email, Telegram, Bitrix24 or amoCRM, and buyer actions on the site plan show up in Yandex Metrica. So you can see where a buyer came from: a portal or your own website.

Listing prices are linked to the pricing module. When you reprice in bulk or launch a promotion with an end date, the changes reach the portals together with the website and price lists. When the promotion ends, it disappears from the portals too.