Getting Started with NetSuite ERP

Getting Started

• Ensure that you have a Pipe17 account.
• Make sure you are licensed to use the Pipe17 NetSuite ERP Connector. If you're not certain, reach out to your Pipe17 onboarding manager
• Follow the steps below to add your connectors

Connector Setup (Basic Flows)

Get connected to the NetSuite ERP connector

• • Install the Pipe17 SuiteApp in your NetSuite account
    • Provide your Pipe17 rep with the NetSuite account ID (from the URL of your NetSuite instance) for SuiteApp whitelisting
    • In NetSuite, go to Customization > SuiteCloud Development > SuiteApp Marketplace > and search "Pipe17"
      •                    
    • Add the new access role
      • Make sure to have an employee record created in NetSuite called "Pipe17". Add the Pipe17 role access to this employee record
      • Do not select the 'Partner Role' option on this record, or you will encounter an error later
      • We also suggest adding Administrator role access temporarily to we can best help with the connector setup and troubleshooting during onboarding
    • Create access token
      • Setup > Users/Roles > Access Tokens > New
      • 
      • Copy the values for Token and Secret, to be pasted into Pipe17 portal next
  • 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
    • 
  • Input your credentials, be sure to select 'I have installed the Pipe17 SuiteApp in my NetSuite account'
  • 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. Push Orders to NetSuite

   • Find the flow labeled "Push orders to NetSuite" and enable it. View the specific settings in the orders subsection below

   • Common settings: these are general order related settings and contain field help in the ? mark icon to the right. 

     • Leverage the order date filter to only push orders from a certain date over to NetSuite

   • Sales orders preferences:

     • Filter order creation by source: Enter the source channel(s) allowed to create orders in NetSuite i.e. fabric, amazonfbm, amazonfba, bigcommerce, shopify

       • If not used, no filter for source channel will be used, meaning orders from all channels will be pushed.

     • Create orders when order status is: Choose which Pipe17 status should trigger the creation of sales orders or cash sales into NetSuite. This prevents orders being pushed to NetSuite until they are in a specified status in Pipe17

       • For example, if an order comes in with a 'Hold' status, these could be prevented from syncing to NetSuite until they are in 'Ready for Fulfillment' status

       • If not used, orders on all statuses will be pushed.

     • Send order updates to NetSuite: This allows order changes that happen in the source channel to sync through Pipe17 to NetSuite. Do not enable if updates are being made manually in NetSuite as these will be overwritten by the integration's updates.

     • Update order when Pipe17 order status is: Choose which Pipe17 status should trigger the update of sales orders or cash sales into NetSuite

       • For example, you may input the status Ready for Fulfillment but disallow order changes to sync to NetSuite after the order has already been transitioned into a Sent to Fulfillment status

       • If not used, orders on all statuses will be updated.

     • Update Pipe17 order status to "Sent to fulfillment" when is pushed to NetSuite: This checkbox is only to be marked when no other fulfillment channel is connected

       • Typically this order status change occurs when Pipe17 is connected to a 3PL/warehouse, but if orders are only being sent to NetSuite for direct fulfillment, this option should be enabled so the status can be updated in Pipe17 when the order is sent to NetSuite.

     • Create customer deposits for paid Sales Order in NetSuite: Typically used for ecommerce orders paid by the customer at the time of order creation

   • Cash sales preferences - if required to push cash sales instead of sales orders in NetSuite, use the setting called "Create cash sales in NetSuite"

     • This leverages similar logic noted for the sales orders regarding source channels, Pipe17 statuses, updates etc.

     • Typically used for in-store scenarios with no shipping process or for Amazon FBA.

     • Only create cash sales for the following order tags: Specify which tag to pick when creating cash sales in NetSuite, use "," to differentiate between tags if more than one will be used. Use this options to create Cash Sales instead of Sales Orders in NetSuite for orders that have the specified tags. If no tag is entered, all order will enter NetSuite as Cash Sales.

2. Customer creation

   • Customer logic will happen alongside the creation of Sales Orders or Cash Sales. Several options are displayed. 

   • On the NetSuite ERP connector page, under the Settings tab, scroll down to NetSuite ERP settings > Customer creation logic. There, ensure settings to match your business needs:

     • Customer category: A separate configuration for customer logic needs to be created for each customer category considered. Two configurations are shown out of the box, D2C and B2B, if neither apply to your business, delete one and erase the value of the other or enter the values considered necessary. Consider category to be the naming of the different logics.

     •  Source and tags: Tags on the order can be used in this field to assign a provided logic. If the order is tagged on Pipe17 as "D2C", enter this value to apply a given logic. Use the pattern <source:tag> to specify a source along with a tag, use <source> if there is no tag. 

     • Customer subsidiary: Fill in the Subsidiary field with a specified value when looking up an existing customer or creating a new customer if it doesn't exist. If searching for an existing customer in NetSuite and two exist with the same email, it will select the default one, with the subsidiary preference.

     • Customer match: A unique selection regarding the behaviors of customer creation within NetSuite needs to be made. Depending on the choice, another setting called "Generic customer Id" will be displayed.

     • Generic customer Id: Depending on the choice made on the setting above, this field will be displayed. If required, enter the NetSuite internal ID of the customer selected to be the generic.

   • New settings can be created to enter required logic dependent on Customer category, Source and tags and customer subsidiary.

   • Use case: some selling channels such as Amazon FBA may mask the customer info when providing order data via API. In this case, a generic customer is often used when pushing the order to NetSuite. With high volume of orders, merchants often also use this generic customer method to simplify the data going to the ERP (and sometimes improve performance)

