Everything merchants ask us about Dynasort, organized by topic and linked to the documentation when you want to go deeper. Not here? The in-app chat is answered by the team that built the product.
What Dynasort is, what install involves, and what happens in the first hours.
Dynasort is a Shopify app that automates merchandising across four storefront surfaces: collection sorting, product option and swatch sorting, search re-ranking, and product recommendations. You define the ranking logic with recipes, weighted combinations of more than 40 attributes such as sales, inventory, margin and review ratings, and Dynasort keeps every surface ordered by that logic automatically. Full overview: How Dynasort Works.
Every product is scored by a recipe: a set of attributes you choose, each with a weight. Dynasort tallies each product's total score, ranks the collection, search results or recommendation row by it, and refreshes the ranking automatically as your store's data changes.
Most stores see their first re-sorted collection within minutes. Setup is three steps: pick a collection, enable it and choose a recipe, then turn processing on. See the Quick Start Guide. A free live training session with the team is included on every plan if you want a guide.
Not for collection or product option sorting: both happen entirely through Shopify's APIs, so nothing is added to your theme and nothing breaks if you switch themes. Search re-ranking and recommendations render on your storefront, so each is added once in the theme editor as a standard app block or app embed. After that one-time step, everything is controlled from inside the app.
No. Collection and option sorting add zero code to your storefront: the order is written through Shopify's APIs, so there is no storefront script latency at all. The search and recommendations blocks are small, self-contained, and avoid render-blocking scripts.
Sorting starts immediately. The moment you enable a collection, Dynasort orders it using catalog signals it already knows: stock status, price, inventory, tags, sales and more. Shopper-behavior analytics appear after the first overnight processing run (around 1:00 AM US Eastern), and behavior-based attributes get richer as traffic accumulates. Details: What to Expect After Install.
Yes. Collection and option sorting are theme-independent. The search and recommendations blocks work with any Online Store 2.0 theme, and the live search embed has per-theme selector settings documented in Live Search theme selectors.
Yes. Dynasort never edits your theme code. Every sorted collection has a Revert To sort order you choose (best selling, manual, newest and so on): disable the collection and it reverts to that order. Uninstalling removes the app and its storefront blocks entirely.
Yes. Dynasort has earned Built for Shopify status, the App Store's highest quality bar for performance, ease of use and merchant experience. More on what that means: Why Dynasort.
Recipes, attributes, boost, pinning and how the core sorting engine behaves.
Dynasort syncs your collection data from Shopify, scores every product with the recipe you assigned, applies any boosts and pins, and pushes the optimized order back to Shopify. The cycle repeats automatically on your plan's schedule. Full walkthrough: Collection Sorting.
A recipe is your ranking logic: a set of attributes with weights, for example Best Sellers 30 points, Price over $100 20 points, New Arrivals 10 points. One recipe can drive many collections, so a single edit updates all of them. Recipes also control sold-out handling, tie breakers and boost usage. See Recipes.
More than 40 signals: sales, revenue, conversion rate, add-to-cart rate, product views, most-clicked, inventory quantity, location-specific inventory, variants and sizes in stock, full size runs, back in stock, price, compare-at price, margin, cost, on-sale status, product age, tags, vendor, product type, SKU, title, metafields, and review ratings from nine review platforms. Full reference: Attributes.
Collections re-sort as often as every 10 minutes on Enterprise, every 20 minutes on Pro and every 30 minutes on Basic. Search results and recommendations do not wait for that cycle: they are ranked live on every request.
Yes, with pinning. Pinning locks a product to a fixed position in one collection while everything else keeps sorting dynamically around it. Use it to preserve hand-picked placements alongside automation. See Product Pinning.
Yes, with boost. Boost adds ranking points to a product across all collections at once, useful for high-margin, seasonal or flagship products. Pinning is per-collection, boost is storewide. See Boost.
You decide, per recipe. Collection recipes can push sold-out products to the bottom automatically, search recipes can hide them from results entirely, and option sorting can send sold-out variants to the end of the swatch row. Hiding sold-out items in search is usually the single biggest search conversion win.
Sorted collections are collections you already have: Dynasort takes over the order only. Managed collections go further: Dynasort also decides which products belong in the collection, based on conditions you set, and then ranks them.
Only on collections you enable, and only the sort order. If you have placements you want to keep, pin those products and let everything else sort dynamically. Disable a collection and it returns to the Revert To sort order you chose.
Yes. The Metafields attribute lets recipes and managed collections read your product metafields, so custom data like a season code, a priority flag or a supplier field can drive ranking and inclusion.
Yes. Enable Push Rank to Metafields on a recipe and Dynasort publishes each product's rank position, score and percentile as Shopify metafields, refreshed hourly. Themes can render "Top 10" badges from it, and Flow, reports and other apps can read it.
Yes. The Location Quantity attribute scores products by inventory at specific locations, so a store fulfilling from one warehouse can rank by what that warehouse actually has.
Nine platforms: Yotpo, Okendo, Loox, Judge.me, Junip, Stamped.io, Trust Reviews, Helpful Crowd and Debutify. Review ratings become a weighted attribute like any other, so well-reviewed products can rise across collections, search and recommendations. See Attributes.
Collections where Dynasort picks the members, not just the order.
Collections whose membership Dynasort maintains for you. You define conditions (for example: sell-through above 20 percent, price over $50, tagged "summer"), choose match-all or match-any logic, optionally cap the collection at the top N products, and optionally rank the result with a recipe. As product data changes, products enter and leave automatically. See Managed Collections.
Shopify's automated collections match on static catalog fields like title, tag and price. Managed collections can also use performance data: sales velocity, conversion rate, review ratings, full size runs, back-in-stock status and more. They can cap membership at the top N performers and prune products that no longer qualify, which Shopify's automated collections cannot do.
Yes: add a match-any condition that targets it, for example a Title or Product Tag condition. Note that products added by hand in the Shopify admin are removed on the next update, because the conditions own the membership. An explicit condition is the reliable way to include a product.
Yes. Set a top-N cap and Dynasort keeps only the N best-scoring qualifying products, so a "Best Sellers" collection stays a tight, high-converting page instead of growing without bound.
Sorting the options inside a product: colors, sizes and any other variant option.
It reorders the option values within a product, for example the color swatches on a product card or product page, so the best-performing variant shows first. The first swatch a shopper sees is the one most likely to convert, instead of whatever was entered first.
Units sold, revenue, price, compare-at price, cost, margin, discount amount or percentage, inventory, in-stock status, variant age, numeric value, alphabetical order, a custom comma-separated order you define, or standard size runs. Sales-based sorts have selectable time windows from 7 days to all time.
No. The common-sizes sort keeps standard size runs in their natural order (S, M, L, XL and equivalents for apparel and shoe systems), and the numeric sort handles numbered sizes. You choose per option, so Color can sort by sales while Size stays in size-run order.
Your recipe decides the order of search results; Shopify still decides what matches.
It applies your recipe to storefront search results. Shopify still decides which products match a query, including typo tolerance and synonyms; your recipe decides the order they appear in, so best sellers, high-margin or in-stock products rise to the top. See Search Re-ranking.
No. Matching stays entirely with Shopify: a query matches exactly the same set of products it always did. Shoppers never see products that do not fit their query and never lose results they would have found before. Only the order changes.
Because shoppers click far past the top. In one large catalog we analyzed, nearly half of 188,000 search result clicks landed past the third position. What sits in those positions is either whatever default relevance surfaced, or products you chose to put there.
Four steps: create a search recipe, preview the re-ranking against real queries in the editor, activate the recipe on the Search page, then add the Dynasort Search Results app block to your search template and enable the Dynasort Live Search app embed. After that, ranking changes never touch the theme again. Walkthrough: Search Re-ranking.
Search recipes default to Shopify relevance as the tie-breaker. With no data at all your results look exactly like Shopify's, and as data accumulates the recipe takes over gradually. No cliff, no scrambled results on day one.
Yes. The suggestions that appear as a shopper types are re-ranked by the same active recipe as the results page. The dropdown uses a compact thumbnail, title and price layout designed for fast scanning. Theme-specific setup notes: Live Search theme selectors.
Yes, twice over. The Search page controls columns per device, results per page, swatches, badges, star ratings and quick add-to-cart. For deeper changes, the storefront pieces ship without !important rules and expose CSS custom properties, so your theme's CSS can override anything.
Dynasort records every results page it serves and tracks serves, clicks with position, click-through rate, add-to-carts and checkouts on the recipe's page. Attribution is deliberately conservative: a click only counts on a result Dynasort actually served, and a checkout only counts when a served product was added to the cart first.
Recipe-ranked product rows on product, cart, home, thank you and order status pages.
Recipe-ranked product rows you can place anywhere on your storefront: "You may also like" on product pages, "Complete your order" in the cart, "Recommended for you" on the home page. Each placement is bound to a recommendation recipe you can read, edit and measure. See Product Recommendations.
Product pages, the cart, collection pages, the home page, custom placements you define, and after checkout on the Thank you and Order status pages via post-purchase recommendations.
No, and that is the point. Each placement is driven by a recommendation recipe whose logic you can open, read and change. If you want the cart row to favor high-margin accessories, you set that, and the preview shows exactly what will serve before anything goes live.
Never. Cart recommendations consider everything in the cart and exclude it. Product page rows are seeded by the product being viewed, and post-purchase rows are seeded by the order while never recommending its own items back.
A recipe-ranked "Complete Your Order" row on the order confirmation (Thank you) page and the Order status page, seeded by what the customer just bought. Those pages are rendered by Shopify's checkout, so the cards automatically follow your checkout's styling. See Post-purchase Recommendations.
Yes, per placement: grid or carousel, cards per row per device, badges with custom colors and translatable labels, swatches, star ratings, quick add-to-cart, image aspect ratio and hover behavior, sold-out handling, a per-brand cap for multi-vendor catalogs, and a minimum count below which the row hides itself rather than look sparse.
Measuring what the sorting actually does, and testing strategies head to head.
Conversion rate, add-to-cart rate, exit rate, bounce rate, views and sessions, broken down per collection, per recipe and storewide, with automated daily, weekly or monthly email reports. Analytics are included on every plan. See Insights.
A chart of your key metrics over time, per collection, per recipe or storewide, with event markers overlaid: sorting enabled, recipe changed, A/B test started, pins or boosts updated, manual re-sorts. It answers "did that change actually help?" by showing the trend before and after each marker.
You test two sorting strategies on the same collection: Dynasort versus your store's default order, or Recipe A versus Recipe B. Dynasort alternates the whole collection between variants on a fixed schedule (1 hour to 1 week per window) and compares conversion, cart, exit and bounce rates. See A/B Testing.
Per-visitor splits need cookies, audience segmentation and two simultaneous orderings, which conflicts with Shopify's edge caching and can show one shopper different orders on different devices. Alternation gives every shopper a consistent view, measures both variants under the same traffic mix, and removes a whole class of caching bugs.
Dynasort runs a two-proportion z-test and marks a difference significant when p is below 0.05, the same approach used by major testing tools. Results are suppressed until each variant has at least 100 sessions, because below that even large-looking lifts are routinely noise. Do not end tests early because one side looks ahead.
No, by design. The statistical result is one input; margin, inventory and brand considerations are yours. When you end a test the results stay available indefinitely, and you decide which variant to run.
Pro and Enterprise. Analytics and the performance timeline are included on every plan.
Flat monthly fees, a 30-day trial on every plan, no usage charges.
Three flat monthly plans: Basic $99, Pro $249 and Enterprise $499, each with a 30-day free trial, billed through Shopify. Every plan includes all four surfaces: collections, product options, search and recommendations. Details: Pricing.
Full access to your plan for 30 days, billed through Shopify only after the trial ends. Uninstall any time before that and you pay nothing.
Capacity and speed, never which features you get. Plans differ in how many collections you can sort, how often they re-sort (every 10, 20 or 30 minutes), monthly serving allowances for search and recommendations, and analytics depth. All four surfaces are on every plan.
Yes, upgrading is one click in the app and takes effect immediately. If your catalog is unusual, talk to us: large-catalog setups are our favorite kind.
Yes. Stores on the retired Free plan keep it for as long as the app stays installed, that promise stands. Uninstalling ends the grandfathered plan; a later reinstall starts on the current plans with a full 30-day trial.
Uninstall the app from your Shopify admin at any time. Billing runs through Shopify and stops with your Shopify billing cycle; there are no cancellation steps on our side and nothing to email us about, though we read every goodbye note.
Programmatic control, AI assistants, and reading Dynasort data elsewhere.
Yes, the Connector: a REST-style API with 16 actions covering collections, recipes, products, boosts and option sorting. It authenticates with a bearer key you generate in the app and is available on Pro and Enterprise plans. Reference: Connector (API Access).
Yes. The Connector page includes a ready-made system prompt containing your store URL, the endpoint and the full action reference. Paste it into your assistant, provide your API key, and ask it to list collections, enable sorting or boost a product in plain language.
Sixty requests per minute per store, with standard rate-limit headers on every response. One API key is active at a time; keys do not expire and can be revoked instantly, and revoked keys stay visible as an audit trail.
When something looks off, and how to reach an actual human.
Three things, in order: that Processing is On in Settings (it is the master switch for the whole store), that the collection itself is enabled with a recipe assigned, and that your plan's re-sort interval has elapsed. If all three check out and the order still looks stale, message us in the in-app chat and we will dig in.
Usually one of three reasons: it no longer meets the collection's conditions, it fell outside a top-N cap, or sold-out handling moved it. Check the conditions first. To guarantee a product's inclusion, add a match-any Title or Tag condition for it; hand-adding it in the Shopify admin will not stick.
Yes. Collection Issues monitoring flags low product counts, sold-out products above the fold and broken size runs above the fold, with thresholds you control and optional daily, weekly or monthly email alerts.
Catalog data from Shopify's APIs, and storefront interaction events (product views, add-to-carts, orders) that power the behavior attributes and analytics. Data is used to sort and measure your own store, not sold or shared. Full details: Privacy Policy.
In-app live chat is answered by the people who built the product, and merchants mention it in most of our reviews. You can also book a free training session, browse the documentation, or email hello@dynasort.io.
No questions match that search. Try a different word, or search the docs.