Happens in the US too, and happens with any scanner that supplies a carriage return after the code.

Don't have any suggestions though.

Thanks both for your replies -
Being a developer myself, it looks as it's just a matter of adding an option that determines when the UPC code should be attempted parsed.

As I can tell from behaviour now, parsing happens for each digit entered, thus for every number you enter with a conventional keyboard, the current value in the textbox is submitted for inspection.

Solving this programatically would be as easy as this:

- add an option named "UPC scanner hits return when reading a code" in options. internally, this could've been named UPCScannerSendsCR

then, on the "OnChange" event of that input box you could have somemthing similar to

public void UPCCode_OnChange( object sender, EventArgs e )
{
  // Disable "hot" code validation when using an UPC scanner, and wait for CR instead
  if( UPCScannerSendsCR )
    return;

  ValiddateUPCCode( );
}


public void UPCCode_OnUpdated( )
{
    if( UPCScannerSendsCR )
    {
        ValiddateUpcCode( );
    }

  // rest as before
}


-- this is simply my suggestion for a fix. My scannner does not seem to be one that I can alter in the sway lostmule described, plus, I am guessing this is a feature that more people would benefit from having. I may just end up buying that scanner, lostmule mine cost $9 hehe