Proposal For NetSuite To NetSuite Integration Between warroad and Touchstone using Celigo

Proposal Summary 

Touchstone Merchandise Group would like to Transfer the Transactions between the Touchstone NetSuite and Warroad NetSuite using Celigo. 

Requirement   

The requirement is to Transfer different Transactions between the Touchstone NetSuite account and the Warroad NetSuite account. 

Deliverables  

Prerequisites 

  • Access to Touchstone NetSuite account and Warroad NetSuite account. 
  • Access to Celigo integrator.io. 
  • Licence for six custom flows in Celigo integrator.io. 

Description of the task 

Here we are syncing different types of Transactions between two different NetSuite accounts.  

First need to setup connections of these two NetSuite accounts. We are using different custom flows to make the transferring of different transactions between Touchstone NetSuite account and Warroad NetSuite account. And all transactions require Mapping, this also will be different according to Transactions. 

Transactions/Records to be synced are: 

  • Sales Order [Warroad] to Sales Order (Web Order) [Touchstone] 
  • Item Fulfilments [Touchstone] to Item Fulfilments [Warroad] 
  • Purchase Order [Warroad] to Purchase Order [Touchstone] 
  • Item Receipt [Touchstone] to Item Receipt [Warroad]  
  • Item [Warroad] to Item [Touchstone] 
  • Inventory Adjustment [Touchstone] to Inventory Adjustment [Touchstone] 

Sales Order (Warroad to Touchstone) 

The Sales order can be exported from Warroad NetSuite and imported to Touchstone NetSuite. The NetSuite Sales Orders from Warroad that must be synced to Touchstone can be identified by a field “Export to Touchstone” of type Checkbox. Only if this field is checked the exporting will take place. Based on this field we can prevent duplicate transactions. 

We are using two different default customers in Touchstone NetSuite for the Shopify and Elastic orders created in the Warroad NetSuite.  

  • 65 Warroad Shopify Orders is the Warroad Customer, customer corresponding to this in Touchstone is 10035 Warroad Online Orders. 
  • Elastic has individual customer in Warroad while Customer corresponding to elastic orders in Touchstone is 35918 Warroad – Wholesale Orders. 

We will be using default Location as Mason: Main Warehouse 

Need to confirm the identifier in Warroad to identify the orders from Elastic. 

NOTE: 

  •  Only One-Way Syncing is considered. 
  • We will be using Item Name/SKU as the identifier. 
  • Updates made to the Warroad sales order will not be synced. 
  • Sales Order Form considered is: TMG – Inventory Purchase Order 

Item Fulfilments (Touchstone to Warroad) 

Corresponding to the sales order created in Touchstone, Item Fulfilment will create in Touchstone and this created Item Fulfilment should import to Warroad. For doing this we need to use a Unique Identifier. Etail Order ID is a field usually taken by Celigo as a unique identifier, so we can’t use this as the identifier because this will cause conflict. In this case, we will be placing “Internal Id” from Warroad Sales Order in a custom field in Touchstone Sales Order and this field can be used as an identifier of fulfilments.  

NOTE: 

  • Only one-way sync is considered. 
  • Partial fulfilments are also considered. 

Purchase Order (Warroad to Touchstone) 

The Purchase order can be exported from Warroad NetSuite and imported to Touchstone NetSuite. Here we will be using default vendor as Touchstone Merchandise Group. The NetSuite Purchase Orders from Warroad that must be synced to Touchstone can be identified by a field “Export to Touchstone”. The location to be taken to consideration is not confirmed. 

NOTE: 

  • Purchase Order Form considered is: TMG – Inventory Purchase Order 
  • Updates made to the Warroad purchase order will not be synced. 
  • Only One-Way Syncing is considered. 

Item Receipt (Touchstone to Warroad) 

When the product received in Touchstone manually create the Item Receipt corresponding to that in Touchstone and transfer that created Item Receipt to Warroad.   Need to identify the synced POs from Warroad by using a custom field as unique identifier and according to this Item Receipt must be created. 

NOTE: 

  • Only One-Way Syncing is considered. 
  • Will consider partial receipt scenarios also. 
  • Will not consider any manual updations to the purchase order created. 

Item (Warroad to Touchstone) 
 

Items from Warroad can be synced to Touchstone.  Only the Item creation is considered in this sync. Updates made to Warroad Item will not be synced to Touch Stone. Once synced a custom field will be marked in Warroad Item which will prevent it from syncing again. 

NOTE: 

  • Only One-Way Syncing is considered. 
  • Only Inventory Items are considered in the integration. 
  • Quantity will not be synced. 
  • We assume existing items in Warroad and Touch Stone are already in sync, hence the integration will consider new items only. 

Inventory Adjustment (Touchstone to Warroad) 

Touchstone Inventory Adjustments for items will need to be mirrored in Warroad. We need to use an identifier to identify the required Inventory adjustments. Updates made to the Inventory adjustment once synced will not be synced again to Warroad. The location to be considered is to be confirmed. 

NOTE: 

  • Only One-Way Syncing is considered. 
  • Only Inventory Items are considered in the integration. 
  • Item Name/SKU will be used as the unique identifier. 
  • We assume existing items in Warroad and Touch Stone are already in sync. 

Assumptions 

  • Items available in Warroad will be available in Touchtone, also Vise-versa. So, we are considering Item Name as the identifier. 
  • We will be using preferred FORM in the case of Inventory Adjustments, Item Fulfilment, Item record, Item receipt. 
  • Field mapping can be confirmed during Development phase. 
  • All the mentioned integrations are one- way
  • All the integrations will run in Schedule
  • No real-time sync is included. 
  • The integration will be first implemented between Warroad NetSuite Production and Touchstone NetSuite Sandbox. 

Leave a comment

Your email address will not be published. Required fields are marked *