The Shopping Page Sort Order feature in Prismic CMS now includes a global “Settings” page type that lets you set a default product sort order for your entire e-commerce site—no code required. You can still override the global default on any individual shopping page when needed.
What’s New
New page type: Settings. Use this page to define a sitewide default product sort order.
Precedence: Any sort configuration applied on an individual page overrides the global default set on the Settings page.
What You’ll Learn
How to create and publish the global Settings page
How to set or change the global default sort order
How to apply page-level overrides
How sort order precedence and inheritance work across your site
Benefits of Custom Page Sort Order
Flexibility: Apply a global default, then override it per page where needed
Consistency: Maintain a cohesive sort experience across the site
User-friendly: Configure everything directly in Prismic CMS
Time-saving: Set once globally, then only fine-tune exceptions
Supported Page Types
These options apply across all shopping page types:
Category pages
Kiosk pages
Brand pages
Strain pages
Subcategory pages
Available Sort Options
Price Low to High
Price High to Low
Brand A to Z
Brand Z to A
THC Low to High
THC High to Low
Classification A to Z
Classification Z to A
More options coming soon
Note: When no sort order is defined, then the default will be price Low to High.
Set a Global Default Sort Order (Settings Page)
Add the Settings page type to your Prismic document library.
On the main repository page, click + Create a new page.
Search for Settings and add the page.
When the page opens, give it a clear name such as “Default - Page Sort Settings.”
In the Sort Products section, select your desired global default sort order.
Save & Publish. Result: All product shopping pages will now use this global sort order unless a page-specific override is configured.
Configure Page-Level Sort Order (Overrides)
Access the page in Prismic CMS that you want to configure.
In the first section titled Page Data, find the Sort Products On The Page dropdown.
Choose your preferred sort option (for example, Price High to Low).
Save or Publish to apply the change. Note: A page-level selection overrides the global default set on the Settings page.
Understanding Sort Order Precedence and Inheritance
Sort order is applied using the following hierarchy:
Custom navigation/URL sort parameters: If your navigation or CTA links include a sort parameter (for example, /collection/flower?sort=brand.keywordAsc), that selection takes precedence over both page-level and global defaults.
Page-specific sort order: If set on a page, it overrides the global default.
Global default sort order (Settings page): Applied everywhere no page-level sort has been defined.
User-selected sort while browsing: Shoppers can change the sort on the frontend; this affects their current view but does not update your CMS settings.
Examples
If the Default-Category-Page page is set to THC High to Low but your Vapes category page is set to Price High to Low, the Vapes page will display products by price descending.
If the global default is Brand A to Z and your Flower page has no specific sort configured, Flower will automatically use Brand A to Z.
If your navigation link to Flower includes ?sort=brand.keywordAsc, Flower uses Brand A to Z regardless of page-level or global settings.
Verifying Sort Order Functionality
Confirm that pages without a page-level setting inherit the global default.
Confirm that pages with a specific sort display products as configured.
Check that custom navigation links with explicit sort parameters override both global and page-level defaults.
Verify that sort preferences behave consistently across site navigation (main menu, footer, side nav) and “See All” CTAs on product carousels.
Best Practices
Always create and publish the global Settings page first to establish a sensible baseline.
Use a clear naming convention for the Settings page (for example, “Default - Page Sort Settings”).
Choose a global default that makes sense for most shoppers (for example, Price Low to High).
Apply page-level overrides only where the business case differs (for example, “THC High to Low” for potency-focused categories).
Review global and page-level settings periodically to ensure they align with current goals.
By setting a global default on the Settings page and using page-level overrides only where necessary, you’ll create a consistent, high-performing shopping experience while minimizing ongoing maintenance.