1. Commerce
  2. NetSuite Point of Sale (NSPOS)
  3. NSPOS Administrator Guide
  4. NetSuite Point of Sale Overview
  5. Standards and Guidelines

Standards and Guidelines

These topics provide general information about setting up and maintaining NetSuite Point of Sale (NSPOS).

Token Based Authentication and the Integration User

Each NetSuite account for NSPOS includes an integration user dedicated to handling the synchronization connection between NetSuite ERP and the replication server. The integration user is configured during your initial implementation.

We support Token Based Authentication (TBA) for the integration user account. A TBA setup does not require you to enter a token when you log into NetSuite ERP or NSPOS. However, the Token Based Authentication box must be checked on the Enable Features page.

See Ensure Token Based Authentication is enabled in NetSuite ERP.

Payment Card Industry (PCI) Software Security Framework (SSF)

NSPOS is a PCI SSF validated application See Appendix: PCI SSF Information for NSPOS for an overview of NSPOS and PCI SSF requirements.

Note:

In addition to PCI-SSF certification, NSPOS 2020.1.X underwent certification under the Payment Application Data Security Standard (PA-DSS). See PA-DSS 3.2 Implementation Guide -NSPOS 2020.1 to view a PDF of the compliance standard.

When Not To Perform Large Updates of Item or Customer Data

You should not perform large item and customer updates during your business hours, such as when transactions are occurring on your registers. A large update is considered to be any import over 60,000 records.

NSPOS integrates with NetSuite ERP to provide Enterprise Resource Planning (ERP) tools for managing your items, customers and other aspects of your business. You can update items and customers in NetSuite manually or through CSV imports. See CSV Imports Overview.

Updates done in or imported to NetSuite periodically download to your POS registers to ensure all information is synchronized and current. NSPOS performs synchronization uploads to NetSuite of sales and other transactions that occur at the register. This is distributed to other registers in your store through the replication server.

Important:

Item and customer updates of over 60,000 records can impact synchronization across the network. If mass updates must occur during business hours, you should limit each update to 60,000 records or less.

Warning:

When updating items, prices, or other data using a CSV import, always select to Run Server SuiteScript and Trigger Workflows. This option triggers the processes needed for proper synchronization between NetSuite and NSPOS. See Run Server SuiteScript and Trigger Workflows.

Planning an Efficient Opening for New Stores and Registers

When opening one or more new stores, it is important to consider the time needed to prepare the registers with current information from your NetSuite ERP setup. This consideration also applies to registers that were previously active but have been turned off for a long time.

When a register is staged, all information fully loaded and up to date. After staging, registers receive only the information needed to keep them current. When a register is turned off, NetSuite holds all new transactions, price changes and customer information for download to the register later.

If a register is turned off for an extended period and then turned back on, the size of the update can be large and take a while to download. This might delay a register from being ready when you need it.

Important:

Excessive download times can delay registers from being ready to accept sales transactions and can affect overall server performance. This delay can be critical in the event of a new store opening.

To ensure your new registers are ready for business, you should do the following:

  1. Stage registers 24-48 hours before first use. If no major ERP updates will occur after staging, this time can be longer without a significant impact on performance.

  2. If a store rollout requires new item and customer information, if possible, be sure to add or import the information to NetSuite ERP before staging new registers. Then the new information will be included during the staging process.

  3. To reduce the impact to existing registers, large item and customer changes in NetSuite ERP should be performed in small increments. A good guideline is limiting changes to 60,000 records or less per day, performed outside of business hours.

    If you are not certain how to limit the number of records or if this guideline does not fit your rollout schedule, please contact NSPOS Customer Support for assistance.

  4. For registers that have been turned off for a long time, restaging a register can be the fastest method for bringing it up to date. Staging is generally quicker than waiting for large downloads to complete.

Related Topics

General Notices