Integrating Ecommerce with NetSuite can involve a large amount of development resources, it is important to set realistic expectations and goals at the outset if you are to achieve a viable, robust integration.
In addition, a number of technical and business considerations need to be taken into account when choosing a technology stack most appropriate for this type of integration.
In this post I have provided an overview the most common messages exchanged and the development effort likely to be associated with these messages.
I have also presented a high level overview of three technology stacks / architectures you might choose to employ during this type of integration.
Messages and level of development effort requied
|Stock update||2 days||Involves setting up and testing a stock file integration between NetSuite and the external Ecommerce Platform.|
|Full Catalogue Data Integration (not including categorisation)||7 days – estimated – requires evaluation||Some investigation is required, certain product configurations in the Ecommerce Platform in NetSuite or the ecommerce platform may cause issues.|
|Category Integration||4 days – estimated – requires evaluation|
|Discounts||Based on specifics of the project.||Differences between discounting methods with NetSuite and the chosen ecommerce platform can make integrating this area problematic|
|Customer specific Products / pricing||Based on specifics of the project.||This area can be problematic. We usually recommend considering a rebuild using SuiteCommerce where integration of customer specific pricing is required.|
|Orders||2 days||One way integration, sending orders from the Ecommerce site to NetSuite.|
|Shipping confirmations||2 days||Send shipping confirmations from NetSuite to the Ecommerce Platform|
|Credit notes / refunds||Based on specifics of the project.||Investigate payment gateway integration / if tokenisation has been implemented / customers can be refunded via the site.|
Three viable architectures for integration are as follows:
|Technology stack||Senario integration is usually used in|
| Middleware Queue based messaging middleware – EG Rabbit MQ / Dell Boomi / Mulesoft
|Integration is required between a software as a service ecommerce platform and NetSuite.Company completing the integration are not the owner of the software as a service platform.For example, we have used this approach to integrate a number of Shopify Webstores with NetSuite.|
| FTP Based Message Queue + RestletsFTP Server with file based queue
|Integration is between NetSuite and an open source installed Ecommerce Platform such as Magento.This is the most common approach taken in practice due to the popularity of Magento and the availablity of low cost development resource who understand how to get information from an FTP based file queue in / out of Magento.|
| Direct Integration with NetSuite Queuing RestletsCustom Record based queue in NetSuite
|Recommended if a software as a service Ecommerce platform is to be integrated with NetSuite and the work is being carried out by the owner of the platform.|
Queue based messaging middleware – EG Rabbit MQ / Dell Boomi / Mulesoft
Integration is required between a software as a service ecommerce platform and NetSuite.
Company completing the integration are a third party and plan to have a large number of integrated ecommerce customers.
Direct Integration with NetSuite Queuing – Restlets – Custom Record based queue in NetSuite
Recommended if a software as a service Ecommerce platform is to be integrated with NetSuite and the work is being carried out by the owner of the platform.