Custom plugin vs Generic plugin,
Which one should you opt for!
Retailers today have multiple options of infusing technologies with their ecommerce setup to super build the interaction and personalization capabilities on their online shops. Plugins have become an integral part to serve this requirement of retailers. And without Question Providing plugin for their own technologies has become one of the major aspects as a technology provider.
However with this new requirement comes the chaos of focus. Focus on technology or, focus on building plugins, focus on plugin for each client or a scalable generic plugin?
Let’s dig in to find out how we at Ideatarmac address this issue.
Before we present our perspective lets take a quick peak into pros and cons of each. Below listed are the main factors that will help you prepare better.
|Custom( client specific) plugin
|Client specific plugins are usually faster to build and cheaper as you can avoid all costly characteristics such as configurable features, address several use cases or its performance scalability.
|This approach might take longer time as compared to a client specific plugin.
|Working with a Solution provider of this merchant who understands this client very well, hence adoptability of plugin for this specific client will be easier. It can be built by a team or developer who is already familiar with this merchant’s specific environment. This can make the installation and usage of the plugin smoother.
|This plugin can be built by anyone who understands the solutions to integrate.
|The investment done in this plugin cant be reused as architecture will not support reusability
|A plugin that can work for majority of the users of this shop system with little customization needed for different client is an alternative.
|Time to onboard further clients will be same or longer compared to the first plugin
|Faster to onboard and better ROI on longer term as the architecture supports reusability of most of the code written for first client.
|Any updates version changes and upgrades needs to be done separately for all clients.
|Management of such a plugin is easier and cheaper as there are fewer places to be updated for changes such as API updates.
|No scalability and limited reusability
Danger of missing on lots of use cases or not being scalable leading to rewriting the plugin from scratch again
|Performance and scalability are usually better addressed in this option since you approach the integration architecture more strategically as compared to addressing one use case.
Reusability of the code even for different Shop systems is possible, in case they share same set of technological stack.
|Lesser risk as you may or may not acquire more clients on this shop system
|This approach ensures that there is a clear demarcation between the product and individual customizations required for each integration into merchants. Therefore, it is easy to use this plugin at scale for 100s of merchant
|Fastest, easiest and cheapest solution if this integration is one off and there is no plan to actively acquire new clients on this shop system.
|Still needs long term interest in the shop system.
This approach might take longer time for the first time as compared to a client specific plugin.
|Working with a Solution provider of this merchant who understands this client very well so adoptability of this plugin for this specific client will be easier.
|A plugin that can work for majority of the users of this shop system with little customization needed for each specific client is an alternative.
Hence as always, It is all about the strategic direction organization wants to take response to a shop system. Speaking from experience, if you are looking to build a plugin for a shop system that does not fit into your strategic plans then a custom or, client specific plugin may be a faster and cheaper way. However, if there is even a plan to have 2nd or 3rd client then a generic plugin is always a better option.
Ideatarmac’s SDK-MVP Approach
At Ideatarmac, we have worked on both approaches. But after building 100s of plugins, we usually recommend going for generic plugins because of its strategic edge. We call it SDK approach.
Based on our broad range of project experience, we recommend that these integrations do not need to address all use cases right from the beginning, therefore, it is wise to consider the first version of an integration as Minimum Viable Product(MVP). Ideatarmac has built an approach that is a mix of SDK approach and MVP approach. This approach delivers a generic plugin in a very short time.
Ideatarmac’s shop system integration products for technology vendors
Below are our products for you to integrate into multiple shop systems by utilizing our above SDK-MVP approach:
Universal Payment Adapter: is an Ideatarmac ‘s licensed B2B, B2C solution software is integrated within few hours to few days.The software connects as a plugin between more than 10 Shopsystem and different payment options. This effortless and agile solution is also future ready and reduces 70% of effort when compared to individual management of Payment service providers.
This solution is complemented by our services to build plugins that scale and adhere to the particular shop system’s requirements. Thus bringing these plugins into app marketplaces bringing visibility across thousands of merchants. We then provide post launch maintenance to ensure smooth onboarding of clients.
Our vision of a simplified solution is encompassed with a seamless operation for a successful eCommerce business. The software is regularly updated and improved by our team of experts.
eCommerce Data Connector: is Ideatarmac’s solution for data integration which is a cloud-based technology. We provide an integration solution that eases the business by refining, transforming and publishing of relevant data among the Shopsystem.
We remove the complexity by providing clear visibility and performance. With the Ideology “Connect Once and Publish everywhere’’ we aim at making your integration a lot simpler and reducing the effort by 70%.
There are other products and services like Shopify Akeneo connector and SFCC PDO (SFCC Cartridge development) services. Do get in touch if you have questions or need further information.