Skip to main content

The Itemize function at time of receiving is slowing down our process considerably, but we need to use it. Does anyone have suggestions on how to populate the serial lines efficiently? We run into the issues below:

  1. We can use the scanner to populate the itemize lines, however, some screens require an “arrow down” set up on the scanners, some require “enter”. Is there a way to stick with one so we are not having to reprogram scanners each time we need to itemize a receipt?
  2. We often have the serials in a spreadsheet, but can only copy/paste one at a time. Is there a way to copy/paste a column? Or multiples in another way?
  3. We have tried to set up an import template for this which somewhat works, but does not update the status of the serials in the same way.

We are using Alliance 15.2. Any suggestions would be appreciated, thanks!

Hi,

Have you considered using ‘Serialize at Usage’  from the Product Centre Serialization option?

This way you’ll avoid moving tons of serial# in the warehouse.

You allocate the serial number at usage only.


Hi @Joshua Liem , 

We do use Serialize at Usage for some of our customers, but some require asset tracking in and out so it is not an option in this case.


  1. We can use the scanner to populate the itemize lines, however, some screens require an “arrow down” set up on the scanners, some require “enter”. Is there a way to stick with one so we are not having to reprogram scanners each time we need to itemize a receipt?
  2. We often have the serials in a spreadsheet, but can only copy/paste one at a time. Is there a way to copy/paste a column? Or multiples in another way?
  3. We have tried to set up an import template for this which somewhat works, but does not update the status of the serials in the same way.

We are using Alliance 15.2. Any suggestions would be appreciated, thanks!

Hi Leann,

Regarding question one, can you please document the screen discrepancies regarding where “arrow down” works vs. “enter” and log a support ticket?  If you need to use different keystrokes in similar screens, this sounds like a usability/consistency issue that should be addressed.

For questions two and three, I was going to also suggest an import template to address the issue with entering multiple serials; however, you mentioned that the items are not updated the way that you’d like.  Can you please document the issue that you are having as well and log a support ticket so that we can review if there is a bug that is causing this issue?

Thank you,

Andrew 


Reply