Skip to main content

Getting Started with NetSuite ERP

In this article

Overview

  • The NetSuite ERP connector is primarily used when you are pushing orders from Pipe17 to NetSuite

  • Supported flows:
    • Push Orders to NetSuite
    • Pull Inventory from NetSuite
    • Pull Fulfillments from NetSuite 
    • Push Transfer Orders to NetSuite 
    • Push returns to NetSuite as Return Authorizations
    • Push eCommerce order refunds to NetSuite as Customer Refunds
  • Note: there is another connector called NetSuite E-commerce, which is primarily used to pull orders from NetSuite INTO Pipe17 to be sent to fulfillment channel(s). This is not the subject of this article.
    • Supported flows of the NetSuite eCommerce connector:
      • Pull Sales Orders or Item Fulfillments from NetSuite
      • Push Item Fulfillments to NetSuite from fulfillment channels
      • Pull Product catalog from NetSuite
      • Push Inventory to NetSuite
      • Pull Locations from NetSuite
  • Flow Example - NetSuite ERP:mceclip2.png
  • Flow Example - NetSuite eCommerce:mceclip0.png

Getting Started

  • First, sign up for a Pipe17 account if you haven't already done so. Create an account here: SIGNUP
  • Make sure you are licensed to use the Pipe17 NetSuite ERP Connector. If you're not certain, reach out to your Pipe17 onboarding contact or our sales team to ensure you are ready to begin setup.
  • Once your account is created and you are logged in, follow the steps below to add your connectors.

Configure NetSuite & Fulfillment Channel

  1. Add the NetSuite connector
    • Go to the "Integrations" tab on the left side of your Pipe17 portal, and click "Add Integration"
    • Select the NetSuite ERP connector
    • Input your credentials (follow the steps HERE)
    • Once credentials are successfully entered, and the connector status shows "Connected" click over to the "Settings" tab within the connector. Step through the numbered steps below 
  2. Push Orders to NetSuite
    • On the NetSuite ERP connector page, under the Settings tab, scroll down to NetSuite ERP settings > Sales orders. There, ensure settings to match your business needs:
      • Only push orders when source channel is: Enter the source channel(s) allowed to create orders in NetSuite i.e. fabric, amazonfbm, amazonfba, bigcommerce, shopify. If the channel is not included on the list, you can pull in an order from the desired channel and view the source value on the Orders > All Orders page in the 'Source' column. The value used here must exactly match the value shown on the Orders list page. If not used, no filter for source channel will be used, meaning orders from all channels will be pushed.
      • Push orders to NetSuite when Pipe17 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 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.
         
      • Allow order updates to sync 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.
      • Push order updates to NetSuite 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.
      • Identify products on orders by: Choose the value that matches the product shown on the order in the sales channel. If the sales channel uses a SKU that matches to the Item Name/Number field in NetSuite, choose Item Name/Number. If the sales channel uses the UPC value in NetSuite, choose UPC.
      • 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.
    • 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. 
    • Once settings and mappings have been validated turn on the connection flow on the settings tab.
  3. Customer management
    • 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.
  4. Cash sales preferences
    • 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:
      • If required to push cash sales instead of Sales orders in NetSuite, use the checkbox called "Create cash sales in NetSuite"
        • This checkbox reuses the setup logic created previously for sales order regarding source channels, Pipe17 statuses, updates, product identification and customer management, 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.
  5. Pull Inventory from NetSuite
      • On the NetSuite ERP connector page, under the Settings tab, scroll down to NetSuite ERP settings > Inventory. There, ensure settings to match your business needs
        • Filter inventory pull based on: Request the Pipe17 team for support to create the logic required by your business to filter out inventory pull. 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.
        • Pull Locations from NetSuite: Check this box to enable the creation of NetSuite locations in Pipe17.
        • Filter location full based on: Request the Pipe17 team for support to create the logic required by your business to filter out location pull. 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.
      • Once settings have been validated turn on the connection flow on the settings tab.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.

Have more questions?
Submit a request
Share it, if you like it.