To insure a successful mobile POS pilot or roll-out, retailers must
- Set clear goals and objectives
- Establish a multi-disciplinary dedicated payment team
- Define clear product requirements
- Select Vendors to Partner with
- Develop a comprehensive project plan
- Measure the results of the test
In the third part of this series, we will look at the importance of defining clear product requirements.
Define Product Requirements
- The specific application and the physical hardware you choose have many make-or-break implications, so it’s very important that you pick the right application and device.
- Mobile POS is not just your cash register or your web site on a tablet.
- It is an entire new way of interacting with your customer. Nothing sinks a pilot quicker than a application that does not meet the user’s needs.
- Mobile POS does need to support your current IT environment. Sales data, payment information, sales clerk tracking, etc. all need to be considered. The transaction set supported on your mobile device needs to be considered. Are all payment types supported? All discounts, special pricing, etc. Is access to custom orders required? Inventory look-up across all stores.
- How will your system interface to any loyalty information you have? Will it access customer e-commerce purchases?
- How will these devices be secured? This includes physically when not in use. Do you use a check-in check-out system when sales associates take a device? What about access control to the tablet? GPS tracking? How are new applications downloaded? Updated?
- What back-end systems need to be interfaced to and what data is required to be sent to the tablet application?
- Is the mobile POS a seamless extension of the in-store system? Can sales clerks move freely between systems? Can you suspend a sale on one device and retrieve it on another?
- A successful mobile pilot and roll-out requires that complete product requirements be defined and implemented prior to the pilot.