Keep your scanned products within reach

History is a record of scans, not a shopping diary

A scan is most useful when you can return to it without searching for the same package all over again. Blurrix keeps an authenticated user's scan history and groups entries by product key, so repeated scans of the same product do not need to fill the screen as separate copies. A history row can show the product name, brand, barcode, image when available, domain, source, score, score level, first scanned date, last scanned date, and a count of your scans for that product. This turns a set of past lookups into a practical route back to a product detail.

Open History when you remember the product but not enough of its name to search reliably, when you want to revisit a detail page, or when you want to notice that you have scanned the same product more than once. The page supports pagination and can be searched across product name, brand, and barcode. You can filter by supported domain, choose a score range or date range, and sort by scan date, score, or product name. These controls are intended to help you find a record, not to turn your history into a scorecard for your choices.

The history view also provides maintenance controls. You can export the scan history as CSV, delete an individual entry, or remove all scan entries for a product barcode. A rescan or replay route can take you back through the product flow when you want to check the record again. Use deletion when you no longer want a lookup in your history; it does not rewrite product information for other people or prove that the product is no longer sold.

Treat the dates as dates of your scanning activity. They indicate when Blurrix recorded a lookup, not when you bought, opened, consumed, finished, or repurchased a product. A scan count likewise means the product was scanned multiple times. It does not establish how much you used or whether you liked it. This distinction keeps the history honest and makes it easier to use as a reference rather than a reconstructed diary.

History can be especially handy after a barcode scan on the move. Scan at a shop, inspect the detail later, then return to the item if you decide to compare it with another product. If an item is relevant to a shopping-list journey, the scanner may also return it to that list. These flows help you carry product information forward while leaving the actual purchase decision with you.

Remember that a saved scan remains linked to the product data available at the time you revisit it. A product can be reformulated, its page can be updated, or a barcode can later show a product-change signal. When you return to an old scan for a new purchase, check the current package. History saves you the lookup effort; it does not make an older label current.

History belongs to the signed-in account that created the scans. Grouping keeps repeated reads of one product practical, while first and last scan dates preserve the timing of that activity. Filters and sorting change what you see; they do not change the underlying product record or recalculate its score. An exported CSV is likewise a copy of the history data available to the account, not a manufacturer catalogue.

A replay or rescan is useful when the product page has changed or when you want to inspect it again. It does not guarantee that a barcode lookup will now return different data. If an item no longer belongs in your record, remove the single entry or the scans for its barcode. That action manages your history rather than deleting the product from Blurrix for everyone else.