Connect NetSuite to Deliverr

This document contains instructions to configure and connect the NetSuite E-commerce connector with the Deliverr connector within Pipe17.

Note: There are two separate NetSuite connectors in Pipe17. The NetSuite E-commerce connector is to be used for this use case, which allows orders to be pulled from NetSuite and sent to Deliverr for fulfillment. 

In this article

• Getting Started
• Configure NetSuite & Deliverr
• Testing

Getting Started

• Pipe17 Account - Ensure that you have a Pipe17 account. If you do not yet have a Pipe17 account, book a demo with a Pipe17 team member to get started.
  Once your logged into your Pipe17 account, follow the steps below to add your NetSuite and Deliverr connectors.

Configure NetSuite & Deliverr

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 E-commerce 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. Sync products from NetSuite to Pipe17
   
   • Enable the settings called "Pull products to Pipe17 (full catalog sync)"
   • Products will begin to sync to Pipe17 and can be viewed from the Products tab in your portal
   • Products must exist in Pipe17 before orders can be sent to Deliverr
   • Note: Once the Deliverr connector is set up, any products in Pipe17 will sync to Deliverr. Use the "Product filter" setting in the NetSuite connector to filter to only the products you'd like to sync i.e. filter by product type/internal ID/subsidiary etc. Use the "?" icon to see all filtering options and formatting required to use these
3. Configure the Deliverr connector
   • See configuration steps HERE
   • Enable the setting for "Send Shipping Requests to Deliverr"
4. Validate the products link from Pipe17 > Deliverr
   • Products in Deliverr should show a Pipe17 alias corresponding to the matching SKU in Pipe17
5. Validate that inventory synced from Deliverr to Pipe17 successfully
   • Inventory should display correctly in the Pipe17 Inventory > All Inventory tab
   • Make sure to link the NetSuite location to the Deliverr location in the Inventory tab > Locations list. Do this by editing the Deliverr location and adding in the NetSuite location internal ID to the External Locations at the bottom
6. Set up order routing
   • If you would like to respect the location NetSuite has assigned to a Sales Order, then enable the setting by going to Integrations tab > Automations: Order Routing Engine > "Create Shipping Request for Pre Routed Orders/Items". This will automatically generate a shipping request to the linked location when an order is ingested to Pipe17 from NetSuite
   • If you would like to set up order routing rules in Pipe17 instead (and ignore the location provided by NetSuite), go to the <COMPANY NAME> tab > Order Routing and set up logic here for automatic order routing in Pipe17
7. Pull Sales Orders from NetSuite to Pipe17
   • Ensure correct field mapping is used so that Order ID and Order Source match up with original order from the selling channel. This is especially important if planning to leverage Deliverr Fast Tags. Go to the "Entities" tab of the connector and set the target fields "External Order ID" and "Order Source" like below:
     • 
     • Request help from Pipe17 if a custom field mapping is required:
     • 
   • Ensure correct shipping methods are setup in NetSuite & Deliverr. The shipping method will sync with the order from NetSuite to Pipe17 exactly as shown on the order in NetSuite. Deliverr has the option to set up a shipping method mapping in their portal.
   • Enable the setting in the NetSuite Ecommerce connector for "Pull Sales Orders to Pipe17" to allow orders to sync
   • Use the setting "Sales Order filter" to filter to just the orders you need to ingest from NetSuite to be fulfilled by Deliverr i.e. filter by location/status/subsidiary etc. Use the "?" icon to see all filtering options and formatting required to use these
   • Orders will sync to Pipe17 based on these settings, and automatically route to Deliverr if successful
8. Enable fulfillments to sync back to NetSuite
   • Enable the setting "Create Item Fulfillments in NetSuite from Pipe17 (3PL)" to allow fulfillments and tracking numbers to sync back to NetSuite once an order is fulfilled by Deliverr
9. Enable inventory to sync to NetSuite
   • Enable the setting "Push inventory updates to NetSuite" to create inventory adjustments in NetSuite to reflect any inventory differences shown in Deliverr.
   • Update the mapping to use your desired inventory adjustment account by going to the Entities tab > Entity: Inventory > Onto NetSuite E-commerce > Adjustment account section
     • 

Testing

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