Practical Ecommerce

App Development Trends Favor Custom Ecommerce Platforms

Frameworks such as Laravel greatly reduce the time to develop applications, making custom ecommerce platforms more economically feasible.

Frameworks such as Laravel greatly reduce the time to develop applications, making custom ecommerce platforms more economically feasible.

Application development is changing. Frameworks, services, and even tools make it possible to rapidly create web and mobile applications custom to a business’s needs. These changes mean that it may make sense for some large and mid-sized ecommerce businesses to build their own custom platforms rather than using “off the shelf” ecommerce solutions.

The question of whether to build a software application or buy a solution — or lease, if you will, in the case of software as a service (SaaS) — is common to almost any modern business, including ecommerce. Making the decision to create an application versus purchasing one requires weighing many factors, and at the moment, the aforementioned development trends could be tipping toward building an ecommerce platform rather than using one off of the shelf.

Build-versus-buy Analysis

If you searched on Google or Bing for “build versus buy,” you’d find no shortage of articles intended to help businesses think through the build-versus-buy decision. Often, these articles will include lists of common build-versus-buy pros and cons.

Building your own application should:

  • Provide just the features you need;
  • Integrate better with your other systems and operations;
  • Allow for better third-party integrations;
  • Provide better performance (faster loading pages for example);
  • Better represent your brand;
  • Provide a competitive advantage.

The cons for building your own application are typically:

  • More expensive;
  • Longer to implement;
  • Need a much larger staff.

In the ecommerce industry, retailers almost always choose to buy. These companies add to the list of potential cons, citing things like Payment Card Industry (PCI) standards or the need to comply with accessibility requirements. I’ll address these cons.

Building an Ecommerce Platform Can be Less Expensive

When you are considering the cost of building versus buying an ecommerce platform, it is difficult to compete with SaaS services like Shopify and Volusion that offer solutions ranging from less than $10 per month to just a few hundred.

With this in mind, small ecommerce businesses should almost always select this sort of solution, at least for now. As an ecommerce business grows, becomes more complex, and starts to sell through additional channels, that business will often need to turn to “enterprise” ecommerce platforms.

On the low end, you can license an enterprise ecommerce platform like Magento Enterprise Edition for, perhaps, $15,000 to $20,000 per year. You’ll have integration expenses, maintenance costs, product support fees, hosting bills, and database services to pay, too. So your annual expenses will be, maybe, $40,000 to $45,000 for a solid solution.

Solutions as good as SAP Hybris might cost $50,000 or more to license, and annual expenses could easily reach $100,000 or more.

These enterprise ecommerce solutions are said to cost less than building a proprietary solution because many companies assume they will need to pay a team of developers for several months to create the custom solution in the first place, plus keep more developers on hand to maintain it. But this may not be true.

Consider for a moment the emergence of modern application develop frameworks. These frameworks provide a foundation for almost all of an application’s basic features and functions, so that building your own ecommerce solution is not really starting from scratch. It is, rather, like standing on the shoulders of giants.

Take the case of Laravel, a PHP framework. Laravel is built to make the most common application features easy to implement. Need database connections? It’s pretty much done for you with Laravel. Need user management and authentication? The basics are built in with Laravel. Want a way to email order information or shipping notifications? Laravel provides a simple API for Swift Mailer, plus drivers for SMTP, Mailgun, Mandrill (a MailChimp service), and Amazon Simple Email Service.

If this is not enough of a boost, Laravel has a $99 add-on (a “scaffold,” in code-speak) called Spark that includes subscription billing using Stripe or Braintree. The difference in code between taking monthly or yearly subscriptions and processing single orders is small. With Spark providing the code to take payments, it will be a yawn. And with a service like Braintree or Stripe, PCI compliance is relatively easy, too.

Put simply, it may be possible to build a custom ecommerce platform using Laravel in about the same time it would take to integrate an off-the-shelf enterprise solution. There should not be a large development bill.

Once the site is up and running, there will be no licensing fees. Hosting the site on Amazon Web Services or DigitalOcean could run up to $1,000 per month.

So, if your new Laravel-based ecommerce solution costs $20,000 a year to host, you could spend, perhaps, $20,000 in initial development and still be investing about the same amount (approximately $40,000) as your first year on a low-end enterprise ecommerce platform.

Put simply, it may be possible to build a custom ecommerce platform using Laravel in about the same time it would take to integrate an off-the-shelf enterprise solution.

This is hypothetical. You would want to look carefully at your own situation. But frameworks like Laravel might mean that developing your own solution is less expensive than you think.

Building a Solution Might be Faster to Implement

A second concern about building a solution versus buying one is that the former might take significantly longer to implement. But this too, may not be true.

Just a few years ago, a developer would have needed to write significantly more code to get a custom solution up and running.

Back then, it did not make sense to write your own content management system, because WordPress just worked. It did not make sense to write your own email system, because MailChimp, MailUp, and Constant Contact just worked. And it did not make sense to write your own ecommerce platform because SAP Hybris or IBM WebSphere Commerce just worked. So why invest the time?

But, again, development has become easier and faster. Here’s an example. If you wanted to have interactivity on your ecommerce site a few years ago, you would probably use a JavaScript library like jQuery. As helpful as jQuery was and is, newer JavaScript frameworks have revolutionized application development. For example, Vue.js and its resources extension make data binding (syncing data with the application) and AJAX simple.

What’s more, there are many services that you can integrate with your custom ecommerce platform to further save time.

A brick-and-click retailer in the northwestern United States, as an example, implemented a high-end, enterprise search solution in 2015. The company spent more than $24,000 in fees and took nearly 90 days to get the service up and running. It worked well.

