Shopify Collection Sorting for Large Catalogs

Shopify collection sorting with ranking signals, minimum moves and rollback safeguards

Your collection keeps showing yesterday's winners while new arrivals and available alternatives sit further down the page. Before adding a sorting app or commissioning custom work, check which order shoppers actually see and write down the rules that order needs to respect. Keep a built-in option if it does the job; automate when your team needs a repeatable combination of sales, stock and merchandising rules.

Check the order shoppers actually see

Shopify's collection sorting options include Most relevant, Best selling, price, product title, creation date and manual ordering. Most relevant uses sales performance and is the default for new collections. Best selling uses the all-time number of orders containing a product, so it answers a different question from “what is selling recently?”

To change a collection's sort order, go to Products > Collections in the Shopify admin and open the collection. In the Collection items section, choose a different option from the Default sort menu, then click Save. With Manually, you can drag a product to a new position, or select several and move them to the beginning, the end or a numbered position.

Open the affected collection in the admin and record its default sort. Then visit the storefront using the plain collection URL. Shopify's collection template documentation explains that a sort_by URL parameter can select another order. A bookmark with a price sort can therefore show a different order from the default you are reviewing.

If price order looks wrong, compare the product's base price with the price shown to that customer. Shopify documents that price sorting uses base prices, not market or B2B catalog prices. Record the market and customer context before treating the result as an automation fault.

If the order keeps resetting

Before dragging the products back again, record what changed: the default sort setting, the saved product positions, or only the storefront display. Save the collection URL, time and first few product names in both the admin and storefront. Repeat the comparison when the problem returns, using the same market and an unfiltered collection URL.

A proposed worksheet for a collection order that won't stay put
What changed?What to check next
The admin's default sort changed from Manually to another optionAsk who or what last saved the collection settings; compare staff activity and app run records with your timestamp
The setting still says Manually, but saved product positions changedCheck which apps or custom jobs can reorder that collection and whether their run records explain the moves
The admin order stayed the same, but the storefront differsRecord the selected sort and full URL; ask the theme or product-grid provider to trace the order being displayed

Shopify's reorder API, covered below, can change positions while the collection remains on manual sort. “Manually” therefore doesn't prove that only a person can move products. Shopify also advises checking that other staff aren't editing the same collection before making changes.

For a hypothetical campaign gift set that drops overnight, compare the change time with the sorting schedule before assuming the pin failed. Ask the operator to pause the relevant sorting job for a controlled test, accounting for any run already in progress. Keep unrelated stock updates running. Once the cause is established, agree which process owns the order and how a merchandiser's exception becomes a rule that process preserves.

Decide which products deserve the first page

A useful brief describes decisions your team can check. “Optimize the collection” leaves too much room for disagreement. “Keep the campaign product first unless it cannot be bought, then prioritize available products with recent demand” gives you something to review.

For a hypothetical fragrance collection, consider a popular perfume whose main size is unavailable, a new scent with little sales history, and a campaign gift set. Decide whether the gift set stays pinned, which variants make the perfume useful to shoppers, and how the new scent earns exposure. There isn't one right policy for every store.

I built Swift AI Collections around weighted revenue, conversion, margin and stock signals, with rules for pinning, hiding, boosting, burying and limiting consecutive products from one vendor. Those are documented project features; the worksheet below is my proposed way to review a sorting setup for your store.

A collection sorting brief you can fill in before choosing software
DecisionWrite downWhat to ask for in the preview
StockWhich unavailable variants disqualify a product from prime positions?The affected product moves according to that rule
CampaignsWhich products are pinned, and when should the pin end?Pins remain visible and conflicts with stock rules are explained
Recent demandWhich sales window should influence the order?Each score identifies its window and data freshness
New arrivalsHow should products without enough history get exposure?A new product is neither forgotten nor declared a winner without evidence
MarginWhich cost basis is available and trustworthy?Missing costs are flagged instead of treated as excellent margins
VarietyShould one vendor dominate the first row?Any variety rule is visible in the resulting order

