Portal feed change requests & standard settings (UK only)

This guide has been reviewed against our global client base and classed as relevant to the UK only

This article explains the types of portal feed changes which can be actioned and delivered by Reapit support and also includes an outline of good practice / standard settings - it covers:

A portal feed is a formatted and defined feed of property data to either your own website, or to a property portal (such as Rightmove, Zoopla, OnTheMarket, Boomin)

Portal feed change request types

The list below outlines changes that can be made to your portal feed

A number of portals are defined as standard and non-chargeable - all supported portal feeds can be found in the Reapit Business Service Catalogue

When setting up a new portal feed, the configuration will default to be that of the main portal that you are already feeding to

Apart from office-level configurations as stated below, all changes are carried out at company and portal feed level as standard

1. Portfolio changes

Portfolio changes relate to which properties will or won't be sent to the property portals or company website

Portfolio change requests should be referred via your local key contact - it is also advised to discuss this with your Reapit Client Success Manager (CSM), where possible, to validate the impact of any changes 

Portfolio-related changes are usually set at the company level (i.e. they are not specific to portals and/or offices)

Change type

Example

Change type

Example

Send exchanged properties as SSTC

Used when properties that are sold are still to be displayed online

Portal provider best practice is that this should not be done

Portal providers (Rightmove explicitly) will remove SSTC and sold properties after 60 days

Let Agreed
(Unavailable/Available)
and 
Arranging Tenancy (Unavailable/Available)

Used when properties with the status of Let Agreed or Arranging Tenancy should still be marketed

Possible with Rightmove Real Time Data Feed (RTDF) but not on other portals

2. Template/format changes

Template changes relate to how property data is presented online, this usually relates to items such as marketing or room descriptions

Template changes do not include the mapping of how property status is presented (e.g. SSTC being presented as Available) - see sections 1 & 3 (above/below) for information on status changes  

Change type

Example

Change type

Example

Additional marketing information

Marketing screen fields, while not standard, can be easily added and configured, such as directions, location & situation

Display address format

Determines how an address is displayed on the portal

Property URL

Present/remove a URL back to your company website

The URL would then need to be able to be generated from information contained against property 

Details/particulars URL

Present/remove a link to a brochure for a property (often a PDF)

Standard brochures are those created within AgencyCloud, accessed by utilising PDF.php or to your company website

Images (default is 20)

The number of images that are sent to a portal

This can be specific to individual properties and should not be set to accommodate one particular property

Some portals also have constraints

3. Attribute and mapping changes

Mapping changes relate to either:

  • how a property status is represented online, e.g. Arranging Tenancy - Available displayed as To Let
    OR

  • how an attribute mapping is represented, e.g. semi-detached bungalow displayed as Bungalow

Standard mapping changes are the same as portfolio changes (see section 1 above) - but mapping changes apply when properties are already being sent to portals and a change is required to present the properties differently

Where attribute mapping is involved, there will always be an impact on the portal feeds and approval will be needed

Requests for mapping changes or new property attributes need to be managed and approved via your key approving contact -  it is also advised to discuss this with your Reapit Client Success Manager (CSM), where possible, to validate the impact of any changes

Change type

Example

Change type

Example

Send exchanged properties as SSTC

Used when you want properties that are sold to still be displayed online

Portal provider best practice is that this should not be done

Portal providers (Rightmove explicitly) will remove SSTC and sold properties after 60 days

Let Agreed
(Unavailable/Available)

and 

Arranging Tenancy (Unavailable/Available)

Used when you want to continue marketing properties that have the status of Let Agreed or Arranging Tenancy

Possible with Rightmove Real Time Data Feed (RTDF) but not on other portals

If you're not yet ready to upload a property to the internet, enable No Internet Advertising in property Marketing
Or use the relevant Disable Portal option to prevent the property being uploaded to a specific portal.

New Attributes

When you need a new property attribute adding or a change to an existing one

4. New data fields

Standard additions that allow fields to be sent to your own website

New data fields relate to your own company website feed and are usually scoped as part of the onboarding process

The list below contains standard additional fields that can be captured, anything in addition to this would be considered a development request

Change type

Example

Change type

Example

Exclusive flag

Specific when sending data to OnTheMarket

Property manager

 

As stated in AgencyCloud

Negotiator

Lat/Long

5. New office & office changes

When an office needs to be added to an existing portal feed, or where changes are required that are specific to an office - office changes relate specifically to OnTheMarket's Early Bird or Lettings Fee based data only

Currently, these are the only office-based configurations allowed

Change type

Example

Change type

Example

Lettings Fee Text

Used when you want to maintain Lettings Fee text for an office

Early Bird

Used when sending data to OnTheMarket, you may require a delay (of a set amount of time) when sending properties to other portals

To support customers working within a franchised model, this can be set at office level

Best practice / standard settings

Standard status mappings (RTDF)

The following are standard for Small Business/Agency clients - these mappings can be amended (on request) for Enterprise clients

Status in AgencyCloud

Status on portal

Status in AgencyCloud

Status on portal

Sales

For Sale - Available

Sold STC - Available

Sold STC - Unavailable

Reserved

Exchanged (date within 60 days)

 

Available

SSTC

SSTC

Reserved

SSTC

Lettings

To Let - Available

Tenancy Current - Available

Under Offer - Available

Arranging Tenancy - Available

 

Available

Available

Let Agreed

Let Agreed

Descriptions

As standard, the following descriptions in AgencyCloud are sent to the portals - additional descriptive fields can be added for Enterprise clients and configured to send in the feeds as required

Description in AgencyCloud

Area on portal

Description in AgencyCloud

Area on portal

Description on main property screen

Summary property description

Seen on initial list after carrying out a search

Description on main property screen, plus Long Description and Situation from property Marketing screen

Detailed property description

Seen on the individual property listing page

Accommodation summary / key features

  • The Accommodation Summary from the Rooms screen is sent as standard
    In order for this to be sent, the Details Approved box must be ticked (in Rooms)

Configuration options

Some standard configuration options that are enabled by default are:

  • Only Exchanged status properties that have an exchange date within 60 days are delivered in the feed (related to status mappings)

  • Sending property details/particulars (if present on property record)

 

Related articles