Getting Started with NetSuite Ecommerce

Getting Started

• Ensure that you have a Pipe17 account created
• Make sure you are licensed to use the Pipe17 NetSuite Ecommerce Connector. If you're not certain, reach out to your Pipe17 rep

Connector Setup (Basic Flows)

Get connected to the NetSuite Ecommerce connector

1. 1. Install the Pipe17 SuiteApp in your NetSuite account
      1. Provide your Pipe17 rep with the NetSuite account ID (from the URL of your NetSuite instance) for SuiteApp whitelisting
      2. In NetSuite, go to Customization > SuiteCloud Development > SuiteApp Marketplace > and search "Pipe17"
         1.                    
      3. Add the new access role
         1. Make sure to have an employee record created in NetSuite called "Pipe17". To do this, search 'Employees' in the search bar in NetSuite, then create a new one. Add the Pipe17 role access to this employee record
         2. Do not select the 'Partner Role' option on this record, or you will encounter an error later
         3. We also suggest adding Administrator role access temporarily to we can best help with the connector setup and troubleshooting during onboarding
      4. Create access token
         1. Setup > Users/Roles > Access Tokens > New
         2. 
         3. Copy the values for Token and Secret, to be pasted into Pipe17 portal next
   2. In Pipe17, go to the "Integrations" tab on the left side of your Pipe17 portal, and click "Add Integration". Select the NetSuite E-commerce connector:
      1. Input your credentials, be sure to select 'I have installed the Pipe17 SuiteApp in my NetSuite account'
         1. Find the account # in the beginning of the NetSuite URL or go to Setup > Company > Company Info: Account ID
         2. Find sandbox account IDs this way instead of the URL since the case and underscore will be different than the URL shows
   3. Once credentials are successfully entered, and the connector status shows "Connected" click over to the "Settings" tab within the connector. Step through the settings below 

Settings configuration

Enabling and disabling flows can be configured with the options at the top of the settings page. The settings on the bottom portion of this page are more specific configurations for each flow

Follow the order of operations below for our suggested setup process for most common use cases. For simplest testing, enable each flow one by one and confirm data syncs before moving to next step.

1. Pull locations from NetSuite into Pipe17
   • This is a pre-req for pulling orders. The location must first exist in the Pipe17 locations list
   • Find the flow labeled "Pull locations to Pipe17" and enable it
   • To filter to a specific location, use the Location Filter box below
     • *Note: if you just installed the connector and go connected in the last few minutes, check back later for filter options to have synced up
2. Pull products from NetSuite to Pipe17
   
   • Enable the flow at the top portion of the page
   • Products will begin to sync to Pipe17 and can be viewed from the Products tab in your portal
   • Be sure to leverage the Product Filter on bottom section of page as needed to pull only a subset of products out of NetSuite i.e. TYPE = Inventory
     • Typically all products are NOT synced, this filter is leveraged to filter by type so we don't pull items such as non-inventory items/discount items etc that will not be needed within the sales channels/fulfillment channels
3. Push inventory into NetSuite to Pipe17
   • This flow allows Pipe17 to create inventory adjustments in NetSuite to keep inventory quantities in sync
     • If not done already, save your progress here and setup the connector you will use to pull in inventory into Pipe17 to be used for testing in this flow, or import inventory to Pipe17 manually
     • Make sure to link the NetSuite location to the fulfillment connector's location in the Inventory tab > Locations list. Do this by editing the fulfillment location and "Add external location" at the bottom, add the corresponding NetSuite location
     • Come back to this step once inventory exists in Pipe17 Inventory page
   • Enable the flow for inventory push at the top of page
     • This push checks for inventory discrepancies every 4 hours, and creates an inventory adjustment in NetSuite if found
     • There is an alternate setting option in the section below to opt for only adjusting inventory in the middle of the night rather than every 4 hours
   • In the Inventory subsection below, enter the subsidiary ID to use on inventory adjustments, along with the GL account internal ID
4. Set up order routing logic: there are multiple options for how to send an order through to fulfillment once it is ingested into Pipe17. Before enabling order pull settings in the NetSuite connector, determine the way orders should be routed to fulfillment. Save your progress and return to this page after doing the below steps
   • If assigning a location in NetSuite rather than Pipe17, follow these steps:
     • Enable the setting in Pipe17 Order Routing Tab (on the left side of Pipe17 portal) > Settings subtab:
       • 
     • Save this and go back to the NetSuite connector settings page. Enable the setting:
       • 
     • This setup will tell Pipe17 to automatically generate a shipping request to the preassigned location when an order is ingested to Pipe17 from NetSuite
   • If assigning a location based on Pipe17 order routing rules (and ignore the location provided by NetSuite), follow the steps:
     • Go to Pipe17 Order Routing Tab (on the left side of Pipe17 portal) > Routing Rules subtab
     • Create order routing logic here and save
5. Pull Sales Orders from NetSuite to Pipe17
   • Navigate back to the NetSuite connector setup page, enable the pull orders setting at the top of the page
   • Below in the Orders subsection:
     • "Pull Orders From" Sales Orders
       • Use this option to ingest orders from NetSuite to Pipe17 prior to a fulfillment being created. Most common use case
     • "Pull Orders From" Item Fulfillments
       • Use this option to ingest orders only once a fulfillment is already created in NetSuite. This would be for a use case where order routing is managed in NetSuite. This might also be used to only send a partial order to Pipe17 rather than allow a full order to be sent for fulfillment
     • Leverage date filter to exclude orders prior to a date, note this defaults to only pull orders from the time the connector was installed or later. Adjust as needed
     • Leverage Sales Order Filter to input additional criteria for which orders should be ingested to Pipe17 i.e. Location, custom order attribute etc
       • If using setting for "Pull Orders From" Item Fulfillments, leverage the filter below this specific to Item Fulfillments record
   • Orders will sync to Pipe17 based on these settings, and automatically route based on routing configuration from step above
6. Enable fulfillments to sync back to NetSuite
   • Enable the fulfillments push flow at the top of the page
   • Several advanced settings exist in the fulfillments subsection, to discuss with Pipe17 rep

Use Cases to Consider

• Orders
  • Standard ecommerce order
  • Order that should split ship
  • Cancelled order prior to fulfillment
  • Cancelled order post fulfillment
  • Order for an out of stock item
  • Order that needs an update after placement - prior to sending to fulfillment vs. post
• Fulfillments
  • Partial fulfillment
• Products
  • Create new
  • Update existing product attribute
• Inventory
  • Inventory change in 3PL system

Testing

1. Add a new product in NetSuite, confirm the product gets created automatically in Pipe17
2. When inventory becomes available in the fulfillment location, confirm inventory reflects accurately in Pipe17
3. Adjust inventory in Pipe17, confirm an inventory adjustment gets created automatically in NetSuite
4. Create an order in NetSuite, confirm order gets created automatically in Pipe17
5. Confirm shipping request gets created automatically (based on order routing setup) against the order in Pipe17
6. Confirm order gets created automatically in fulfillment system
7. Once order is fulfilled, confirm fulfillment syncs to Pipe17
8. Confirm fulfillment syncs to NetSuite

Flow Examples