Building a Price Range Filter for Ditto with andFilter

Filtering a Ditto catalog by price range is a classic Evolution CMS task. It also exposes the limits of plain TV matching, because a price filter is not about equality. It is about numeric comparison.

The source question pointed to using the andFilter extender with TV-based product data. That is a workable direction as long as the price TV is stored consistently and treated as numeric data.

What matters most

• The price TV should contain clean numeric values without currency text.
• The filter should normalize the “from” and “to” inputs before building the query.
• Missing boundaries should degrade gracefully, for example “from only” or “to only”.

A practical strategy

Use one layer to validate the request values, then pass a composed filter into Ditto or its extender. Keep formatting separate from filtering: prices should be compared as numbers and only formatted for display afterward.

Common mistake

Do not store values such as 1 200 руб. directly in the price TV if that same field is meant to be filtered numerically. Human formatting belongs in output, not in storage.

For older Evo shops this pattern is still valid: a clean numeric TV plus an explicit range filter will always be more dependable than trying to parse decorative price strings inside the query logic.