Put the alternatives next to each other

Use comparison when the choice is real

Product Compare is built for the moment when a shelf, search result, or saved shortlist leaves you with a few genuine alternatives. Add two to five products and Blurrix requests a server-built comparison. The response presents normalized product cards and can include the product name, domain, image, score, score label, category, scan count, and available supplement value information. It also identifies the highest scored comparable product, then lists localized guidance and per-product advantages and disadvantages.

Start with products that answer the same shopping question. A comparison is clearest when the alternatives are close enough that their differences matter. Scan products from their packages, search for exact items, or bring them from a relevant product surface. Before trusting the result, check that each card represents the intended variant. Similar names, new pack sizes, flavours, and regional formulations can make two records look more alike than the products really are.

Read the total score as an overview, then move to the stated differences. The comparison leader is the highest scored comparable record in the current group. It is not an instruction to buy that product, a statement about personal suitability, or a claim that it wins every criterion. One product may fit a particular recipe, budget, format, or availability constraint better. The point of the comparison screen is to make those trade-offs visible enough to consider deliberately.

Supplement comparisons can add a Supplement Value Lens when relevant data is available. This view compares price per serving, price per declared active gram, and, for qualifying extracts, price per standardized active gram. It helps you read a price structure without reducing the decision to the largest or smallest figure. Check the package's declared serving and the price context, because both can change.

The comparison route has tier access and quota behavior. Blurrix only consumes a Product Compare quota after at least two products are found, so a failed load does not use a comparison. If your current tier has a finite allowance, the screen can show the remaining comparison quota. This makes the limit legible while keeping an unsuccessful lookup from feeling like a lost attempt.

A comparison remains tied to the product records available at that time. Open a detail page when a difference needs more context, and return to the current label if it conflicts with the record. When you finish, you do not need to treat the highest number as a winner's medal. Choose the product whose documented trade-offs make sense for the purchase you are making.

The request accepts identifiers for two to five products. Each identifier can use a product ID or barcode, and the server can probe supported product storage when a domain is not supplied. A comparison only becomes meaningful once at least two records are found. That rule also avoids an incomplete request from being presented as a verdict on a single item.

Fields vary by domain and by the information stored for each product. A food card may offer different record data from a cosmetic card; supplement value figures require price, serving, and active-amount data. Where those inputs are absent or unsuitable for direct comparison, read the gap as a gap. The app does not convert missing price or standardized-extract information into a false value.

The comparison endpoint applies feature access and tier-specific quota rules. A useful comparison consumes its product-compare quota only after at least two products are found, so a failed lookup or one surviving record does not use a comparison. The result can show the remaining quota where the tier has a finite limit. Access rules decide whether the feature is available; they do not affect the scoring formula or turn a card into a recommendation.

Use the screen after you have identified the actual alternatives. Verify the variant first, read the reported differences, and then inspect the product pages for the inputs behind a score. The winner label changes with the set of records in the request. It cannot account for unrecorded price changes, stock, taste, packaging condition, or the purpose you have in mind for the product.