I’m going to start off by saying that we want to make the operator’s life as easy as possible to collect the best / most data. The age old saying still holds true; “good data in, good data out”. As soon as the task becomes too hard for the operator or they are provided with too many options, the data starts to deteriorate, and we want to keep the data as “clean” as possible. For example, if you expect each operator to enter a description you can bet they will all be different. But if the description is provided as a read only field for them to validate the item they are cubing, the data will remain “clean”. Taking time to enter a description also decreases the system’s throughput.
There are up to 21 customisable fields (other than Product ID, UOM, length, width, height and weight) which can also be recorded, saved and managed. Due to the vast requirements of all our customers, these fields serve as descriptions fields only and have no process logic behind them – this customer wants Nestability but that customer wants Security Risk. But you want the units in millimetres instead of centimetres, easy. You want a dropdown of your UOMs, no worries. You want the Product ID to be searchable, done!
Really, CubeMaster is your oyster (wait, that doesn’t sound right but you get what I mean). Take a moment to think about what features you would like to capture and have a chat to us, and we can help either making it work or finding another suitable outcome.