Why is it coming up with the wrong price?
This is a fairly common question that end-users come up with that relates to items not coming-up in point of sale with the right price.
The most common reasons for this are:
- Incorrect Item Price-1 values.
- Incorrectly set-up or conflicting price rules.
- Improperly assigned customer categories (when Customer Category specific pricing is used).
- Improperly assigned Item Categories/Sub-Categories (when Customer Category specific pricing is used).
- Improperly applied Item based pricing updates.
While the above items are primarily just set-up and configuration issues, sometimes this kind of issue can also be combined with end user usage and training issues. Here’s a recent example of this perfect storm:
For an extended period of time users would ring up certain items by scanning the bar-code, or manually selecting it from a look-up window. Often as this was being done, the quantity was always correct, but with some items, the price was always way too high. Without further investigation, users would just do a price override and correct the selling price. This process went on for many, many months.
Finally someone in the organization decided to launch an investigation into why it was happening. The following was found:
Item set-up was inconsistent for a number of their items that were at issue.
- In most of these cases, the item had a stocking Unit of “EACH”, with an Alternate-1 unit of “CASE”, and the “Preferred Unit” set as “CASE”. However, many of these items were not configured to "Prompt for unit" at point of sale, so the "CASE" unit was automatically being selected, by default.
- Users, thinking that the price was incorrect, without addressing the unit issue, were just doing a Price Override on the line and changing the “BOX” price to the "EACH" unit price.
So the end result here was…
- Cases of the items were being sold at the "EACH" price. This is not only screwed-up their margins,but the inventory quantity levels as well.
- Compounding the issue, When users were running Purchasing Advice Reports, the software was detecting low levels of product, and making buy recommendations for products that were not physically low on stock. Also, users were just blindly posting the purchase request without validating the overage recommendation that the software was making.
If you are seeing similar behavior to the above, Please contact the CCS Retail Systems Support Department for assistant in correcting it.
– John