Fixes NSPOS 2025.1.0

In addition to behind-the-scenes fixes, NetSuite Point of Sale (NSPOS) 2025.1.0 includes the following updates.

• Void Processing Rejected After NSPOS Kiosk Agent Restart – Payment void transactions might have been rejected on NSPOS Kiosk if an agent restarted the system. This issue has been resolved in this release.

• Formatting of Currency Not Working Properly in Some Cases – For all NSPOS and NSPOS Kiosk receipts, the currency for receipt formatting is taken from the location currency setting. If this is not set, or is set incorrectly, we load the currency from the subsidiary currency setting. If both the location and subsidiary currency is not set, the application loads the currency from the operations system setting.

• SuiteTax Handling Items with Old or No Tax Schedules – The fall back to default Tax Schedule was not working properly when pre-SuiteTax schedule or no tax schedule was not configured for an item. This has been fixed in this release.

• Continuation to Adopt the Latest Technologies – We've migrated internal components to .NET8, to keep pace with industry standards.

• Limitations of Item images on Kiosk -limitations – Images from the File Cabinet folder User Documents assigned to items are not going to be downloaded to NSPOS or Kiosk. To use web store images in Kiosk, you need to have Site Builder features enabled.

• Windows Kiosk Mode Behavior – Closing the Kiosk user interface in configured Windows Kiosk Mode will turn off the machine.

• Automatic Database Backup When the Database Becomes Corrupted – Staging now automatically detects database corruption and creates a backup.

• SuiteTax Not Updating Data Properly – In some cases, the tax data for the SuiteTax engine was not updating properly. The data should now update as expected (issue 805091).

• Register Uploading Data to NetSuite ERP Correctly – In some cases, due to large amounts of data, registers might have had problems with sending data to NetSuite ERP. This issue has been resolved and data should upload as expected (issue 722410 and issue 722465).

• Sales Orders Created in NetSuite ERP Without Specified Location Failed to Sync to NSPOS – If a user created a Sales Order in NetSuite ERP, NSPOS had a problem syncing its data to the NSPOS system. NSPOS now syncs data successfully into the system (issue 764941).

• Inconsistent Item Record Data in ERP Causing All Items downsync – If data on the item record is inconsistent, then NSPOS cannot process it. The item is skipped, the problem is logged, and downsync continues with the next item (issue 797602).

• Barcode Printing Not Working Properly on Some Types of Star Printers – Changes were made to receipts for both NSPOS and the NSPOS Kiosk to fix this problem (issue 740870).

• Time Discrepancy in Monitoring Data Between NetSuite ERP RA-Workstation Monitoring and NSPOS "normal state" – Data shown in NSPOS normal state shows the time according to the operating system time zone configuration. Data shown at RA-Workstation monitoring will show in UTC format with timezone information.

• Customer Monitor Used with NSPOS Not Showing Items Beyond Screen Size Properly – If you had two monitors configured for NSPOS, the customer monitor was not properly showing items if the list of items exceeded screen size. This issue has now been reoslved (issue 795146).

• Long Class Name Assigned to Item Made Customer Unable to Use Item in NSPOS – If your class name was too long while working with Classification/Class in NetSuite ERP, that item might not have been usable at NSPOS for sales. This issue has been resolved (issue 791743).

General Notices