Tutorial: On-Demand Customers for NetSuite

Tutorial: On-Demand Customers for NetSuite

On-Demand Customers, if enabled, allows you to pull in the sever-side data, that is not stored locally, into SuitePOS. This significantly reduces bottlenecks (and times) during customer syncs because not all the customers are required.  

STEP 1: Enable On-Demand Customer

NetSuite POS Settings:

STEP 2: Fine Tune Saved Searches

Either the default Customer Saved Search (or the store level Customer Saved Search - release 4.1.0+) can be modified to reduce customers sync'd.

POS Settings - Saved Searches:

Minimum Requirements
At a minimum, the Anonymous Customer must be brought in on the Customer Saved Search.

As with any changes to the Saved Searches, once implemented a FULL SYNC must be performed on just the Customers. This will avoid creating orphan customer records locally (that can become quickly out of date). 

Manually Select On-Demand Customers

Customers can be searched by manually typing in the letters. This will auto-reduce the customer data locally.  If Customers are not found, you can select either email or the phone number (direct search) and this will do an exact match server-side and bring the customer in.  You can also do a generic server-side search by hitting the magnifying glass. 

Very Large Customer Counts
For customer counts that exceed 200k, it is best to utilize direct searching on email or phone number versus trying to do a generic search. 

Manual Customer Search:


While on-demand searching is very useful for reducing sync times there are some things that need to be considered and balanced.
No Internet or NetSuite Down
With this enabled, if the internet goes down (or NetSuite is down) then you will not longer be able to perform customer server-side searches.  Only local searches can be used.
Retrieval Times
Customer retrieval times will highly depend on your server package with NetSuite and the current load. Most timings we have seen for direct server-side retrieval  is a second or less (for up to 4M customers).
Search Limits
For performance, we have limited generic customer searches to 300. 
Daily or manual full/diff syncs will clear out customers stored locally. This is to avoid creating orphan customers that are not picked up during the sync (due to the criteria being limited).

    • Related Articles

    • Tutorial: On-Demand Items for NetSuite

      On-Demand Items, if enabled, allows you to pull in the sever-side data, that is not stored locally, into SuitePOS. This significantly reduces bottlenecks (and times) during item syncs because not all of the items are required. This is primarily used ...
    • Implementing On-Demand Customer and Items Strategies and Optimizations

      STOP On-Demand Customer and Items should not be considered if your customer or item syncs happen at an acceptable speed; generally when there are less than 20,000 items and 40,000 customers. On-Demand Customers On-Demand Customers should only be ...
    • Tutorial: NetSuite Saved Customer and Item Searches

      Saved Customer and Items Searches allows you to customize what is including in the syncs and pin it at the POS Settings level (typically a store). This is used to override the Active Saved Searches that apply to all POS Settings and provides an ...
    • Tutorial: Enabling UOM (Units of Measure) (NetSuite Only)

      Requires the purchase of the SuitePOS Advanced Inventory Module UOMs (Units of Measure) is a NetSuite feature that permits a single item SKU to be stocked and/or sold in various configuration Units at the click of a button. Using the Advanced ...
    • Tutorial: Activating/Deactivating Optimize Diff. Syncs. in NetSuite.

      Diff Syncs are performed each login to SuitePOS (if enabled in POS Settings) or at least every day. Diff Syncs search for customers and items that have been updated since the last Diff Sync and applies those updates to the local device cache. Some ...