Search parameters and comparison operators

A normal Search form field requires two behavioral settings: Search parameter identifies the Store value to filter, and Comparison defines how the entered value matches it.

Built-in Search parameters

Parameter	Effect
Location (geocode address)	Converts an entered address to latitude/longitude and establishes the distance origin
Keyword (name/text)	Searches Store name/text through the keyword query
Category	Filters stores by Category IDs
Brand	Filters stores by Brand ID
City	Filters the Store location city
Country (ISO-2)	Filters by two-letter country code such as US or AU
Distance / radius	Applies radius around the active coordinates
Custom field	Appears as meta:<field-key> and filters that Store custom field

— Not mapped — displays the field but sends no Store-filter mapping. This is usually a configuration mistake in a Search form.

Comparison operators

Operator	Use it for
Equals (=)	Exact text/number/date/choice value
Contains (LIKE)	Partial text or a value inside multi-value metadata
Any of (IN)	Any selected value from a set
Greater than or equal (>=)	Minimum number or on/after date
Less than or equal (<=)	Maximum number or on/before date

Correct combinations

• Keyword Text → LIKE allows bak to match Baker Street.
• Rating Number → >= with 4 returns ratings of four or higher.
• Service Checkboxes → LIKE when a stored multi-value field contains selected services.
• Category multi-select → the Category mapping sends selected IDs through the category query; do not replace category IDs with category labels.
• Date → >= for on/after, <= for on/before, or = for the same date.

Distance is special

A Distance/radius field can provide the radius value, but filtering requires an active coordinate origin from a Location search or browser geolocation. Radius without latitude and longitude cannot determine what is “within” the selected distance.

Custom field mapping

Create the custom field first under Store Locator → Custom Fields. Reopen the Search form so meta:<key> appears in Search parameter options. Match the Search field type and comparison to how the custom value is stored; a numeric-looking value stored as arbitrary text may not behave like a true numeric range.