Skip to main content

Lot and recall check

Before a product, a spare part, a medicine or a chemical is used, someone scans it. Red, with a large "do not use" and the reason, stops something recalled or expired from going any further.

How it works#

  1. Your API keeps the current list of blocked products, lots or serial numbers.
  2. The worker scans the code on the pack before using it.
  3. Your API answers green if it isn't blocked, and red with the reason if it is.

What your API checks#

  • The code is on the recall or blocked list.
  • Optionally, the expiry date, if it is part of the code (GS1 Data Matrix codes often carry the lot and expiry).

Example answers#

{ "status": "ok", "title": "OK to use", "message": "Not on the recall list (updated today 06:00)" }
{ "status": "failed", "title": "DO NOT USE", "message": "Lot 23B41 recalled on 2 Sep · put it in the red box" }

Settings#

A different sound for failure makes a red result hard to miss on a noisy floor.

{  "app": "scan2check.com",  "settings": {    "apiUrl": "https://api.example.com/recall/check",    "symbols": [      "datamatrix",      "ean13",      "code128"    ],    "soundFailed": "doubleBeep1"  }}

Open in configurator — loads these settings so you can put in your own API URL and generate the QR code.

Watch out for#

  • Green only means "not on the list". It is only as good as the list. Show when the list was last updated in the green message.
  • A product code isn't a lot. A recall usually affects one lot, but a plain EAN names only the product. If the lot isn't in the code, your API can only warn about the whole product.