NetSuite releases two system upgrades per year to all accounts, often providing new functionality within existing features in addition to launching brand new capabilities.  Prior to being upgraded to the new release, all accounts are given access to a release preview environment that allows users to preview the changes in a sandbox-like setting.  Detailed documentation describing all changes that are included as part of the new release are also provided at this time and can be accessed from the New Release portlet and in SuiteAnswers.  In this post, I’m going to share the five changes that are being made as part of 2019.2 that I am most excited about.

NetSuite natively supports direct shipping integration with but UPS and FedEx, which allows users to print shipping labels for a wide variety of service levels for each carrier from within the NetSuite UI.  To expand upon those capabilities, NetSuite also supports the integration of third-parting shipping platforms that connect to hundreds of other carriers, such as USPS, DHL, and even LTL and large freight transportation providers.  These integrations allow for shipment information to be passed back into NetSuite automatically, however the standard functionality that converts UPS and FedEx tracking numbers into links does not work with any other carriers.

When choosing a costing method for your inventory it is very valuable to fully understand all of your options and the impact of such a decision. Things to consider when making this include the following:

On Thursday, August 2nd, Evan Goldberg, the Founder of NetSuite and EVP of Development for Oracle NetSuite released the following video titled Today, Tomorrow, and the Next 20 Years for NetSuite. 

Guest Post by Paul Seibert, E-Commerce Practice Director at SuiteCentric

The rapidly consolidating cellular telephone industry in the United States, and the primary service providers that form that industry, are in today’s marketplace faced with a number of pain point. These include but not limited to network congestion collapse, which exacerbates an increasing inability of the major cellular carriers to monetize packet traffic, along with unabated increases in P2P or peer-to-peer traffic, unlimited connectivity and Over-The-Top OTT content strategy.

You’ve got complex orders with different pricing for each customer. You need a flexible system in place to streamline the order-to-cash process.

If you have siloed systems, the order management process can be very manual and prone to human error. But, what would your company look like if you could automate and manage your entire order lifecycle from order capture and validation, to order release and shipment confirmation, all the way through to follow up customer communications and payment settlement?

With the new revenue recognition requirements implemented by FASB, many companies are looking for support on how to manage these requirements.  The changes to revenue recognition have an impact on both organizational business processes and configurations within the software that manages revenue.  The following article will illustrate considerations when managing the new requirements.  ASC 606 has listed 5 core principles to managing revenue:

In my previous blog, we explored what Project Methodology is meant to do at a high level and why it is important.  When professional services organizations share their methodology with their customers, they are showing them what to expect and preparing them for success.  The more the client is bought into the outlined process and understands the value, the more likely the project is to succeed.

This article is a continuation of my previous post, in which we started setting up a workflow using SuiteFlow to pre-populate several field values within a ticket record used by support staff to help improve their overall efficiency. We began by configuring the workflow itself, and then added a simple automation to set and unset the value of a custom field called “Completed By” based on the value of the “Status” field.  In the second half, we’ll dive deeper into workflows and use joins to source fields from other related records to populate additional fields on the ticket for an even more dynamic automation.