Jen Shanahan Senior Solution Consultant

The total discount buttons at the POS do not currently honor the pricing flags of the items. In the case of our most recent implementation this does not meet the requirements.

The POS end users have the requirement to have a button to offer discounts for Employees, Crew etc. However they don't want this discount to be added on top of already discounted items. It was my understanding that the 'Total Discount' flag on the item would solve for this, however this is not the case. The discount is added on to any other discount applied to the items regardless of this flag.

Suggestion:

• Add a configuration option to the POS setup of these buttons on if it should honor the item setup discount flags or not.
• Alternatively allow the POS discount buttons to apply a set Coupon code so the discount can be tied to that coupon where product validation would be honored.

Detailed Example:

In the current setup:

Item 1234 is sold for $7 because the item was on sale for $10 and the Employee discount button (Total Discount of 30%) was applied at the POS utilizing the Total discount button for employees. (Total Discount on the item is set to NO)

Desired Setup:

Item 1234 is sold for $10 and is not discounted additionally once the employee discount is applied because the Total Discount flag on the item is set to NO.

Current Workaround:

Utilizing coupon codes that cashiers have on a small printout taped to the POS terminal so that the discounts apply as desired. This does not solve for the case where an additional discount may be given at an open %. In this scenario the cashier must remember to remove the discount by line item before applying the blanket open discount % from the POS.

The current discount setups are cumbersome and difficult to use for complex organizations looking to do large scale sales.

There needs to be the ability to combine discount types such as mix and match and quantity discounts.

For example I have a category setup for Hats > $5 Hats and a subset of 100 items under this sub category. I want to provide a sale on a certain set of items that if you buy 4 they are $12, this sale only includes about 80 out of the 100 available hats in this subcategory.

The sale item is setup as Include all Hats in the $5 Hat category and then line by line listed out SKUs for exclusions for the remaining 80 items.

In the current setup I have to set this as a quantity discount, then go to the released products grid and find the list of items that shouldn't be on sale that are under this category, then enter them line by line as an exclusion to the quantity discount grid. This is incredibly time consuming and difficult especially if the user setting these up does not have excel skills to do comparisons.

Once this is applied it works as expected and the 4/$12 hat special works. However it would be better if we could list out just the SKUs we wanted included in this sale. In the current methodology this only works if you buy 4 of the same SKU and not across multiple SKUs.

Suggested change:

Add a radio button or selector of some sort to the quantity discount option to specify if mixing of line items setup is allowed. This will prevent having to setup items as included by category and then excluding the items that should not be included as a part of the sale by simply allowing the end user to add all SKUs that should be included into the sale in the grid.

When a manager goes to close out a shift enters in the tender then later discovers there is a mismatch in what the cashier should have vs. what they have they go and research before closing the shift. Once they determine the issue they need to put notes on the shift as to what details of the issue were that resulted in the mismatch. In order to get to this notes screen they have to redeclare the tender again.

We would like the ability to go back and edit the notes field before closing the shift out without needing to redeclare the tender again.

The ability to communicate important announcements, system updates etc. to end POS users is important. It would be great to add a POS function on the welcome screen for announcements.

These announcements would be readily editable and pushed out system wide. Things like important process changes, communications about system downtime where offline mode will occur, notifications of policy changes etc. Just a small text box about 200-400 characters long would be sufficient.

In many cases shifts will occur without cash. During the shift close process when cash or check is present and additional manager is used to validate cash and check totals.

It would be incredibly useful to display on the Mange Shift screen at the POS what shifts contain cash / check sales so that the additional person can be present as the shift is selected. This prevents the unnecessary step of loading the shift to determine if cash or check is present. No total values should be displayed just a simple check box or some indicator that cash / check were transacted during the shift.

A simple check mark noting if Cash/Check is present for the shift is important in these scenarios to identify when an additional person is needed to validate funds declared at the end of a shift.

With QR codes becoming more commonplace in ticketing, events etc. It would be great if there was a way to configure the POS to parse data from a QR code.

For example a data string may come across with some type of seperator (, | etc.) it would be great if we could program the POS to parse that data.

So if I have a string like this: P|10005614|987654321|692

I could create a parse parameter of 1=P, 2=Item ID, 3=Coupon Code, 4=Customer Record. This would allow a transaction to be processed with a single scan and ring in the Item Type, Item ID, Redeem the Coupon Code and Submit the Customer record.

This would greatly speed up transaction times in scenarios where someone has pre-purchased an entry product ahead of time and has a QR code with all of the relevant data points.

We would like to have info codes have an input type of Alphanumeric so that we could utilize Min/Max value rules to prevent invalid info code entries.

We have scenarios where we sell 'passes' that have a serial number on them. Often times a cashier will scan the UPC into the info code instead of the serial number causing reporting data to be incorrect. If we could set min/max rules based on alphanumeric info codes this would make the info code invalid and prevent incorrect data points.

For example the barcode of an item is: 012100001 the serial number that we ask for in the info code is something like 24AB98765 If we could set a Min Value of 24AB0000000 it would prevent someone from scanning the item barcode into the info code.

It's quite common in a retail environment to allow the sale of an item, but not a return.

We need a method on the product or elsewhere that will allow us to allow sales but no returns.

For example if I sell a promotional item at ALL SALES FINAL I don't want the cashiers to have to remember which items are returnable and which are not. This can be a VERY lengthy list and is impossible to manage without some blocking mechanism.

There are often times where products are only available during certain periods in time.

For example during the Summer season an assortment of summer products are available. During the Winter something different. It's cumbersome to constantly have to set expirations on assortments that are going to be re-used again and again.

We would like to setup Assortment Periods where the expiration is based on a reoccuring timeline instead of static dates. For example I would like to assign a Period called 'Summer' with a static date range (no year) so that from 5/1-8/31 yearly this assortment of products are available. The same for each season etc.