Proposal summary

This proposal details how the integration between NetSuite and Castlelan for the purpose of Extended Warranty registration

Requirement 

We need to register a warranty sold by Rightworx at the point that the Sales Order is FULFILLED.

The current Sales Order Process is

1. Sales Order Entered (manually or via Website)
2. Payment Taken (which approves SalesOrder)
3. Drop Ship POs raised.
4. Sales Order Invoiced
5. Raising an Invoice creates an “Extended Warranty Record”.

When the Sales Order is Fulfilled, the Extended Warranty needs to be “registered” with the supplier via an API (attached), and the warranty reference number returned to Netsuite.

Initially, we are looking at sending over the following information – but this could be expanded.

• Client ID (static information)
• Client Key (static information)
• Sales Order Number  – Stored on the Extended Warranty Record custrecord_nbs547_salesorder}
• Start Date – Stored on the Extended Warranty Record {custrecord_nbs547_date}
• End Dates – Stored on the Extended Warranty Record {custrecord_nbs547_expirydate }
• Deal Code  – Stored on the Extended Warranty Record {custrecord_bs_warranty_deal}
• Delivery Date – from the Sales Order Link on the Extended Warranty record
• Customer First / last name – From the Customer link
• Products – Stored on the Extended Warranty Record (but the way this is stored may need to be altered).{ custrecord_nbs_item_array }
• Phone – Stored on the Extended Warranty Record {custrecord_nbs_warranty_phone}
• Mobile Phone – Stored on the Extended Warranty Record {custrecord_nbs_mobile_phone}
• Email – Stored on the Extended Warranty Record {custrecord_nbs_warranty_email}
• Address – It looks like we may have to split the address in lines {custrecord_nbs_address }

I do not think that the API is quite ready yet, it is new, so it may be a few weeks before we can test it.

Solution

• We will deploy a WorkFlow on the  ‘Extended Warranty Registration’ custom record. When all the required fields are populated in the custom record, this will trigger the state named ‘Castelan Integration’
  • All the field values will be on the ‘Extended Warranty Registration’ custom record. 
  • For the item, consider all the items in the Sales Order which are Inventory Item with the Item Type as ‘Furniture’.
    This information will be sent to Castlean

Assumptions

• A single Sales Order can have multiple Item Fulfillment and Invoices or advance billing.
  Whatever the case may be, the Item under consideration for Castelan Warranty Integration will be all the line items in Sales Order (referred in the ‘Extended Warranty Registration’ custom record) which is an Inventory Item with the Item Type as ‘Furniture’
• Only the required field value and address (shipping address) will be sent to Castelan Warranty Integration
• The solution will be developed till the creation of data in the required JSON format for Castelan Warranty Integration API.
  The actual API implementation is done when the API is made available by Castelan and the changes need to be updated in the solution.
• An extra field will be added to the custom record to store the status of the API.
  This will be helpful in case the API failed due to some reasons

Time

14 hrs