Then in the fall, one of the company’s developers connected a bit of custom code to Algolia search. The result was a solution just as functional as the high-end search, and it took just two hours to implement.

If this same retailer wanted a custom ecommerce platform, it could use Algolia to provide the search.

How long it takes to build your ecommerce platform will depend on your requirements. But building need not take much longer, if any longer, than implementing someone else’s solution.

Custom Ecommerce Platform Might be Easy to Maintain

The next common con for building your own solution is that you will need to hire extra developers and system administrators to maintain it. But, once again, this may not be true.

Infrastructure as a service has become popular. There are a number of tools designed to help you maintain your servers and your code.

Laravel has a service called Forge designed specifically to help a small team or even a single developer host applications on Amazon Web Services, DigitalOcean, and Linode.

IBM’s Compose makes setting up and accessing databases like MongoDB or Redis as easy as using a web app.

In the end, you may need to have a developer or system administrator, but maintaining your custom application does not have to be a huge burden,. Relative to some enterprise ecommerce solutions, it may still be less expensive.

Summing Up

The build-versus-buy analysis is not going away. The balance may soon swing one way or the other. But at the moment, web application developers have many frameworks, services, and tools that make it feasible to build a custom ecommerce platform.

These tools, services, and frameworks may marginalize some ecommerce platforms — those that are overpriced or under performing. It is a golden age for application development. It could be a good time to consider whether building makes sense for your ecommerce operation.

Armando Roggio

Armando Roggio

Bio   •   RSS Feed


Sign up for our email newsletter

  1. Alfred Beiley May 2, 2016 Reply

    Fully comprehended the article. It was worth reading to know about the latest fluctuations in Ecommerce and app development. The only doubt is that I still feel that building cost-effective, easy to maintain and faster to implement altogether is irrational, is it?

    • Armando Roggio May 2, 2016 Reply

      I think it is very reasonable. Give it a try. See how quickly you can have a site up and running with Laravel. I’ll bet you will be surprised.

  2. @clarkchambers May 2, 2016 Reply

    Great article Armando. Nice to see the deeper end of ecommerce explored on Practical Ecommerce.

    Bespoke ecommerce also comes with the benefit of keeping your ecommerce apart from your content. Decoupling the two means changing CMS/frameworks doesn’t have to affect ecommerce machine you’ve optimized. Keeping your content + inventory systems upgradable.

  3. Nitin Srivastava May 3, 2016 Reply

    I am a big fan of your writing Armando but on this one I do not agree with. It looks like advertisement of Laravel :) Don’t take it otherwise.

    Comparing off the shelf solution with custom built one as taking the same time is not actually true.
    Custom code development will always take more time than using an off the shelf eCommerce solution. My reasons are as follows:
    a) It takes time to define the db structure and properly audit it to make sure there isn’t anything wrong with it. In case it is wrong, your entire system is going to crumble.
    b) Just because few addons are available for Laravel, does not make it an awesome platform for development. CakePHP and Symfony have a much bigger user base and far many more addons.
    c) The entire conceptualization of the eCommerce solution is not a child’s play. It takes time to build one and needs very experienced minds. Getting them can be difficult as well as costly.
    d) No matter which framework do you use, Laravel, Symfpony, or CakePHP you will still have to code and test. Testing means repeat testing of each module after changes and then integration testing and so on.
    e) Moreover, if you build a custom solution you are dependent on the developer who wrote that software, in case it has been written poorly, anyone else will have hard time supporting it. Open Source solutions or even proprietry solutions for reputed companies always provide you with a bigger developer pool to choose from.
    f) New releases, bug fixes, efficiency improvement, all this comes free with off the shelf eCommerce solutions and they are going to be missing with custom developed solution.

    Custom developed solutions will cost 5-10 times more than off-the-shelf eCommerce solutions.

  4. John Contarino May 3, 2016 Reply

    Excellent article, lots of good advice and helpful links.

    As someone who built my own eCommerce framework, I much prefer custom solutions for my clients. I can give them precisely the functionality we need today with room to grow for tomorrow.

    While solutions like Shopify are good out of the box, you have to remember you are stuck in a one-size fits all box! With a custom-built solution, you can do anything you want in terms of design and functionality very quickly.

  5. Tom Bowen May 6, 2016 Reply

    Great post (as always) Armando. I’ve found that perhaps the biggest advantage to “build” is that the resulting tool is easier to use. Since it’s not built for the masses, it is designed straight to your needs (which you said), but a big result of that is that it becomes much easier to use because all that other unused stuff is not there. You’re not presented with a control panel for an airplane when all you need to do is drive a car.

    Good article.

  6. Stefy Biber May 12, 2016 Reply

    Nice post to read as an app developer. I have developed a number of apps with the help of various cross platform mobile app development platforms.

    I want to suggest the author as well as all the developers, an another app development platform, Configure.IT . Just try this one, you will not regret for sure. This is my personal view, I have developed plenty of apps with this platform, so I recommend this tool to everyone.

    The unique features are,

    => Cross Platform Native App Development Tool

    => No Coding required, just drag & drop

    => Direct API Connect

    => No need to design UI, you can import .PSD file directly for UI Purpose

    => A large numbers of templates to choose an attractive design

    To know a list of other features visit,

    Review this platform once, I am sure you will forget all other platform, same happen to me as well.

  7. Robert Mills October 10, 2016 Reply

    Cool article. Thanks. Let me share an excellent tool that will help your to get calculated costs for development of your mobile application