Algolia catalog search: exclude unavailable items before breaking ties

Use a three-record toy catalog to check that popularity cannot override eligibility.

Source: www.algolia.com
August 26, 2026
2 min

An unavailable item must stay out; a popular item should rank higher only when relevance ties. Algolia documents a sequence of tiebreaking relevance criteria, with business weights available through custom ranking late in the default order. Don't use a lower score as a substitute for a hard availability rule.

Article img
L-03 has a score of 9 but is filtered out; L-01 and L-02 rank first and second.

Figure 1. Original expected-results diagram, not a test run. The score orders eligible tied records only.

Run the same fixtures against your current search

Build a toy equipment catalog. L-01 and L-02 are available portable lamps, identical in searchable attributes, with popularity scores of 5 and 2. L-03 is unavailable and scores 9. Search for “portable lamp” with availability required: expect L-01 then L-02. Filter to a category with no eligible item: expect an explained empty state, not a silent relaxation. Add an available item with a clearly weaker text match and a high score to check that business preference doesn't overtake earlier relevance criteria.

Run the same checks against built-in search. Require all three passes before comparing configuration and maintenance, including who refreshes availability and who explains order changes. If built-in search passes reliably, don't migrate yet. If filtering passes but the tie order isn't explainable, use Algolia's ranking inspection to identify the deciding criterion. Use no real catalog, logs or credentials for this exercise.

Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.

Original source:www.algolia.com