
Writing after a long time, i planned to write this post after i started reading Jim McGaw’s “Begining e-commerce“, i liked the style of writing and things he has written on planning on building an e-commerce website. posting in excerpts about planning from the 1st chapter.
Building an E-commerce website is a very interesteing thing. An e-commerce project using any particular framework tends to be fairly complex, with lots of ins and outs. They allow you, as a developer, to start by building a simple product catalog, and then go deeper into hooking into third-party payment processors with web service calls.

Visual design for e-commerce tends to be pretty straightforward. Generally, you don’t need to create graphics-heavy grunge designs to wow your audience, like you might need to do for a blog or business-card web site. As far as e-commerce goes: the simpler and cleaner, the better. But still, please note taht design is a very important aspect of an e-commerce website. Customers and their purchasing decisions are very much influenced by the look and feel of a web site, so it’s well worth your time to learn a bit more about design and make sure that your site doesn’t turn customers off visually.
First, Before jumping right in and starting with the coding process, take a moment and write down on a paper about what it is that you want to create. It’s common practice for software developers to write a specification for larger projects before they start coding. There are few different kinds of specifications; the one that we’re going to do now is a functional specification, which will describe in plain English what our code is supposed to do. How you choose to write your own specification is not terribly important, but it is important that you write something, just to make sure that your ducks are in a row and you don’t run into unforeseen problems with your plans down the line. If you make any mistakes or run into problems, it’s much easier (and cheaper) to change a few lines of text on paper than change lots of written code.

A little example on writing a functional specfification for your e-commerce website:
“Pixels-n-Acoustics will be an online tore that sells Books, Music CD’s,music accessories, Movie CD’s & DVD’s, amazon kindle and smartphones. When the user first comes to the site, the home page will display some featured products, a list of categories, and search box that will let them search the catalog. Navigation will be straight across the top below the banner. Product lists should be thumbnails that include a small image of the product, with the product name. Products can be in as many categories as we want. We need to be able to add products and categories through a form so we don’t need to always have computer programmers doing it. These forms need to be protected so only authorized individuals can access them. Products can be added to a cart. Checkout will be a single page where we prompt customers for their information and let them submit the order to us. (How can we inform customers about our privacy policy? Make it always available to them?) We’re going to ship orders from our location where our retail shop currently does business. Search Engine Optimization (SEO) should always be a priority. Everything should be stored securely. Our site should be accessible to people with disabilities, such as blind people. How should we order products when several are listed on a single page, such as a category page? We need analytics to track conversions and figure out who’s buying what. The administrative login also needs a place for us to view orders. Orders can only be placed with a valid credit card on the site, and once the card is approved through a real-time lookup, the order can be submitted with a status of ”submitted.” Fulfillment will occur on our end, and we’ll set the status of the order to “processed” once they’ve been shipped. We need to handle returns easily. This will require the ability to refund a customer’s money, less any handling fees we might charge them. How can we make this information available to the customer? Where should we explain our return policy, during checkout? A hyperlink to a “Return Policy” page.”
The point is not to convince venture capitalists to fund us, but to figure out what we’re going to do, internally, by getting the mental juices flowing. It can be free-form. Crawl through the site you’re envisioning in your mind and jot down any thoughts or questions that come to you. Keep it around and add to it as ideas come to you. The more ideas you have in mind from the start, before you start building the thing, the less likely you are to forget something mission-critical and have to go back and redo a bunch of your work. For real business, you need to plan for growth, and a large part of that is starting your online application with a decent architecture that is your own, that you can later modify without limit, and that offers you benefits over your competitors. And if you happen to be entering a market where you have no competitors (what business are you in again?), then you either have a terrible idea (why is no one else doing it?), or you will end up with competition very quickly, especially if your venture meets with any success whatsoever. You want to be able to do things better than everyone else, and a key part of this lies in your technology.