How to read absorption data — and why it matters more than price

The two ways to express it

Absorption is expressed either as a rate — units sold per month — or as months of inventory, which is the remaining unsold stock divided by the monthly sales rate. Both are useful and they answer slightly different questions.

Units per month is the operational number: it tells a sales team whether they are on plan this month. Months of inventory is the financial number: it tells the CFO how long the project will carry cost before revenue completes, which drives the interest burden and the peak funding requirement.

For underwriting purposes, months of inventory is the more important of the two, because it is the input that determines whether a project's finance cost assumption is realistic.

Why it leads price

Prices in Indian residential are sticky downward. A developer facing slowing sales has strong reasons not to cut the headline rate: it signals weakness to the market, it antagonises buyers who already transacted, and it resets the reference point for every future negotiation. So the initial response to weakening demand is almost never a price cut.

Instead, the developer holds the rate and concedes in less visible ways — a floor-rise waiver, a free parking slot, an extended payment plan, a stamp-duty contribution. Meanwhile velocity has already fallen.

The consequence is that anyone watching price sees nothing for two or three quarters after the market has turned. Anyone watching absorption sees it immediately. This is the single strongest argument for making velocity the primary indicator in any market read.

Getting a usable comparable absorption figure

The difficulty is that absorption data is not published reliably. Developers report bookings rather than registrations, report selectively, and have every incentive to present velocity favourably.

A workable approach combines several imperfect sources. Registered transaction records give a lagging but hard count of completed sales. RERA quarterly updates disclose inventory positions that can be compared period to period. Channel partners who sell the catchment daily have an accurate if anecdotal read on which projects are moving. And site-level observation — how many visitors, how full the gallery is on a Sunday — is crude but informative.

None of these alone is sufficient. Triangulated, they produce a directional absorption estimate that is considerably better than a developer's own projection.

• Registered transaction counts by project and period — hard but lagging
• RERA quarterly update inventory disclosures, compared across periods
• Channel partner intelligence on which projects are actually closing
• Site observation of footfall and gallery activity
• Bank and lender channel views on disbursement volumes by project

The underwriting error that costs the most

Developers typically underwrite realisation carefully and absorption casually. The absorption assumption is the more dangerous one, because it drives cash flow timing, peak funding and interest cost — and because its error is invisible for a long time.

Consider a project underwritten to sell 400 units in 24 months that in fact takes 36. The revenue is not lost; it arrives later. What is lost is twelve additional months of finance cost on a large exposure, plus — almost invariably — the discounting the developer resorts to in month twenty-six when the lender starts asking questions. The second cost usually exceeds the first.

The discipline that prevents this is simple and uncomfortable: build the absorption assumption from the observed velocity of genuinely comparable inventory in the same catchment, then stress it downward by a meaningful margin, and check whether the project still works. If it does not survive a 25 percent slower absorption case, the plan is fragile regardless of how good the location is.