The SuitePOS Upgrade/Release Process

The SuitePOS Upgrade/Release Process

One of the many advantages of subscribing to software is that you will get upgrades from time to time. This is important so that the latest version of the platform (NetSuite or Salesforce) and Apple iOS are properly supported. Upgrades are also a mechanism we use to fix bugs, improve processes and add valuable new functionality that may be important to you.

Upgrade Components

There are two parts to an upgrade. For each upgrade, one or both components need to be applied for SuitePOS to function correctly. This is determined and outlined on associated Release Notes that are provided.

The server-side (or platform) upgrade is perform by a qualified Administrator that installs the new Bundle (NetSuite) or Package (Salesforce).

The client-side (or device) upgrade is co-ordinated by a qualified Administrator that installs the new App on each device. In some cases, the App can simply be overwritten (and therefore a re-registration and a full sync is not required). In other cases, the App has to be uninstalled first and re-installed (generally for major upgrades). 
For retailers with larger terminal counts a Mobile Device Management (MDM) solution is recommended so that the client-side upgrades can take place timely, accurately and efficiently.

Types of Upgrades

  • Major Releases eg. 3.5 adds specific support for new versions of the platform (NetSuite or Salesforce), new (more complex) functionality and bug fixes. Major releases typically happen once or twice a year.
  • Minor/Patch Releases eg. 3.5.1 adds critical functionality, urgent support and/or bug fixes. These can happen several times a year. This may involve upgrades to either the server-side or client-side code (or both).
For Major Releases, it is possible that the SuitePOS App will be backward or forward compatible to other bundles/packages. That said, it is not guaranteed. End user testing is always required.
Once a server-side NetSuite Bundle or Salesforce Package upgraded. You cannot go back.
Some releases my require you to remove and re-install the SuitePOS app; if that is the case and Full Sync is required - this will be identified in the Release Notes.
If using NetSuite and a Full Sync is required, ENSURE you have enough concurrency to be able to perform full syncs of all your terminals. Alternatively you have to manage the full syncs manually across your terminals. 

Testing Upgrades

You are responsible for testing new releases. We regression test upgrades the best we can but all permutations of unique business configurations cannot possibly be tested.  Ideally you test in a Sandbox environment by carefully reading the release notes, upgrading and running typical business transactions. This ensures you have tested your roll out procedures and become familiar with the new features. We cannot emphasize how important this step is.

If you do not have a Sandbox, we would recommend that you pick an appropriate time (a very slow period or after hours) and upgrade the server-side bundle/package first (if applicable); followed by the app on a few devices. Once things are stable (after running some tests); roll out to all your other devices.

The Upgrade Process Summarized

  • Read the release notes carefully
  • Test on a Sandbox first if you can
  • In production, plan ahead and pick a convenient time
  • Upgrade the server-side bundle/package
  • Upgrade a few terminals and run some tests
  • Roll out to the rest of the terminals.
It should be noted that in some cases you can simply overwrite the app and therefore there is no need for a re-registration and full sync. In other cases, you have to remove the app and re-register (which performs a full sync).

The SuitePOS App and Release Notes are here: Download the SuitePOS App
DO NOT PARTIALLY UPGRADE FOR LONG PERIODS OF TIME:
In other words: do not install the App on devices without being on the supported server-side bundle/package (or vise-versa). Ensure all active terminals are on the same version.