Menu
Feedback
Start here

Known issues

Known issues
Price filter applied on top of 'spot price' instead of regular price
Intelligent Search
ID: 982664
Backlog
Published on2/15/2024
Last updated on2/15/2024
1 min read

Summary

Price filters are applied on top of the "spotPrice" value, which is the price for special payment conditions, instead of the item's regular price.

This may affect expectations while diverging from most places, which focus on the regular price, as the shelves and cart usually do, or properties like "priceRange" from the API.

Simulation

Consider a product priced at $430 with 10% off in a specific payment method, generating a "spot price" of $387.

Filtering by items with a price between $300 to $400 will return this product, which usually will be shown on the shelf as $430 (its regular price), generating the perception of divergence.

In the same way, the "priceRange" property from the API will answer with the following values (considering this product as the single result for this search query), feeding the sense of divergence:

"priceRange": { "sellingPrice": { "highPrice": 430, "lowPrice": 430 }, "listPrice": { "highPrice": 430, "lowPrice": 430 }}

Workaround

N/A

Contributors
1
Photo of the contributor
+ 1 contributors
Was this helpful?
Yes
No
Suggest Edits (GitHub)
Contributors
1
Photo of the contributor
+ 1 contributors
On this page
Still got questions?
Ask the community
Find solutions and share ideas in the VTEX Community
Join our community
Request VTEX support
For personalized assistance, contact our experts
Open a support ticket
GitHubDeveloper PortalCommunityFeedback