It goes wrong on its own
Nothing broke. The catalogue moved and the order did not follow it.
New arrivals “The drop I launched last week is still buried behind last season.”
- Today
- New arrivals have no sales history, so a best-seller sort files them at the bottom on day one and they never climb out.
- With QSortby
- Rank on new and selling: recency weighted against real velocity, so a fresh product rises the moment it starts moving.
newest × velocity Live stock “By Friday half my front row is out of stock.”
- Today
- Shopify's own sort leaves a sold-out product exactly where it was until someone steps in and moves it.
- With QSortby
- In-stock first is the top tie-breaker and cannot be switched off. A product that hits zero sinks within minutes and climbs back on restock.
in-stock first Seasonality “Our best sellers change every month. The collection does not.”
- Today
- A sort you set in spring is still ranking on spring demand in October.
- With QSortby
- Choose the window: a rolling hour for a trend, last month for a season, a fixed range to re-run a campaign.
window picker Too big to do by hand
The work is possible, just not at the size the store has grown to.
Scale “I stopped merchandising when the catalog passed a thousand SKUs.”
- Today
- Dragging works at twenty products. It is a chore at two hundred, and after that it stops being something a person can keep up with.
- With QSortby
- Write the rule once and apply it to as many collections as you want. New products join on their own; you never open the picker again.
bulk apply · app membership Position “Forty products look identical on the grid — position is the only thing deciding the sale.”
- Today
- And that position was set by whoever dragged them last, on a day nobody remembers.
- With QSortby
- Rank on conversion rate or revenue instead of instinct, so the near-identical products that actually close take the front row.
conversion · revenue Per shopper “People browse for ten minutes and leave without buying anything.”
- Today
- One fixed order serves every visitor, whatever they arrived looking for.
- With QSortby
- A feed built from what this visit is doing — pace, dwell, revisits. No login, no purchase history, no quiz.
per-shopper feed You want to stay in charge of it
Automation is only worth having if you can still see, check and undo what it did.
Explainability “Someone asks why a product is where it is, and I have to answer.”
- Today
- Every app in this category will re-order a collection. Almost none will let you read the rule that did it, let alone change it.
- With QSortby
- The criteria and their share of influence are yours, written in plain words and editable. On any product, the Similar tab names the signal behind every match it made.
score breakdown Proof “I changed the order and I have no idea whether I made it worse.”
- Today
- Reorder, then wait a fortnight and read a sales chart that moved for ten other reasons too.
- With QSortby
- Run the new order against your current one as a split test, with attributed revenue and a stated minimum sample. Every configuration change is on record with its date, so you can always see which rule was live when a week went the way it did.
A/B · snapshots · attribution Your theme “The app's product cards don't look like the rest of my store.”
- Today
- You take the app's markup, or you pay a developer to reskin it every time the theme changes.
- With QSortby
- The feed can hand back your theme's own product-card snippet, so app-chosen products render in your theme rather than beside it.
theme card
Three situations we hear often are not on this list — sorting on variant-level stock,
pinning a product to a position, and scheduling a sort for a few days and back.
The app cannot do them yet, so they are not claimed here.