> ## Documentation Index
> Fetch the complete documentation index at: https://docs.uselayers.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Find duplicate sort orders in the dashboard

> Layers flags sort orders that share the same setup or produce the same ranked results, so you can prune redundant configurations and keep the storefront list tidy.

Layers checks your published sort orders for two kinds of overlap and calls them out in the dashboard so you can consolidate before they clutter the storefront picker.

## What gets flagged

Two flavors of duplicate are surfaced separately:

* **Same setup** — Two sort orders compile to the same ranking configuration once weights, direction, and order are normalized. This is a strong signal that one of the two can be deleted or renamed.
* **Returns same first N** — Two sort orders are configured differently but produce the same top ranked products against your live catalog. This catches setups that look distinct on paper but converge to the same output.

When a pair matches on both, only **Same setup** is shown — the setup match is the more actionable finding.

<Note>
  Sort orders that depend on per-request context — user affinity, geo distance, or [conditional expressions](/platform/sorting/conditional-expressions) — are excluded from the results-based check because their output changes per shopper.
</Note>

## Where it appears

### Sort orders list

A badge appears under the storefront status on any published sort order that has a twin:

* **Same setup as \<name>** — neutral badge, links to the other sort order.
* **Returns same first 50 as \<name>** — warning badge, links to the other sort order.

Only one sort order in each pair is flagged. Layers keeps the canonical member — the system default or the one with the lowest display order — unflagged so your primary configuration stays clean.

### Sort order editor

Opening a flagged sort order shows an alert at the top of the editor with a link to its twin, so you can compare setups side by side before deciding which to keep.

## When to act on a flag

* **Same setup** — Almost always safe to delete or unpublish the duplicate. If both are intentional (for example, one is used only by a [recommendation block](/platform/blocks) and one drives the storefront), rename them so the difference is obvious to the team.
* **Returns same first N** — Worth a closer look. The two sorts might legitimately agree on today's catalog but diverge as inventory or metrics shift. Preview each one on a few collections before deleting.

## How the check runs

* Setup-based matches recompile on every save, so a badge appears (or clears) as soon as you change an expression.
* Results-based matches refresh nightly, and also on save for the sort order you just edited. The editor alert shows how long ago the check ran.

## Next steps

* [Preview a sort order](/help/sort-orders/preview-sort-order) to compare ranked output between two candidates.
* [Bulk actions](/help/sort-orders/bulk-actions) to unpublish or delete flagged duplicates in one pass.