Using Proper Physical Count Procedures
It’s always a good idea to make copious notes about physical count configuration and usage issue and to review them prior to doing the actual work.
Typically, this process would include:
- Making backups of current data. – Typically, this would involve backing-up the full database.
- Archiving old count files for previous periods or years. – This would ensure that old files are not accidentally imported.
- Making sure that PDT’s (Physical count device) batteries are fully charged, and that any old count data is cleared from the devices.
- Training staff who will actually be doing the work to properly use both the software and hardware functions.
Taking this proactive approach is vitally important, especially if you only do inventories once a year or less frequently. Failing to do this can mean a potential disaster waiting to happen…
As an example…
An end-user who had just completed a physical count determined that ALL of the adjusted inventory levels were wrong for all of their locations.
In working with the counter staff, the following was later determined:
- When importing the count file into the default PDT’s (Physical count device) software directory, the file downloaded was named the same as what it was last year and downloaded to PDT software’s default directory.
- However, their default NCR Counterpoint parameter was pointing to a different import folder than the PDT software default. When the staff imported the count file, they were actually importing the previous year’s physical count file. – No one had checked the date of the file or the content before importing it.
- After importing the count file, the user did a blind post the count data without checking any of the data, and just let the system to adjust all items not counted to zero.
To compound matters…
- No backup of the existing CounterPoint data files was done prior to the start of the import process. – This means that they had no recourse but to restart the physical count process.
- The count file had obvious errors in it (Barcodes scanned into the quantity field; Quantities input into the barcode field; Blank Quantities; etc.). – The NCR Counterpoint software has both a verify function that can be used prior to importing data and various worksheets that can be used for reviewing and validating data.
- Other users had started multiple physical count snap-shots that involved many of the same items. Some of these has been open for as long as a year.
- On detecting the initial problem, the staff repeated the exact same import/post process (using the wrong file) at least twice, before finally creating a new physical count, and without doing any imports, then zeroed-out
the entire inventory for that location.
The one saving grace here was the current year’s count file uploaded not been deleted, nor had the PDT been purged after the upload.
If you are unsure of any part of the physical count process, CCS Retail Systems can provide both training and technical assistance prior to starting the count, as well as ongoing process support during the actual count.
PCI DSS Requires Transition to Secure Pay Before April 30th, 2018!
TSYS and WorldPay Ending CPGateway Support
TSYS will discontinue support for the NCR Counterpoint Gateway (CPGateway) platform on April 30th, 2018. Merchants who are currently processing EDC payments through TSYS via CPGateway are advised to migrate to NCR Secure Pay before this date to ensure they can continue processing without interruption.
In addition, Worldpay will discontinue support for CPGateway within a similar time frame (we will announce the actual date on which CPGateway support will end for Worldpay merchants as soon as it is confirmed). Again, we strongly encourage merchants who are currently processing EDC payments through Worldpay via CPGateway to migrate to a Worldpay (TCMP) account for NCR Secure Pay to avoid any interruptions.
TLS (Transaction Level Security) 1.2 Transition
Getting Ready for TLS 1.2 (Check My TLS Status)
Payment Card Industry Data Security Standards (PCI DSS) require all PA-DSS validated payment applications to discontinue the use of “early TLS” (i.e., all versions of SSL and TLS 1.0) by June 30th, 2018.
To comply with this requirement, NCR Secure Pay will no longer accept early TLS connections after 2:30 A.M. on June 5th, 2018. In addition, updates to NCR Counterpoint V8.5.4 and V8.4.6 that will require the use of TLS 1.2 for payment transactions processed through NCR Secure Pay will be released as follows:
- V8.5.4 Patch 002: Scheduled for 2/20/2018
- V126.96.36.199 Service Pack: Scheduled for 3/6/2018
NCR does not plan to release patches or Service Packs to support TLS 1.2 in other versions of NCR Counterpoint.
To sign up for an NCR Secure Pay account, Contact CCS Retail Systems ASAP.
Are You Ready For EMV Security?
Before you start taking chip cards (EMV) with your NCR Counterpoint System there are a few thing that need to be done.
- First, you must be on at least NCR Counterpoint version 188.8.131.52, although this version of the software will work with EMV, it is recommended that you upgrade to the latest version of 8.5.3 so you may benefit from any fixes and new features.
- With 8.5.3 in mind, it is also necessary that your operating system is at least Windows 7, as of 8.5.2, Windows 10 is supported. Windows 7 and above support the latest encryption protocols to help keep your data safe. Windows XP does not have these updated protocols and will not be updated by Microsoft to include them.
- If you are already taking credit cards but have not updated to NCR Secure Pay, that will need to be done as well. With NCR Secure Pay, it will protect you and your customers data as it is no longer kept on your system and is tokenized to further protect the data. You may also need to update your merchant account to support NCR Secure pay. CCS can work with you and your merchant services rep to get your account ready for NCR Secure Pay and EMV processing.
- You must be using an Ingenico ISC250 Pin Pad that has the correct version of firmware to work with your software AND NCR Secure Pay EMV processing. Firmware will vary depending on NCR Counterpoint version. CCS can help find your current firmware version and update (if necessary) to the correct version.
- Pay codes (Touchscreen and Regular ticket entry) – the following pay codes must exist and be assigned to the store setup (but do not necessarily need a button) VISA, MC (or MasterCard), DISC (or Discover), AMEX (or American Express). Also there must be an EMV pay code button to activate the chip reader when processing a chip card. Note – If a card has a chip, it must be inserted into the reader, if a card does not have a chip it may be swiped just like before. In the case of a chip that will not read, a Manual EMV button can be setup to allow the customer to manually type in their card information securely through the Pin Pad.
- Once the above has been complete, CCS can test the setup in a test environment to be sure that all settings both on the bank and the software side are correct. Once confirmed working, CCS can setup a time to implement and go through a test transaction so you can see the flow of an EMV chip card transaction.
If you need help with any of the above, please contact the CCS Retail Systems Support Department @ 800.672.4806 or send us an email to get you started on your way to EMV processing
NCR Counterpoint API Release
|NCR Counterpoint API
Great News! NCR is pleased to announce the release of version 2.0 of the NCR Counterpoint API, which includes several new features and resolves a number of issues in the initial v1.0 release.
If you are updating the NCR Counterpoint API from v1.0 to v2.0, you can install the new version over your existing installation by downloading NCRCounterpointAPI.exe from the Partner Portal and running it on your NCR Counterpoint API server. All existing settings, users, and endpoints will be retained when you update to v2.0.
Detailed information about the functionality and use of the Counterpoint Rest API is maintained on GitHub. Please visit https://github.com/NCRCounterpointAPI/APIGuide on GitHub for more information about the Counterpoint Rest API.