hi, you may want to have a look at this:
Judging from what I read in your use-case description until we have native ability to control how widget focus is being moved around in an app on demand (e.g. via a dedicated trigger action, which is discussed as a feature already in a different thread: Tulip player cursor to Badge ID field )
I would probably just create 10 different steps in sequence, each with its own barcode scan trigger and an instruction for the operator which field to scan next.
And then a summary step at the end showing all capture input all-together for verification.
If you can setup your device like I did, it should work without the operator needing to touch anything between steps. He can just scan his way through 