News
tech

A Listing Feed Is a Scheduled Copy, Not a Live Window

A listing feed is a file your system publishes, and each rental site copies it on its own clock. Rentsync pulls rent and availability roughly every two hours while photos can take 12 to 24 hours, so a unit can be correct in your software and stale on the portal.

A listing feed is a file your property management system or listing provider publishes, stating the current condition of every unit you market: rent, availability, unit type, photos, contact details. Each rental site reads that file on a schedule it controls, then stores its own copy. What renters see is the copy, not your record.

That one distinction settles three things operators get wrong: how fast a change shows up, which system wins when two of them disagree, and why some ads ignore your feed completely.

The portal reads your feed, your feed does not reach into the portal

Syndication is a pull, not a push. Showdigs describes it to its own users as a passive process in which the networks read your published information periodically. Your side can be instant and the public result still lags, because the schedule belongs to whoever is reading.

The published intervals are short but not trivial. Rentsync says its Infinity Network rental listing sites pull the most important data, such as rent and availability, approximately every two hours, while photos and other media can take 12 to 24 hours to update. Showdigs tells its users that Zillow, Zumper and Realtor.com each monitor its feed several times a day, with a window of four to six hours, and that Apartments.com updates listings once a day at noon Eastern.

Note the split between data types. Availability moves on one clock and photos move on a slower one, so a unit can show the new rent beside the old photos for most of a day.

Each hop adds its own delay, so add them up

Most small operators have two hops: source system to feed provider, feed provider to portal. Anyone on an integration has three, and the delays stack.

Rentsync spells this out for feed-integrated accounts. It has to pull the updated data out of your property management system before it can change its outgoing feed, which it describes as taking up to six hours, and then the rental listing site pulls from Rentsync, which adds up to three more. Rentsync asks clients to allow 24 to 48 hours for changes to appear before reporting a problem. RentEngine, which sends its data in real time, still tells users it can take up to 24 hours for a change to be reflected on a listing website.

The number you should plan around is the sum of the worst case at each hop, not the fastest figure any one vendor quotes. For a three-hop setup with a photo change in it, a full day is normal and not a fault.

The source system wins, so the portal is the wrong place to fix a mistake

Editing the copy does not change the original, and the next read overwrites your edit. Aptly puts the rule plainly in its own documentation: property management system marketing data may overwrite an edit when the integration does not support bidirectional sync.

The same page carries the sharper warning. Visible editing controls do not establish which system owns a synced field. An edit box on a portal is not evidence that the portal owns the value. It means the portal will accept typing.

So a wrong rent gets corrected where the data originates, then verified on the portal once the interval has passed. Correcting it on the portal produces a fix that looks right for a few hours, disappears without warning, and teaches you nothing about which field was wrong.

Some stale ads are not yours to change at all

This is the case that convinces people their feed is broken. The unit rented three weeks ago, the feed says so, and the ad is still running.

RentEngine lists the usual culprits for a listing that shows outdated information: old showing or leasing software, the property management system itself, an MLS feed, or a duplicate somebody posted by hand. Its position is blunt, and it applies to every provider: it cannot control listings published by other systems. The fix is to remove or disable the duplicate at the source that created it.

A ghost ad is not only an embarrassment. It generates enquiries for a unit that does not exist, which distorts what you believe about demand, and it muddies the gap between days on market and days vacant.

How to work out your own lag

  1. Write down every hop between the unit record and the live ad. Name the source system, any feed provider in the middle, and each portal.
  2. Ask each vendor for two intervals, not one: how often availability and rent are read, and how often photos and media are read.
  3. Add the worst case at each hop. That sum is your real lead time for price changes and availability flips.
  4. Test it once. Change one field at the source, note the minute, then check each portal until it lands. Keep the result somewhere your leasing staff can see it.
  5. Search your own unit address on each major site and on a plain web search. Anything you find that your feed does not control has to be taken down where it was published.

What changes once you know the number

Availability flips stop being same-day work. If your worst case is a day, a unit coming off the market on Friday needs the record updated Thursday, or you spend the weekend answering calls about it. Price changes get entered before the rent is advertised anywhere, not after a prospect quotes the old number back at you. And a portal that still shows the wrong thing after the interval has passed becomes a real signal worth reporting, rather than a guess.

None of this makes a feed less useful. It makes the gap between your records and the public record a known quantity, which is the difference between a system you manage and one you argue with. If your enquiry volume is weak even on accurate listings, that is a different problem from reach.


Back to all articles