Property listings are your organization's catalogue of what you have to sell — the projects, the unit types within them, and what each one costs a given buyer. It replaces the spreadsheet that usually lives on one person's laptop.
Listings are managed by the owner and admins. Agents do not edit the catalogue; they work from what you publish into it.
One project, many unit types
A listing has two levels. The property holds what is true of the whole development: name, address, description, amenities, photos, and what is included in the cost. Underneath it, unit types hold what differs — floor area, rooms, price.
First define the options that vary — Type A / Type B, Corner / Intermediate, Phase 1 / Phase 2. Then add unit types one at a time with Add Variant, choosing a combination of those options for each. The picker only offers combinations you have not used yet, so you cannot create the same unit type twice or invent one that does not exist — but you decide which ones are real, rather than having every possible combination created for you.
Pricing
Price sits on the unit type, and each one can carry a separate price for Bumi, Non-Bumi and International buyers — the reality of Malaysian developer pricing, rather than one price with the differences kept in someone's head.
Each price entry records:
- Selling price — the headline figure.
- Rebate price — what the buyer actually pays after discount.
- Cashback — entered by you. If it is simply the gap between the two, use the fill button beside the field to drop in selling price minus rebate. It is a button rather than something automatic so that a cashback you typed on purpose is never overwritten while you edit a price.
- Availability — per buyer type, because a Bumi lot can be gone while the same unit type is still open to others.
You control what is shown: rebate and cashback each have their own toggle, so a listing can present a discount, a cashback, both, or neither.
Getting a catalogue in
Entering a large development by hand is slow, so listings import from a spreadsheet. Download the template from the listings page — it comes prefilled with your team's usernames and owner emails, so the columns that have to match an existing record are not guesswork.
Rows are grouped by Slug: rows that share one become the same property, and each becomes a unit type under it. So a 40-unit development is 40 rows sharing a slug, not 40 separate properties.
Import is for getting a catalogue in, not for editing one that is already there. A slug that already exists is skipped rather than updated, and categories, amenities and specifications are not part of the spreadsheet — set those in the app after importing. Rows that cannot be read are reported with their spreadsheet row number and the reason, so nothing is dropped silently.
Sharing a listing
Open a property and export a PDF — a brochure for the whole development, listing every active unit type with its pricing and a price range across them, ready to send to a client.
Public listing pages, where buyers browse your catalogue themselves, are part of the Online Presence add-on and are not available yet.
How it connects
Listings are not a silo. Categories come from your own category tree, so a property is filed the same way your leads are. Case Declaration links a closed deal to the specific unit type that was sold — which is what lets a commission trace back to a real unit rather than a typed-in name.