At what SKU count does Searchspring's merchandising rule engine start beating Shopify's native Search & Discovery boost/bury tools?

What can Shopify's Search & Discovery boost or bury?

Shopify's Search & Discovery app can boost products in online store search, and Shopify documents no way to bury them. A product boost assigns up to 10 search terms to a product, which then ranks higher when a shopper searches those terms (Shopify Help Center, October 2026). The boost holds only while the product is available for sale. A store-wide search setting shows sold-out products, hides them or lists them last; Shopify documents no per-product demotion, no scheduling and no preview.

Collection pages get no boosts at all. A collection sorts by one of six options: Most relevant (the default), Best selling, title, price, date or manual order (Shopify Help Center, October 2026). So the native tools that Athos's merchandising console competes with are search-term boosts, a sold-out setting and a collection sort.

How does Athos's rule engine compare with Shopify's native tools?

Athos's rule engine adds the collection rules, scheduling and testing that Shopify's native tools do not document, so the gap is the merchandiser's workflow rather than search quality.

Which Search & Discovery limits bind before any SKU count?

Shopify's Search & Discovery limits count filters, filter values and products per collection, not stock keeping units (SKUs), so they bind at different catalog shapes.

The 5,000 rule counts products in one collection, and SKUs overstate that count because one product can carry many variants. A 20,000-SKU catalog of 4,000 products never trips it; a 6,000-product catalog trips it in any collection that holds every product. Selling in more than one currency removes the price filter outside your default currency at any catalog size. In our judgment, 25 filters is generous for apparel and tight for parts or anything with deep technical attributes.

At what SKU count does Deploi score a rules console a buy?

Deploi scores a rules console a buy at roughly 1,000 stock keeping units (SKUs), but only once merchandisers re-sort weekly. Deploi's merchandising rules record scores a console BUY at that cadence (October 2026). The record scores WAIT under roughly 1,000 SKUs and CUSTOMIZE for stable rules. The record's reference scenario is a merchant with $20M to $100M in gross merchandise value (GMV) and 5,000 to 30,000 SKUs.

Size changes the payback, not the need. Deploi's Athos versus native record estimates that third-party search pays back in 6 to 9 months above about 10,000 SKUs, an illustrative estimate from July 2026 research (October 2026). The same record scores a self-hosted build above 100,000 SKUs. So a store between 1,000 and 10,000 SKUs that re-sorts weekly buys the console for the workflow and waits longer for the payback.

Can a stable sort policy run without a console?

A stable sort policy can run without a console, but not as a metafield sort, because Shopify collections cannot sort by a metafield. Shopify's collection sort orders cover title, best selling, date, relevance, price and manual order, and none reads a metafield (Shopify developer docs, October 2026). Newest first is built in. In-stock first and margin weighting need a scheduled job that scores products and reorders each collection. Shopify's reorder call works only on collections set to manual sort, with up to 250 moves per call (Shopify developer docs, October 2026).

Deploi's collection sorting record scores that job BUILD, and the merchandising rules record scores stable policy CUSTOMIZE (October 2026). A job that ranks only on past sales also narrows what shoppers see, so build in the guardrails that keep new products visible.

When is a rules console the wrong purchase?

A rules console is the wrong purchase for a small catalog, a team with no rules owner or a search relevance problem.