eCommerce Scenario–guide to the overall eCommerce landscape

eCommerce implementation are complex and each implementation has it’s own uniqueness. That said, like any other technology stack implementation, these implementation too can be broadly classified based on commonalities that exist amongst them. These commonalities are based on the scenarios that these implementation cater to and can be looked at from various perspectives like the scale of implementation, target audience, market needs, distinguishing feature sets and so on.

This classification help not only serves as your big picture that’ll help understand the overall eCommerce landscape, they also serves as a your guide thought the various phases of your project. These patterns are also directly or indirectly targeting by software vendors. So whether you’re only looking to understand the overall eCommerce landscape or making a decision in eCommerce space, it is important for you to understand these scenarios. Do remember thought that most eCommerce storefront implement a combination of at least two of these scenarios with some degree of variation.

  1. Simple Shopping CartThis is the simplest form of an eCommerce site that primarily involves implementing a shopping cart functionality that will allow customers to place orders and make payments online. This scenario is characterized by websites that typically comprise of by static web pages offering information about the merchant’s product and services. The number of products offered in this scenarios are very small, ranging from a just a couple to may be 20-30 on the higher side. The products and services information is fairly static and doesn’t change frequently. Customer experience and user interface is often neglected in these sites and is a common scenario implemented by individual sellers, small companies; NGO’s whose paramount objective is merely to enable their customer to place orders online. Other eCommerce functions like stock management, order management, fulfillment are managed offline and manually.
  2. Boutique eCommerceMost commonly implemented scenario by boutique companies, manufacturers, small retailers who are serious about eCommerce. While the online storefront may not generate significant revenue for them, it is an important part of their brand and customer retention strategy. These storefronts complement the merchant’s brick and mortar stores, and gives its customers an option to place orders or replenish their supplies online. Consistent user experiences across the store and online storefront is important to this scenario. This scenario is characterized by rich, inutile user interface; broad but shallow feature eCommerce sets, limited external system integrations and semi-automated process . The eCommerce solutions implemented in this scenario may not always meet business requirements; business may adopt to out of box implementation to a larger extent as significant development would be an expensive proposition. The number of product ranges from a couple to a few hundred.Small and medium enterprises that are new to eCommerce, often adopt this scenario to serve as a cost effective, and easy to manage testing ground.

There’s more.. If you are interested in reading the complete report, you can request the same for a nominal fee of $50.

This entry was posted in eCommerce and tagged , , , , , , , . Bookmark the permalink.

4 Responses to eCommerce Scenario–guide to the overall eCommerce landscape

  1. Jonathan says:

    Sanjeev
    Could I get a copy of the full post/document?
    Thanks
    jonathan

  2. gaurav pranesh says:

    This is very interesting to learn about e commerce , could you please mail me a copy.

  3. Santosh says:

    Hi Sanjeev,
    Article looks really good. Please could you mail me full article to know more about ecommerce domain.

    Cheers,
    Santosh

  4. Ariel Jalali says:

    Hi Sandeep

    I am trying to compare enterprise level e-commerce sites.
    Saw your discussion on LinkedIN and would like to see your perspective in your white paper.

    Thanks and best regards,

    Ariel

Leave a Reply

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

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>