Sort your collections. See why. Prove it worked.

Because the built-in sort is one fixed rule with no window you control, no sold-out handling, no per-shopper variation, and — the part that matters — no way to tell whether it earned you anything. QSortby lets you choose the signal and the window, demotes sold-out products automatically, can give each shopper their own order, and A/B-tests the result against your current sort with attributed revenue behind it. Install the Free plan on one collection and compare for yourself.

Most of the feature list is the same on all of them, ours included — automatic sorting, sold-out demotion, rules on sales, margin and stock. Treat that part as a tie. What differs is whether you can check the result. QSortby lets you read and edit the rule itself — the criteria and how much each counts — and names the signal behind every similar-product match; it keeps every configuration change on record with its date, so you can tell which rule was live in any week; shows the last run beside your pixel and catalogue-sync state on the app home; and labels revenue influenced — never caused — with the minimum sample per arm on screen whether or not you have reached it. None of that is a paid tier. Install Free on one collection and look at it.

A real plan. Every install starts with 10 days of full access to every feature, then drops to Free — one managed collection with real-time ranking, sold-out demotion and revenue attribution, running indefinitely at $0 with no card. Paid plans add collections, personalization and analytics; they don't turn the core back on, because it was never off.

There's no single black-box formula. You pick the ranking signal per collection — sales velocity, revenue, margin, conversion rate, trending momentum, selling-fast, repeat-purchase, engagement or newest — and QSortby scores your catalog in real time, keeping in-stock products first. The part that answers "maximum conversion value": you can A/B-test any sort against your current order, and QSortby measures the funnel it drove (clicks → add-to-cart → influenced revenue, via last-touch attribution) and reports statistical significance — so the winning sort is the one the data proves, not a guess.

Eleven live signals: sales velocity, revenue (GMV), margin, conversion rate, trending momentum, selling-fast (velocity vs. remaining stock), repeat-purchase rate, engagement (clicks / CTR / dwell / add-to-cart), review score — read straight from the review app you already run, with nothing to set up — or newest, over a rolling or fixed window you choose. Save any signal-and-window pair as a named preset and point other collections at it. Per-visitor "For You" ranking blends weighted signals per shopper. Or order any collection by hand.

QSortby runs an A/B test between the new sort and your current order, then attributes downstream orders (last-touch) to the feed a shopper interacted with — reporting click-through, add-to-cart and influenced revenue per variant with a significance verdict. You see the lift on your own store, you're not taking it on faith.

Only if you want it to. Every collection has a before/after preview — the exact order the next run would produce, side by side with what's live, as product cards with added, removed and reordered counted. You can switch auto-publish off entirely, so a new order waits for your approval, or keep the collection manual and let QSortby decide only the order of products you picked yourself. Every published order is stored with the configuration behind it, so you can always see what changed and when. Preview, manual order and exclusions are on every plan, including Free.

The app home carries the last run next to the state of your pixel and catalogue sync, so a sort that has stopped shows up there instead of on your storefront. Every published order is stored with its timestamp and the configuration that produced it, so “when did this collection last change, and to what” has an answer you can read rather than infer. Sold-out demotion is the one thing that never waits — a product that hits zero sinks within minutes and climbs back to its earned position on restock.

Two halves, and you can inspect both. On the product side, QSortby drafts a fit tag for each item — comfort, gifting, reassurance, effortless, classic and so on — and you approve or rewrite them; you can open any product and check its tag. On the session side, it reads what this visit is actually doing — pace, dwell, revisits, comparisons, hesitation before the cart — and leans the feed toward the matching tags. You set the signals and their weights yourself, so the rule behind any order is one you can read and edit — never a black box. Pro gets the read as a report while your storefront stays untouched; Growth applies it live per shopper, behind the same A/B test and attribution as everything else. Cost is capped per store: reads are cached per behaviour pattern and there's a daily ceiling, past which the rule-based classifier answers instead — the feed never degrades.

Both, and they run off the same engine — that's the point. The ranking decides which products a shopper meets; the upsell surfaces decide what else goes in the basket. Because the offers are fed by the same live signals, they suggest what's actually selling and actually in stock instead of a static list you have to keep updating. Six surfaces: cart drawer and cart page, a free-shipping progress bar, frequently-bought-together on the product page, a thank-you-page offer, popups with AND/OR rules, and an offer inside checkout itself. The first two are on the Free plan.

No. Suggestions come off a pre-ranked pool rather than a fresh catalog scan, the per-shopper step is a cheap reorder of that pool, and nothing is added to your theme's critical path — the widgets render after the cart, not before it. If a request fails, the section simply doesn't appear; a cart never blocks on an offer.

No code. QSortby maintains standard Shopify collections — add them like any other. One step does happen in the theme editor: flip the QSortby embed on so we can read the behavioral signals that drive ranking and attribution, and drop in a block if you want the personalized or best-seller feeds rendered on a page. Toggles only — nothing to edit.

It drops to the bottom automatically, and returns to its earned spot once restocked.

Yes — because they are rendered by your own theme, not by us. The best-seller and For You blocks can hand Shopify your theme's product-card snippet, so the cards come out with your markup, your CSS and your badges: a QSortby feed is indistinguishable from a native collection grid. Nothing to restyle, and nothing to redo when you change theme. Most apps ship their own card markup, which is why they never quite match.

Yes. Pairing rules group products by vendor, product type, tag or a metafield you choose, and hold the group together when the collection re-sorts — in an order you set inside the group, so the shirt leads, then the trousers, then the shoes. You also choose what happens when one of them sells out: keep the group as it is, hide the missing item, demote it, or split the group. Write the rule once and point any collection at it.

Yes. Every published order is stored together with the configuration that produced it, and orders are attributed back to the feed a shopper actually interacted with. So “what did this collection look like on the 12th, which settings produced that, and what did that version earn” is a question with an answer — not a guess from memory.