Menu
Feedback
Start here
Tutorials
Developer portal

Known Issues
Support Rules
Troubleshooting

Frequently Asked Questions
Announcements
Known issues
O=OrderByPriceASC (or OrderByPriceDESC) could bring the wrong order
O=OrderByPriceASC (or OrderByPriceDESC) could bring the wrong order
ID: 582861
Backlog
Published on 5/20/2022
Last update on 6/21/2024

Summary

O=OrderByPriceASC (or OrderByPriceDESC) can use the wrong policy to order prices. Also, since the indexed price only has one decimal place, the second decimal place of the price will not be considered.

Additionally, the prices of non-comprehensive sellers are not considered in the sorting. As a result, regionalized stores on the Portal are unable to use the orderByPrice parameter.

Simulation

  • Enter more than one price on the product. Ex: two different list prices on different sellers

  • Put page sorting by price (ex: O=OrderByPriceASC)

  • See that the sorting is not in the order of the prices being displayed or

  • Search for two products with decimal prices. Ex: price 1 = 14.04 and price 2 = 14.01

  • Put page sorting by price (ex: O=OrderByPriceASC)

  • See that the sorting is not in the order of the prices being displayed

Workaround

None on the Portal. However, the account can switch to Inteligente Search.

Contributors
2
Photo of the contributor
Photo of the contributor
+ 2 contributors
Contributors
2
Photo of the contributor
Photo of the contributor
+ 2 contributors
On this page
Still got questions?
Ask the community
Find solutions and share ideas in the VTEX community.
Join our community
Request support from VTEX
For personalized assistance, contact our experts.
Open a support ticket
GithubDeveloper portalCommunityFeedback