3. Pull Inventory from NetSuite

   • • Find the flow labeled "Pull inventory from NetSuite" and enable it. Also enable the locations pull flow - there needs to be a location created in Pipe17 representing the location before inventory can be pulled. View the specific settings in the inventory subsection below

       • Filter inventory pull based on: Usually, the filter is made to include a set of locations specified by Internal ID or by some other value within the location record in NetSuite.

       • Force inventory sync: Force pull inventory from NetSuite along with the locations. Please make sure 'Pull inventory from NetSuite' and 'Pull Locations from NetSuite' are enabled first.

    

4. Pull Fulfillments from NetSuite

   • On the NetSuite ERP connector page, under the Settings tab, scroll down to NetSuite ERP settings > Cash sales. There, ensure settings to match your business needs:

     • Item fulfillments filter: Request the Pipe17 team for support to create the logic required by your business to filter out Fulfillments pull. If filtered by location, use the field below.

     • Only pull Item Fulfillments from specified Locations: Enter NetSuite internal ID for locations. If blank, fulfillments will be pulled for all locations. Partial fulfillment is supported; meaning that if the Item fulfillment in NetSuite has multiple lines with different locations assigned, only the line whose location was specified will be pulled.

   • On the NetSuite ERP connector page, under the Mappings tab, ensure the correct field mapping is used. A baseline is provided automatically by the connector but all can be customized or removed.

   • New custom mappings can be requested and the Pipe17 team will provide support.

   • Some standard fields and custom fields may not be found on the SOAP order scheme or may not be reachable via API. 

   • Once settings and mappings have been validated turn on the connection flow on the settings tab.

5. Push Transfer Orders to NetSuite 

   • Make sure the 3PL location has an external location linked to NetSuite.

     • One way to do it is to pull location form NetSuite then merge it to a 3PL location; having locations pulled from NetSuite prior to TO push is recommended, but not required.

     • Other way is to manually add an external location on the 3PL location and link it to a specified NetSuite location.

   • On the NetSuite ERP connector page, under the Mappings tab, ensure the correct field mapping is used. A baseline is provided automatically by the connector but all can be customized or removed.

   • New custom mappings can be requested and the Pipe17 team will provide support.

   • Some standard fields and custom fields may not be found on the SOAP order scheme or may not be reachable via API. 

   • Once settings and mappings have been validated turn on the connection flow on the settings tab.

6. Push returns to NetSuite as Return Authorizations

   • On the NetSuite ERP connector page, under the Settings tab, scroll down to NetSuite ERP settings > Return authorization. There, ensure settings to match your business needs:

     • Close RMA in NetSuite once refunded: If this checkbox is enabled, the RMA will be closed in NetSuite once it has been refunded.

   • On the NetSuite ERP connector page, under the Mappings tab, ensure the correct field mapping is used. A baseline is provided automatically by the connector but all can be customized or removed.

   • New custom mappings can be requested and the Pipe17 team will provide support.

   • Some standard fields and custom fields may not be found on the SOAP order scheme or may not be reachable via API. 

   • Once settings and mappings have been validated turn on the connection flow on the settings tab.

7. Push eCommerce order refunds to NetSuite as Customer Refunds

   • Refunds have two possibilities to create differentiated records in NetSuite; Customer refunds or Cash Refunds.

   • If looking to create Customer refunds, on the NetSuite ERP connector page, under the Settings tab, scroll down to NetSuite ERP settings > Customer refunds. There, ensure settings to match your business needs

     • Create Customer Refund when order is canceled: Mark this checkbox to create a Customer Refund when the order gets canceled. The refund will be applied to the whole order. This use case applies to cancellations prior to order shipment.

     • Advanced settings for creating Customer Refund: Request the Pipe17 team for support to create advanced settings for Customer Refunds.

     • Mappings for creating Customer Refund: Request the Pipe17 team for support to create advanced mappings for Customer Refunds.

   • If looking to create Cash refunds, on the NetSuite ERP connector page, under the Settings tab, scroll down to NetSuite ERP settings > Order refunds. There, ensure settings to match your business needs

     • Advanced Settings for Order Refunds: We are creating Cash Refunds to refund fulfilled items, but you can specify refund type to create Cash Refunds when it’s not fulfillable. Request the Pipe17 team for support to create advanced settings for Order Refunds.

   • Once settings and mappings have been validated turn on the connection flow on the settings tab.

Mappings

1. On the NetSuite ERP connector page, under the Mappings tab, ensure the correct field mapping is used. A baseline is provided automatically by the connector but can be customized.

   • New custom mappings can be requested and the Pipe17 team will provide support.

     • Some standard fields and custom fields may not be found on the SOAP order schema or may not be reachable via API.