Choose the rules that matter to this collection. Adding signals you cannot explain makes the result harder to trust.

Don't mistake placement for demand

In Swift AI Collections, click-through is adjusted for the position where a product appeared before it feeds back into ranking. This addresses a feedback loop: a product gets prominent placement, earns clicks there, and uses those clicks to keep its placement. Raw clicks alone don't separate shopper preference from the opportunity to be seen.

Ask a provider to show the positions behind an engagement score and explain how products with little exposure are handled. If your store lacks that evidence, keep the decision modest: review stock and sales rules first, rather than assuming a click-based score is fair.

Sparse conversion data needs similar care. The project blends a product's conversion rate with the collection average until it has more evidence. This illustrative JavaScript calculation shows the idea; the weight is an example, not a recommended setting for every store.

Shrinking a sparse conversion rate toward the collection average
// k = how many views of evidence before a product's own rate dominates
const k = 50;

function shrunkConversion(orders, views, collectionRate) {
  return (orders + k * collectionRate) / (views + k);
}

shrunkConversion(1, 1, 0.02);      // ≈ 0.039, not 1.0
shrunkConversion(120, 2400, 0.02); // ≈ 0.049, close to its own 0.05

The first product's single order doesn't establish that every future visitor will buy. A review should make that uncertainty visible, not hide it behind a precise score. To compare two proposed strategies, use the collection A/B testing brief to check delivery, define success and decide what inconclusive evidence means.

Move only what needs to change

Large collections need a plan that can finish predictably. Shopify's collectionReorderProducts documentation requires manual sort order, accepts up to 250 moves, and returns a job to poll for completion. Moves apply sequentially, so a destination is interpreted after the earlier moves have taken effect.

For example, imagine an order of products A, B, C, D. To put D first and leave the others in their relative order, only D needs to move. Ask your developer to simulate the complete sequence of moves and compare the result with the approved preview, especially when a change spans multiple batches.

In the Swift AI Collections project, planning around products that could stay in their existing relative order reduced 84,916 moves to 22,299 across 57 real sort runs from a 47,000-product store. API batches fell from 382 to 137. These are measurements of work avoided on those inputs, not evidence of a sales increase or freedom from API limits.

Test the awkward cases before scheduling it

A pleasing preview isn't the whole acceptance test. Check what happens when inputs are stale, another run is still writing, or someone wants to undo the result.

The project snapshots the order before applying a run and allows one writer per collection. It also aborts a run that would move more than 60% of a collection. The documented median was 5.9% across the production runs; that context explains the project's threshold, but your store needs its own review of what counts as an unusual change.

Proposed acceptance checks for collection automation
TestEvidence to keep before approval
Preview without applyingCurrent and proposed order, rule explanations, and no storefront changes
Stale stock or sales inputVisible freshness information and an agreed decision to hold or proceed
A run moves an unusually large shareThe threshold and the review required before a write
Manual and scheduled runs overlapOne completes before the other can write to the same collection
Apply finishesThe actual product order matches the approved preview
Stop and restoreScheduling can be paused and the saved order restored for the agreed test collection

Start the restore test with unchanged collection membership. If products were added or removed since the snapshot, agree how to handle those differences before trying to restore an old order. Restoring positions doesn't reverse unrelated price or inventory changes.

After applying, check a real phone and the customer's sort selector. Use the product-card review checklist to confirm that variant choices, prices and cart actions still make sense as products move.

Start with one collection and a clear decision

Save its current order, complete the brief, and mark the products you would move by hand and why. Compare that proposed order with a built-in sort first. An app is a reasonable next step when it can demonstrate your rules; custom work fits when a specific requirement remains unmet and your team can support the integration.

The Swift AI Collections case study gives you a concrete implementation to compare against. If the problem is customers typing a product name and failing to find it, use the Shopify search diagnostic guide instead; changing collection positions addresses a different shopping task.

If you'd like help reviewing the brief, share the collection and its exceptions through Shopify search and merchandising enquiries, or book a call. That gives us a practical starting point for deciding what your store needs.

Keep reading

Back to the blog