DaysOnMarket Increment

A proposed RESO standard to make DOM data accurate, efficient, and long-lasting — without changing who controls the calculation.

DOM has a shelf life problem. Today, DaysOnMarket goes stale the moment it leaves the MLS. Downstream consumers either re-download hundreds of thousands of listings every night or show inaccurate data. The DaysOnMarketIncrement proposal fixes this with three simple fields.

Today
"DaysOnMarket": 5
Goes stale overnight (rotten banana!)
Consumers must re-fetch to stay accurate
Every hop in the chain makes it worse
Proposed
"DaysOnMarketIncrementYN": true
"DaysOnMarketIncrementBase": 5
"DaysOnMarketIncrementTimestamp": "2026-04-20T05:00:00Z"
MLS still controls the calculation
Accurate for days, weeks, months
Survives every hop without losing accuracy

How it works

1.

The MLS calculates DOM however it wants — its rules, its policy. Nothing changes for MLS business logic.

2.

Along with the current DOM count, the MLS sends when that count was accurate and whether it's still incrementing.

3.

Downstream consumers do simple math: base + days elapsed = current DOM. No nightly re-downloads. No guessing.

The full talk

A 17-minute walkthrough from the RESO Spring 2025 conference covering the problem, a solution you already understand, and the spec.