Currently, the DB only tracks the result of the datamatrix, the goal of this is so that if the same code has already been scanned, it will show the info screen instead, and to handle cases where 2 bags have the same datamatrix, it includes an option to override it.
Currently, the DB only tracks the result of the datamatrix, the goal of this is so that if the same code has already been scanned, it will show the info screen instead, and to handle cases where 2 bags have the same datamatrix, it includes an option to override it.