In this section · 3 articles

A property doesn't show up as a match

Work out why a property you expected is missing from a requirement's matches, or a requirement from a property's, from its status and expiry date to a purpose or category that doesn't agree.

Applies to
Property CRM 5.0 and later
Who can do this
Administrator, Team member
Permission
feature.pcrm.property.edit
On this page

Symptom

You open a requirement, and a property you think suits the buyer isn't in its Matches card. Or you open a property, and a buyer's requirement isn't listed. Open both records side by side, then check these in order.

Tip: A match that scores low is still a match. Before anything else, look further down the card: a Fair match can sit below many better ones.

Check these, in order

1. The list hasn't been refreshed

Matches are worked out when the card loads. Fix: select Find More Matches on the requirement, or Refresh on the card.

2. The property isn't Available

Only properties with Status Available are matched. Under Offer, Sold, Rented and Withdrawn aren't. Fix: if the property is back on the market:

  • Under Offer: on the property, select Release offer. Laramin says Listing back on the market.
  • Withdrawn: edit the property and set its Status to Available.

3. The listing has expired

A property whose Listing Expires On date has passed isn't matched, even if its status is Available. The date is checked against today in your business's time zone. Fix: edit the property and move Listing Expires On to a later date, or clear it.

4. The purpose doesn't agree

Requirement PurposeMatches property Purpose
BuyingSale
RentRent
LeaseLease
Joint VentureJoint Venture

A buyer looking to rent never sees a property for sale. Fix: correct whichever record has the wrong purpose.

5. The category doesn't agree

The Category must be the same: Residential, Land / Plot or Commercial. A requirement for a Commercial office doesn't see a Residential apartment. The Property Type doesn't have to agree: a different type only lowers the score. Fix: correct the category on whichever record is wrong.

6. The requirement isn't Active

This applies when you're looking from a property: it lists only requirements with Status Active. On Hold, Fulfilled and Closed requirements aren't listed. Fix: if the buyer is looking again, set the requirement's Status to Active.

7. They belong to different businesses

A requirement only matches properties of the same workspace. Fix: check the Business of each record, if your list shows that column, or switch workspace and look for the property there. Records can't be moved between businesses. See Switch workspace.

8. The property is in the trash

A deleted property isn't matched. Fix: someone who can restore properties restores it from the Properties list's trash. See Delete and restore records in bulk.

9. It's beyond the first 50

The card shows the best 50. When it says, for example, Showing 50 of 120, the rest scored lower. Fix: tighten the requirement, for example with a city, a BHK or a budget, so that better matches rise to the top. See How matching works.

10. There's no Matches card at all

The card is hidden if you can't list the other side: properties on a requirement (feature.pcrm.property.list), requirements on a property (feature.pcrm.requirement.list). Fix: ask an administrator to give you a Property CRM role that includes it. See Give people a Property CRM role.

If the property matches but scores lower than you expect

Check what the score is built from:

  • Price on Request is on, or Budget (max) is empty: budget isn't scored.
  • The property's City is spelled differently from the requirement's. Capitals don't matter, but spelling does: "Bangalore" and "Bengaluru" are different cities.
  • The buyer's Area / Locality must appear inside the property's, or the Pincode must be the same.
  • Area compares Built-up Area (sq.ft). If the property has none, area isn't scored.

Still not working?

Raise a ticket from Support Center in your Laramin app. Include this page's link, the codes of the requirement and the property, and what you checked.