Currently, only the Salesforce Enterprise Edition with "Person Accounts" enabled is supported.
The retailer is responsible for installation, applying the upgrades to the SuitePOS package and app, and testing. It is recommended that these tasks are performed by a qualified Salesforce Administrator in a sandbox environment first.
Overview
SuitePOS is installed and configured under the guidance of a SuiteRetail Implementation Manager. There are two primary components; the SuitePOS Package which contains the server-side code, and the installation of the SuitePOS App on the terminal/device.
STEP 1: Prepare your Salesforce Org
Install the latest Salesforce Package (URL is in the most recent Release Notes)
Create a new profile, say "SuitePOS", based off any other appropriate profile you have.
Change the default layouts as follows:
Products > SPOS Product Layout
Accounts > SPOS Account Layout
Person Accounts > SPOS Person Account Layout
Salesforce Profile Layout Screen:
Enable the following SuitePOS Lists and Values for each Person Account Record Type:
Picklist1 through Picklist5
Enable the following SuitePOS Lists and Values for each Product Record Type (if applicable):
Merge Line Items (Set Default: "Use Settings")
Type (No Default). Note: If Type is Blank the Product is not displayed in SuitePOS
Enable Test Area Capture. (Set Default: "Disabled")
Sub Type (No Default)
Service Printer Output (No Default)
Enable SuitePOS fields for the standard objects on all relevant Account and Product Layouts. Best practice is to create a Section called "SuitePOS"
Allocate Permission Sets to Salesforce Users (including the System Administrator)
Enable Lists and Values for Each Person Account Record Types:
Person Account Layout (Example):
Product Layout (Example):
Most clerks will be 'Terminal Users". Terminal Users (aka. Registered User) can be shared across devices to avoid having to purchase a Salesforce User for each terminal. Salesforce governance restrictions may apply.
"Admin Users" are System Administrators typically (or Retail/Store Managers).
STEP 2: Download the SuitePOS App
For retailers with 10 terminals or more, it is highly recommended using a Mobile Device Management (MDM) solution to better manage and co-ordinate each device.
Open the SuitePOS app and select Salesforce on the registration screen
Make a note of the Device Id (a unique identifier needed later)
OR..MDM distribution
Using IPA file distribute the App.
Open the SuitePOS app and select Salesforce on the registration screen
Make a note of the Device Id (a unique identifier needed later)
Example SuitePOS Registration Screen:
STEP 3: Finishing Up (Using the Sample Data)
Add in at least one employee (clerk) to POS Access; set the access rights and a PIN.
Modify the one terminal (from the sample data) on POS Terminal; set the device id and terminal options.
Modify the one setting (from sample data) on POS Settings; set up all the options.
Ensure that one terminal is associated to at most one POS Setting.
Ensure there is at least one Product enabled for SuitePOS.
Salesforce POS Access:
Note:
Unlike a Registered User (which can be unique (or shared) across all clerks and equates to a Salesforce User; POS Access Users are unique for each clerk and have their own PIN.
Salesforce POS Terminal
Salesforce POS Setting
Salesforce POS Setting related to POS Terminal
Salesforce Product
STEP 4: Test SuitePOS (using sample data)
Open the SuitePOS App on one terminal
Register the SuitePOS App using a Salesforce User (one time event)
At login, enter a valid clerk PIN
Add a product to the cart
Complete the sale (using cash as the payment)
Check the sale has been recorded in Salesforce
SuitePOS Registration (one time event)
SuitePOS Clerk Login
SuitePOS Sale
SuitePOS Payment
Salesforce Transaction Screen (Header)
Salesforce Transaction Screen (Detail)
Start the implementation
Initiate the implementation with your SuiteRetail Project Manager.
The retailer is responsible for installation, applying the upgrades to the SuitePOS bundle and app, and testing. It is recommended that these tasks are performed by a qualified NetSuite Administrator in a sandbox environment first.\ Overview SuitePOS ...
In order for SuitePOS to work you will need to first create a POS Terminal record using the 'Device Id" of the terminal and allocate it to a POS Settings record (which contains all of the configuration parameters). Once that is complete, you then ...
Custom fields (at the Customer/Account level) are very useful for tracking any metric about your shoppers. You can use them to take notes, track preferences and desires and even script information to read only fields to showing things like $ spend ...
From time to time credit card payments have been processed but the underlaying transaction has failed to write to NetSuite or Salesforce; or it is simply missing. The solution will depend on the underlaying cause. This may include: The transaction(s) ...
Sometimes clerks need to perform actions directly in NetSuite. This could be activities such as seeing analytics or reports, researching transaction history and/or accepting payments against receivables. To make this process easy, SuitePOS allows a ...