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.
How it works
The MLS calculates DOM however it wants — its rules, its policy. Nothing changes for MLS business logic.
Along with the current DOM count, the MLS sends when that count was accurate and whether it's still incrementing.
Downstream consumers do simple math: base + days elapsed = current DOM. No nightly re-downloads. No guessing.
For MLSs
- Fewer complaints about inaccurate DOM on portals and apps
- Less pressure to increase feed frequency or bandwidth
- Full control over DOM definition and policy — unchanged
For vendors and MLS platforms
- Populate 3 additional fields at publish time — no recomputation after export
- Fully backward compatible — existing
DaysOnMarketremains as-is - No changes to existing DOM logic or calculations
For API consumers
- Accurate DOM without nightly re-syncs
- Less data transfer and storage churn
- Works between updates with minimal logic
The full talk
A 17-minute walkthrough from the RESO Spring 2025 conference covering the problem, a solution you already understand, and the spec.
Read the spec
A small addition to the data model.
A big reduction in stale data.