Numerator & Barcode Scanner problem

[JohnS]

Numerator issue - We use prefixes on ticket and order numbers to help differentiate the different departments and cross selling.

Bar Ticket - BT#
Bar Order - BO#
Restaurant Ticket - RT#
Restaurant Order - RO#

On the CSV report the ticket numbers are ok, but the order numbers are missing the prefix.


Barcode Scanner issue - Can scan with menu numerator set to big, and none. When numerator is set to small for a menu that is showing, the first scan does not register, all scans after do. If you change to another menu with a small numerator set - same thing, will not register first scan, but all scans after are fine.

[emre]

-Since store order numbers as numerics we don't apply formatting while generating order numbers. Formatting works with Ticket numbers.
-Thank you for the Barcode scanner issue. It should work fine on next release.

[JohnS]

Is the formatting something that you could add in later? It gives you an ability to track cross selling between departments which can be valuable data.

[emre]

Yes it is... but unlike alphanumeric ticket numbers we store order numbers as numeric data so we can't apply text formatting like we do with ticket numbers.

[JohnS]

Quick fix - I have edited the SQL database and set the Bar Orders to start at 9000000 and the Restaurant Orders to start at 1000000.

When we export the data via CSV, we filter by User then break the Orders up by department.