Pricing land in Kashmir: marla, kanal, and the rate trap
Land here is quoted as a rate, not a lump sum. Storing only the total is how listings end up with prices nobody recognises.
Ask what a plot costs in Srinagar and nobody says "ninety-nine lakh, ninety-nine thousand, seven hundred". They say "one lakh per marla". The rate is the number the seller has in their head, the number the buyer negotiates, and the number everyone repeats.
Software that stores only the total quietly loses that.
The units
- Marla — 272.25 square feet. The everyday unit for a plot in town.
- Kanal — twenty marla, 5,445 square feet. The unit for anything substantial.
- Acre — 43,560 square feet, roughly eight kanal. Used for land outside town.
A listing that says "10 Marla" and "₹1,00,00,000" is complete only if you can also get back to "₹1,00,000 per marla". If the system computed the rate by dividing, you would get exactly that. But run it the other way — store the rate and multiply — and something better happens: the total inherits the rounding instead of inventing it.
Why the direction matters
Sellers quote round rates. Nobody says "₹99,999.70 per marla". They say a lakh. If your system stores the total and derives the rate, then the moment an area is anything but a whole number you get a rate with a tail on it, and the listing page shows a figure the owner would not recognise.
Store the rate as typed. Store the area as typed. Let the total be the thing that comes out. The total is what search ranges and sorting need, so it still has to exist and be authoritative — but it should be the derived number, not the source of truth.
BluPlots keeps all three on a plot: `ratePerUnit`, `areaValue` with its `areaUnit`, and `price` as the authoritative total. Rate-priced property types fill in the first two and the total falls out. Everything else — a flat, an office — sets the total directly, because that is how those are quoted.
The frontage question
For a shop, the rate is not the whole story either. Frontage — the width facing the road — can matter more than the area behind it. Two shops of four hundred square feet, one with eighteen feet of frontage and one with nine, are not the same asset and should not carry the same price per square foot.
This is why a single "area" field is not enough for commercial stock. The form for a shop asks for frontage and road width; the form for a plot asks about road access and whether it is a corner. Different property, different questions.
A practical rule
If the person selling it quotes a rate, store the rate. If they quote a total, store the total. Do not make the software guess which kind of transaction it is looking at — ask the form to know, and let the record keep both the number that was said out loud and the number that has to be searchable.
Try it on your own pipeline
BluPlots is the CRM these notes come from. Free for 15 days, no card required.
Start free trial