Identifying Limitations of POS Features
On this article you will get to know Limitations of POS Features. Conducting the audit is comparatively easy if you plan to the method. The knowledge you derive are going to be invaluable for you and your entire team. First, you’ll want to work out the dimensions and scope of the project. It’s important to work out each type and version of POS system that your company uses, alongside the department-specific functionalities, like service desk, restaurant, electronics, and pharmacy, and the way much visibility your organization or team has got to the related data on the rear end. This last piece is particularly important because the exercise is actually pointless if the activities are invisible to you.
Next, you’ll want to develop a comprehensive list of all transactions that require to be tested and understood. This list would come with legitimate transactions, high-risk transactions, and any activities which will drive a high-amount exclude (HALO) or low-amount exclude (LALO) action. HALO and LALO actions are driven by amounts that, once reached during an item or transaction-level occurrence, will “lock out” the cashier from performing the function without some sort of manager intervention
The list below shows some samples of transactions you’ll run to know platform limitations. These examples are strictly associated with refunds and not the whole scope of the project:
• Refund with a receipt
• Refund without a receipt
• Return on cash, check, mastercard, gift cards, or merchandise credit due bill (When watching refund to mastercard, consider both manual entry and swiped.)
• Refund on employee purchase
• Refund of bottle return
• Refund of a purchase item, BOGO, coupon, or markdown
• Refund of cash order
• Refund of warranty or long-term service agreement
• Refund card or merchandise credit (Can it’s re-charged? HALO or LALO?)
• Change refunded item to “damaged” in controller
• Attempt to record a negative sale
• Attempt all of the above in training mode (Is there a flag or differentiator?)
• Complete a non-scanned refund with item not on file
• Try to bypass the web refund procedures
• Refund on same day, same store
• Refund on same day, different store
• Refund on fraudulent item not purchased (directly off shelf)
• Refund on different day, different store
This list is fairly robust but nowhere near complete. The list should include all kinds of transactions, including basic sales, item voids, post voids, coupons, discounts, damages, suspended transactions, then forth. There should be special considerations given to satellite registers or POS systems within the specialty departments mentioned earlier.
Going Beyond POS Features
Learning the restrictions of every data-generating system within the shop is important to find out where your company could also be missing stopgaps or countermeasures. As an example, what’s the dollar threshold at which a cashier can process a price override without the necessity for management approval? Most of you almost certainly thought of a dollar amount as you read this. But are you sure? Simply because the quality procedure or cashier training manual both say the quantity is $10, for instance, this doesn’t mean that the system isn’t set at a special level. And it’s our responsibility to know what that level is.
In a perfect world, we might compile results data and make a worth proposition. This might be leveraged to encourage our partners in IT, systems, or operations to correct the difficulty and to make sure that our platforms limitations always match our protocols. Within the world, however, this is often not always possible. But as long as we are conscious of the inconsistency between platform and protocol, we will build reporting to watch for deviant behavior.
