SuitePOS Release 3.0
UPDATE HISTORY:
NOTE: The order of operations is to upgrade the NetSuite Bundle or Salesforce Package first (as defined on the download page) and then roll out the App upgrades to all your POS terminals after first testing one terminal. It is strongly advised that you test this release with a sandbox account first before running in production. SuiteRetail accepts no responsibility for lack of testing of your environment.
3.0.1a Build 638
- Build that simply increments the version number because a provisioning profile that extends out to 10/1/19 is now used. Prior builds expire 10/20/18 (approx.)
3.0.1 Build 638
- Combines all fixes relating to data center issues and better handles such events so customers can override any NetSuite issues relating to that.
3.0.1 Build 637a (*d)
- Increments version number for customers who are using a MDM solution.
3.0.1 Build 637 (*d)
- By-pass data center dynamic urls for rest calls if NetSuite service fails
- Stabilized FQ processing
- If the Square Reader cannot authorize. Display message.
3.0.1 Build 635 (*d)
- Fixed a minor issue to do with registration and Square/Square Plus authentication.
- Changes to some error messages for Square/Square Plus authentication
3.0.1 Build 631 (*d)
- Enable new Square SDK.
- Fix some price embedded bar code issues
- Fix some Sales Order Module issues
- Misc bug fixes
3.0.1 Build 620 (Beta) (*d)
- Fix issue when internet/server down and shifts enabled. Now allows you to login to the POS.
- Fix some issues centered around tipping
- Fix some small bugs
3.0.1 Build 615 (Beta) (*d)
- Initial production release
- Sales Order Bugs fixed
3.0.1 Build 602 (Beta) (*d)
- Support for NetSuite Line Level Taxes
- Sales Order Support
2.5.1 Build 598 (Beta) (*d)
- Fixed several minor Avatax bugs
- Fixed some bar code scanning bugs
2.5.1 Build 592 (Beta) (*d)
- Added in environment designation on the registration (role) screen, so roles can be better differentiated when you have Sandboxes (SP) and Release Preview accounts (RP).
2.5.1 Build 591 (Beta) (*d)
- Initial beta release
WHATS NEW IN 3.0
Sales Order Module
NetSuite Sales Orders are now supported in SuitePOS. This means you can ring up a sale (and take a full deposit) for later pickup in-store or to be shipped out. Perfect for retailers that do a lot of special orders or keep minimum inventory on hand.
Contact us if you are interested in the Sales Order Module
Support for the new Square Reader SDK
Currently, SuitePOS uses an App to App integration to support Square Payments. Square has released a better way to integrate that avoids issues (and confusion) associated with App to App integration and significantly improves speed.
"Square Plus" is a new Gateway option found under POS Settings and once enabled you simply re-auth Square and re-connect to your reader (after first un-pairing it from the old Square App) in SuitePOS settings menu. You can take a copy of one of your POS Settings record to try it out on one of your terminals to see what you think.
Please note: Offline credit card processing is currently not supported in the New Square SDK.
NetSuite Line Level Taxes
NetSuite Line Level taxes are now supported. This means that products can be taxable or not at the line level. If products require more complex tax configurations such as multi-state jurisdictions and line level taxes, whereby items are taxed at different rates, then Avatax is required.
Quick Service Module
To better service quick service retailers we have now provided the ability to print service tickets to up to two separate LAN printers. This means, for example, that you can now sell cash and carry items plus food and drinks on the same ticket and have the service items (in this case food and drink) print at the service station(s) for preparation.
Contact us if you are interested in the Quick Service Module
Improved Customer Address Management (NetSuite)
Previously we managed customer addresses using the override address field. In order to support SuitePOS features, such as Sales Orders, and to more accurately represent customer addresses (both billing and shipping) we have separated out the address fields and mapped them to the standard NetSuite address fields.
Scanning in the notes field
You can now scan things into the notes field on all sale and refund transactions. This can have a myriad of miscellaneous uses regarding the tracking and storing information on transactions.
Check Payment Method
We now separate checks as another payment/refund method. This makes tracking the check number and reconciliation a lot easier for customers that reeive checks. To set up you need to update the POS Settings record to enable the check payment method and in the case of NetSuite point to a NetSuite Payment Method.
Ignore Projects During Sync
Projects/Jobs are not applicable to SuitePOS. They are no longer pulled in on synchronization.
Hide Discount Items
This feature allows you to hide discount items for item search, selection or scanning. When enabled on the POS Settings record, it hides all standard discount items. It is most useful for those that are using the Advanced Promotions module so that duplicate discount items are not displayed during item search or selection.
Record Last Login Information
To better manage terminals, we have added new fields to the POS Terminal record that show the last registered user, last pos user, last pos user login date and the last version that accessed the record. This is set every time a clerk logs in.
Advanced Orders Renamed to Advanced Payments
The Advanced Order Module has been renamed to Advanced Payments. This is to better reflect what the module does. Special payment methods like "On Account" and "Financed" (coming soon), which allows customers to finance the balance due during checkout, are part of this module.
NetSuite Avatax Improvements
Note: this release requires Avalara Avatax Version 6.0.3 or greater
For those using Avatax, we used to calculate tax at the POS and then when the record posts to NetSuite the tax is re-calculated and the tax documents are posted. In order to support tax for the location of the store, Avatax used a flag on the NetSuite Location record (Pick Up) to designate the address to use. The problem with that is that if you also run NetSuite Sales Orders through that location it would tax based off the stores location. This proved challenging for some retailers.
We have de-coupled the reliance of this field being checked on to the Location record and now silently posts the address of the location as the ship-to address on the transaction. This means you can run both NetSuite Sales Orders and POS transactions through the same NetSuite location and have the tax calculate correctly for each. It is important to realize, that if the Pick Up flag is left as on, then there should be no difference to what you were doing prior. In other words, tax will always use the Location address for all transactions that flow through NetSuite.
Furthermore, returns across different locations and jurisdictions are now better handled for returns that are created from an original sale that occurred at another location with a different tax code. The tax code and date from the original sale is now used.
NETSUITE ONLY:
SPECIAL INSTRUCTIONS:
If you have custom forms linked to the locked SPOS iOS Device role, updating the bundle will revert these forms to the SPOS default forms. In order to correct this, you will need to re-set your custom forms back in the role. If you are already using a custom device role, this does not apply.
Verify permissions on the Terminal role
You will need to manually add the Enable Features “Full” permission to the role your registered terminal user is using. This is typically the SPOS iOS Device role (or your active copy of it).
If a One World NetSuite account, you will also need to add the Subsidiaries “View” permission found under the “Lists” tab on the role (screenshot not available).
You may also need to look and check you have "Employee Search" permission allowed.
SALESFORCE ONLY:
Package URL (Package 2.68):
https://login.salesforce.com/packaging/installPackage.apexp?p0=04t0f000000TeDa
Note: It is important to update these fields and layouts even if you do not intend to use them.
POS Settings Field Label Rename
Please rename the label for the field name "Enable Advanced Orders" to "Enable Advanced Payments"
POS Settings Layout Upgrade
Add the following fields to the Settings Layouts(s) and associated Profiles:
SPOS__Check_Enabled__c to the Payment Methods section
SPOS__Hide_Discount_Items__c to the Transaction section
SPOS__Enable_Quick_Service__c to the Modules section
SPOS__Service_Ticket_1__c to the Receipt section
SPOS__Service_Ticket_2__c to the Receipt section
Pre-cursor to a subsequent release (3.x)
SPOS__Enable_Special_Orders__c to the Modules section
Create a Section called Sales Order under the Transaction section
SPOS__Default_Sale_To_SO__c to the Sales Order section
SPOS__Pickup_Address_Info__c to the Receipt section
POS Terminals Layout Upgrade
Add the following fields to the Settings Layouts(s) and associated Profiles:
SPOS__Last_Registered_User__c
SPOS__Last_POS_User__c
SPOS__Last_POS_Login_Date
SPOS__SPOS_Version__c
Product Upgrade
Add the following fields to the Product Layout and associated Profiles:
SPOS__Service_Printer_Output__c
Transaction Payment Upgrade
Add the following fields to the Transaction Payment Layout and associated Profiles:
SPOS__Check_Number__c
Add a New List Value to Method in Transaction Payments
"Check"
Transaction Upgrade
Add the following fields to the Transaction Payment Layout and associated Profiles:
SPOS__Billing_Attention__c
SPOS__Billing_Addressee__c
SPOS__Shipping_Attention__c
SPOS__Shipping_Addressee__c
 and then roll out the App upgrades to all your POS terminals after first testing one terminal...&media=//suitepos.com/cdn/shop/articles/download_996d3f9b-9e5a-418f-b37c-9c37a5500ea8_600x.png?v=1524884668){kind=link}