<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Ecommerce Experiment &#187; ecommerce development</title>
	<atom:link href="http://www.ecommerceexperiment.com/tag/ecommerce-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ecommerceexperiment.com</link>
	<description>Detailing an ecommerce startup from scratch!</description>
	<lastBuildDate>Thu, 08 Jul 2010 13:28:38 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How to choose a web developer?</title>
		<link>http://www.ecommerceexperiment.com/2009/06/16/how-to-choose-a-web-developer/</link>
		<comments>http://www.ecommerceexperiment.com/2009/06/16/how-to-choose-a-web-developer/#comments</comments>
		<pubDate>Tue, 16 Jun 2009 09:55:58 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[ecommerce]]></category>
		<category><![CDATA[ecommerce development]]></category>
		<category><![CDATA[web]]></category>
		<category><![CDATA[web development]]></category>

		<guid isPermaLink="false">http://www.ecommerceexperiment.com/?p=198</guid>
		<description><![CDATA[We are lucky to already have a web developer on board for this project (me  ), but if we didn&#8217;t have this experience in house, then we would need to look elsewhere. Choosing a web developer will depend quite heavily on your budget, expectations and the scale of your operation.
Once you know what your [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="margin-top: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.ecommerceexperiment.com%2F2009%2F06%2F16%2Fhow-to-choose-a-web-developer%2F"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.ecommerceexperiment.com%2F2009%2F06%2F16%2Fhow-to-choose-a-web-developer%2F" height="61" width="51" /></a></div><p>We are lucky to already have a web developer on board for this project (me <img src='http://www.ecommerceexperiment.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> ), but if we didn&#8217;t have this experience in house, then we would need to look elsewhere. Choosing a web developer will depend quite heavily on your budget, expectations and the scale of your operation.</p>
<p>Once you know what your budget is, what you expect/what from the web developer and you know just how big the site will be, and then you will need to go out and find a web developer. This could be anyone from a freelancer, to a small web company, to a much larger web company, and this decision mostly will depend on your budget. Most importantly you need to be sure that the developer you choose is capable of handling the work and will be able to help you grow.</p>
<p>Here are our guidelines for how we feel a company or individual should go about looking for someone to develop their new eCommerce site.</p>
<ol>
<li> Work out a realistic budget for what you would like to spend on the development work</li>
<li> Work out what your expectations/requirements for the web developer are. (This could be anything from custom stock integration to a specific payment provider).</li>
<li> Determine how big your site will be (in terms of products and visitors), as this will determine the right software and systems to use for your site.</li>
</ol>
<p>After this, you should have a good idea in your mind of what sort of web developer you require. When choosing between a freelancer, a small company or a large company, it is necessary to keep in mind your requirements now, but also your future requirements:</p>
<p>A freelancer would be an ideal low cost solution initially, however as your company grows and the workload increases, it may lead to them having to pass the work onto a small company in order to better facilitate your requirements. By this I mean that they might not have the current capacity to handle your increasing workload and they may not want to grow larger than being just freelance.</p>
<p>A large company would be a very expensive solution initially, but they would be able to handle the growth and would <strong>possibly</strong> have more experience in dealing with large projects and be able to help you grow your business quickly in a well thought out manner.</p>
<p>A small company would not be the cheapest solution, but they would also bring to the table the capacity to grow alongside your new ecommerce business.</p>
<p>Once you have these sorted out, you need to then choose a web developer, it is best to approach a number of different companies/people and get quotes from all three.</p>
<ul class="unIndentedList">
<li> Ask to see examples of their previous work.</li>
<li> Ask if you can speak to some of their current clients to see what they think.</li>
<li> Ask them what makes them stand out above all the rest and what sort of technology will they be using to run your site.</li>
<li> Ask them how they would intend to host your site, as you want to make sure they are using a secure solution that is backed up every day with the backups being kept for at least a week.</li>
<li> Make sure you tell them as much detail about your project as possible and ensure they have an exact specification to work to when calculating a quote or writing a proposal for you.</li>
<li> When you get a proposal back from the company, read it carefully and watch out for hidden terms and conditions and ensure that everything you want is in the proposal. As anything not specifically written in the proposal document is 99% of the time, not included in the price.</li>
</ul>
<p><strong>Golden Rule:</strong> It is important to remember that the cheapest option is not always the most sensible option (&#8220;<strong>pay peanuts, get monkeys</strong>&#8220;). However, it is still important to remember that big companies will charge more because they have more overheads involved.</p>
<p>It is also prudent to make sure you are not paying for a &#8216;big brand&#8217; company to work on your site, when they might not necessarily do anything different to a smaller brand company.</p>
<p>I&#8217;m not saying here that you should throw away your money, but you must make sure that the decision you make is not solely based on cost, but is a compromise of quality and keeping costs within your budget.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ecommerceexperiment.com/2009/06/16/how-to-choose-a-web-developer/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Choosing a technology</title>
		<link>http://www.ecommerceexperiment.com/2009/06/04/choosing-a-technology/</link>
		<comments>http://www.ecommerceexperiment.com/2009/06/04/choosing-a-technology/#comments</comments>
		<pubDate>Thu, 04 Jun 2009 21:00:17 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[ecommerce]]></category>
		<category><![CDATA[ecommerce development]]></category>
		<category><![CDATA[functionality]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[RoR]]></category>
		<category><![CDATA[Ruby on Rails]]></category>
		<category><![CDATA[technologies]]></category>

		<guid isPermaLink="false">http://www.ecommerceexperiment.com/?p=162</guid>
		<description><![CDATA[If you are building your own eCommerce site, then very early on, you will make a decision on the technology that will make the basis of your site.
Your first decision is to determine if you wish to develop your own system from scratch, or do you want to use readily available open source software and [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="margin-top: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.ecommerceexperiment.com%2F2009%2F06%2F04%2Fchoosing-a-technology%2F"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.ecommerceexperiment.com%2F2009%2F06%2F04%2Fchoosing-a-technology%2F" height="61" width="51" /></a></div><p>If you are building your own eCommerce site, then very early on, you will make a decision on the technology that will make the basis of your site.</p>
<p>Your first decision is to determine if you wish to develop your own system from scratch, or do you want to use readily available open source software and adapt it to meet your requirements. This usually comes down more to your situation, budget and time frame. If you have a short time frame and a low budget, then you really don&#8217;t have time to be building your own software, so you need to use open source.</p>
<p>In our case, we will be developing our own system from scratch (or rather rebuilding our old system from scratch), this is because we have time to work on the development of the system and it gives us an opportunity to blog about the system as we go, explaining how and why we did things as we go.</p>
<p>Open source software is a quick and cheap alternative to get your eCommerce system up and running, and some of the software currently available (magento, etc) is phenomenal. One of the major downsides that we find with open source eCommerce systems, is that generally they don&#8217;t quite fit with how you want to do things, and if you don&#8217;t know them inside out, it makes it much harder to change things to be more suited to your needs.</p>
<p>We also chose not to use open source technology as we would need to invest a significant amount of time familiarising ourselves with the system and how it works and how the coding works, so that if we decide to integrate it with a stock control system, we would be able to do so. This all takes up valuable time, which by the time we&#8217;re confident enough to be writing useful additions to the open source software, we could have just written a system ourselves that is tailored to our exact needs, but if we do need to modify it, it&#8217;s easy because we built it, so we can change it 10x quicker than anyone else could.</p>
<p>Once you have made a choice between open source and developing your own system, the next choice will only really relate to those that chose to build their own system, as choosing an open source software package will have already dictated to you what language will be used.</p>
<p>If you are building your own system however, you will need to decide what DB to use and what programming language you want to use in order to the develop the system. One of the most common combinations is a MySQL database with PHP, however Ruby on Rails is proving to be a big contender for PHP and is certainly worth a look in.</p>
<p>Because we have more experience in working with PHP, I chose to continue down the route of using PHP in conjunction with a MySQL database as it will enable me to quickly work through the development without having to learn new things by using ROR. At the end of the day, I think that whatever technology you choose to use, will not make much of a difference to the end result, it is just about what you are more familiar with and how confident you are that you can develop such a complex system using that technology.</p>
<p>It is a good idea to plan out the development of the software, so that you can keep on top of things and keep track of where you should be with the development, so that you can deliver the software in time to launch your new online store. With this in mind, I would suggest creating an implementation schedule, where you list all of the tasks and items that need to be built/developed in order to make the system, and then prioritise these, setting targets based on how long you think it will take to make. An important thing to remember is that you should prioritise features that are considered to be CORE functionality features, and then once these features have been completed, then you can start to look at features that are not a necessity to launch, but may well make your admin life easier.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ecommerceexperiment.com/2009/06/04/choosing-a-technology/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>The Banking Hurdles</title>
		<link>http://www.ecommerceexperiment.com/2009/05/23/the-banking-hurdles/</link>
		<comments>http://www.ecommerceexperiment.com/2009/05/23/the-banking-hurdles/#comments</comments>
		<pubDate>Sat, 23 May 2009 11:49:09 +0000</pubDate>
		<dc:creator>Justin</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Money]]></category>
		<category><![CDATA[banking]]></category>
		<category><![CDATA[business banking]]></category>
		<category><![CDATA[carts]]></category>
		<category><![CDATA[ecommerce]]></category>
		<category><![CDATA[ecommerce development]]></category>
		<category><![CDATA[ecommerce experiment]]></category>
		<category><![CDATA[ecommerce shopping]]></category>
		<category><![CDATA[hsbc]]></category>
		<category><![CDATA[opening a bank account]]></category>
		<category><![CDATA[transactions]]></category>

		<guid isPermaLink="false">http://www.ecommerceexperiment.com/?p=96</guid>
		<description><![CDATA[In the long terms will we stay with HSBC? I doubt it unless our business grows drastically to over £1 million. The major problems I had with HSBC are that unless you are a sizable business they really don't care and are faceless in communicating with their customers. When you need something from them you have a long drawn out process and no ability for them to be flexible. Business colleagues who are running large turnover businesses can't speak highly enough of HSBC as a personal bank manager is appointed.]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="margin-top: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.ecommerceexperiment.com%2F2009%2F05%2F23%2Fthe-banking-hurdles%2F"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.ecommerceexperiment.com%2F2009%2F05%2F23%2Fthe-banking-hurdles%2F" height="61" width="51" /></a></div><p>I&#8217;m sure you&#8217;ve been at a dinner party and at some point during the evening someone mentions a bad experience with a bank. It&#8217;s like opening the flood gates as everyone round the table will have a story to tell. Unfortunately I&#8217;m not able to tell you that a business can run without a bank as it can&#8217;t! Unless you&#8217;re stuffing all your cash under the floor boards.</p>
<h4>Are banks all the same or should you be using the same criteria as a normal supplier to choose who to work with?</h4>
<p>In my view this is true to a certain degree and in the current economic climate banks are hard work. We have taken a slightly strange approach to choosing our bank.</p>
<p>We are going with <a href="http://www.hsbc.com/1/2">HSBC</a> not for the fact I think they are a great bank but because I&#8217;ve banked with them as a business for 5 years. Another deciding factor is all my <a href="http://www.ecommerceexperiment.com/about/">co-directors</a> also bank with HSBC. As we are on a tight time frame we are able to open an account very quickly as we are known customers of the bank.</p>
<p>Due to the time constraints on us to open the account it seemed important to open a bank account with the least number of hurdles. HSBC like all banks are wary of new businesses but having a proven business banking trading history and personal banking trading history goes along way. This shows the bank that we can keep within facilities, how much we have in the account and what risk they are exposed to from the get go.</p>
<p>This will be my forth business bank account with HSBC so I know how to fill out the forms, what to expect from their team and the hurdles I need to cross.</p>
<p>In the long terms will we stay with HSBC? I doubt it unless our business grows drastically to over £1 million. The major problems I had with HSBC are that unless you are a sizable business they really don&#8217;t care and are faceless in communicating with their customers. When you need something from them you have a long drawn out process and no ability for them to be flexible. Business colleagues who are running large turnover businesses can&#8217;t speak highly enough of HSBC as a personal bank manager is appointed. Until you get to this point you are going to feel very lonely. It&#8217;s very likely once the business has a trading history of just 3-4 months we will move our banking facilities.</p>
<p>I don&#8217;t want to open the flood gates but I would like to hear from other small businesses on arranging their banking.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ecommerceexperiment.com/2009/05/23/the-banking-hurdles/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Development from the beginning</title>
		<link>http://www.ecommerceexperiment.com/2009/05/22/development-from-the-beginning-2/</link>
		<comments>http://www.ecommerceexperiment.com/2009/05/22/development-from-the-beginning-2/#comments</comments>
		<pubDate>Fri, 22 May 2009 12:40:34 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[ecommerce development]]></category>
		<category><![CDATA[ecommerce experiment]]></category>
		<category><![CDATA[software]]></category>

		<guid isPermaLink="false">http://www.ecommerceexperiment.com/?p=91</guid>
		<description><![CDATA[We have always used our own software for our ecommerce sites from the beginning. Since then the system has been added to and modified as and when required to add or improve functions on a very ad hoc basis. We had been planning various upgrades to the system in order to improve it&#8217;s functionality and [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="margin-top: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.ecommerceexperiment.com%2F2009%2F05%2F22%2Fdevelopment-from-the-beginning-2%2F"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.ecommerceexperiment.com%2F2009%2F05%2F22%2Fdevelopment-from-the-beginning-2%2F" height="61" width="51" /></a></div><p>We have always used our own software for our ecommerce sites from the beginning. Since then the system has been added to and modified as and when required to add or improve functions on a very ad hoc basis. We had been planning various upgrades to the system in order to improve it&#8217;s functionality and capabilities, but I quickly came to the conclusion that perhaps there was a better way to go.</p>
<p>After spending some time looking around for open source alternatives to our system (which there are some extremely smart packages out there i.e. magento, etc), I felt that these solutions would become more of a problem than a solution. We would need to invest a significant amount of time into familiarizing ourselves with the code and how the system works and the processes involved. Without this it would be very difficult for us to make changes to the underlying system if we needed to add to the functionality to meet a clients needs.</p>
<p>Deciding that our current system wasn&#8217;t up to the job and the open source alternatives weren&#8217;t going to be suitable for what we needed, I took the decision to completely redevelop our software from scratch. This would enable us to eradicate any problems from the old system, implement new functionality and most importantly, improve the usability of the admin area to make it as simple to use as possible.<br />
I will be building the new system alongside and around the ecommerce experiment site, this will enable us all to personally use the system day to day as part of the experiment, so we will quickly be able to iron out any bugs or usability issues.</p>
<p>The plan for the development is to build up a basic framework for the admin area and the database, ensuring it is functional and robust enough for our needs. I will then work with Ryan to integrate the new design for the site with the system, whilst completely rewriting the code that deals with the checkout process, making the flow from basket -&gt; checkout -&gt; order confirmation much more simpler for the customers to use.<a rel="me" href="http://technorati.com/claim/835zckkqja">Technorati Profile</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.ecommerceexperiment.com/2009/05/22/development-from-the-beginning-2/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
