Scan food and compare its ingredients.

Scanning is the quick route into the product page

The Blurrix Scanner is a full-screen camera flow with a barcode mode. Open Scanner from the app, choose barcode scanning when needed, and place the code where the camera can read it. A successful lookup takes you to the product detail page, where the available score, ingredients, nutrition, safety information, history, and other product surfaces can be reviewed according to the product domain and data available. Scanning is useful at a shelf because it starts with the actual package instead of a broad search result.

A barcode identifies a product record, not every detail of the package forever. Blurrix first checks its stored records and can use supported external catalogues if the product is not already known. A result is therefore a starting point for checking the product, not a reason to skip the label. Compare the product name, size, ingredients, and nutrition panel with the item in hand. If a package has changed, the detail page may reflect an earlier record while new information is still being processed.

When the barcode is found, do not stop at the headline score. Open the detail that explains it. Food products can show the score dimensions, ingredients, nutrition, and related analysis. Cosmetics and supplements have domain-specific information. Read any data-quality or analysis-status message as part of the result. An unavailable packaging analysis, for example, means the system did not have sufficient usable record data for that part of the page. It is not a hidden conclusion about the product.

If Blurrix does not find a barcode, that is an honest outcome. The app does not create an ingredient list or a score from the barcode alone. Depending on the route and product, other app flows may help with a new product or a label-based process, but a failed lookup is not proof that the product is unusual, good, or poor. Keep the package information available and use the route that fits what you need to record.

Scanning can also connect to other normal journeys. An authenticated scan can appear in your scan history, where products are grouped by product and can be searched, filtered, sorted, exported, replayed, or removed. In a shopping-list flow, the scanner can return a successful barcode result to the list so the product can be added. These are convenience paths, not background claims that the app knows what you purchased or used.

For a smooth scan, make the barcode readable, avoid glare, and give the camera a moment to focus. If the first attempt fails, move closer or change the angle rather than repeatedly scanning a blurred image. Once the detail page opens, use the time saved by the camera to do the part that matters: check whether the record matches the product and read the information behind the score.

Scanning needs camera permission and a readable code. Glare, a damaged print, a very small barcode, or poor focus can avoid recognition before any product lookup begins. Try changing the angle or distance and keep the code inside the camera view. A successful read still leads to a lookup, so recognition of the digits and a found product are separate steps.

If you return to a product later, the history and detail page can help you locate the recorded result again. Treat that history as a record of scanning activity. It does not show a purchase, consumption, or product preference. The useful sequence is simple: scan the package, confirm the displayed variant, then open the record data behind the available analysis.

The lookup path starts by normalizing the barcode and checking stored food and cosmetic records. If neither local record matches, supported external catalogues can be queried in parallel. A food result follows FoodScore, a beauty result follows BeautySafe, and a supported general-catalogue result is classified before the relevant path runs. No result from those sources produces a not-found response. The scanner does not infer a product label from the barcode digits.

A product page can contain more or less material depending on its domain and recorded record data. A food may show score dimensions and nutrition data. A cosmetic can show INCI-related analysis. A packaging-analysis status may say that there was no usable front image or that the available image lacked enough visible record data. These are explicit limits on the displayed analysis, not silent negative or positive findings.

Scan history is available for authenticated users and groups repeated scans by product. It can help you return to a record, but it remains activity history. Filters, exports, and a replay route organize or reopen that record; none of them confirm that the product in front of you still has the same formulation.