{"section":"known-issues","requestedLocale":"en","requestedSlug":"manual-sorting-of-collections-doesnt-work-as-expected","locale":"en","slug":"manual-sorting-of-collections-doesnt-work-as-expected","path":"docs/en/known-issues/Portal/manual-sorting-of-collections-doesnt-work-as-expected.md","branch":"main","content":"## Summary\n\n\n\nManual sorting of collections doesn't work as expected. There are two ways to sort SKUs using a collection:\n\n\n1. Using the ContentPlaceHolder control type collection;\n2. Using a search or search context of a Landing Page with the SearchResult control (in this case, the querystring _O=productClusterOrder_\\{ProductClusterId\\}%20asc_ must be used).\n\nIn both cases, the system supports sorting up to **30** SKUs of the collection. When the collection has more than 30 SKUs, all spare SKUs will be listed BEFORE those positioned between 1 and 30.\n\n\n> This behavior is observed in all VTEX stores, including those developed using VTEX IO.\n\n\n\n#### Simulation\n\n\n\n\n1. Create a collection;\n2. Manually insert more than 30 SKUs;\n3. Save the collection;\n4. Create a template with ContentPlaceHolder or SearchResult;\n5. Set up the association of the ContentPlaceHolder with the collection or set the search in the folder search context;\n6. Wait a few minutes for the cache to expire;\n7. Access the page and note that the first ordered items will be items placed after 30.\n\n\n#### Workaround\n\n\n\nAs a workaround, we have the following options:\n\n\n- Use collections with only 30 items, if it's essential to apply manual sorting;\n- Use the Release Date field, register the dates in the desired sequence, and use the field to sort the collection."}