<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Selling products from your website</title>
	<atom:link href="http://blog.physiopulse.com.au/2009-10/selling-products-from-your-website/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.physiopulse.com.au/2009-10/selling-products-from-your-website/</link>
	<description>Getting the best out of your physiotherapy clinic website</description>
	<lastBuildDate>Mon, 12 Dec 2011 01:45:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Yalcin</title>
		<link>http://blog.physiopulse.com.au/2009-10/selling-products-from-your-website/comment-page-1/#comment-117</link>
		<dc:creator>Yalcin</dc:creator>
		<pubDate>Wed, 27 Oct 2010 04:26:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.physiopulse.com.au/?p=207#comment-117</guid>
		<description>An update regarding the eShop module I mentioned in my previous comment: For now we have decided to shelf the idea, as there seems to be little interest from our clients. We would rather keep our platform easy to use and delivering on promises instead of overloading it with features.

That said, if the demand increases, we will surely put it back on the roadmap.</description>
		<content:encoded><![CDATA[<p>An update regarding the eShop module I mentioned in my previous comment: For now we have decided to shelf the idea, as there seems to be little interest from our clients. We would rather keep our platform easy to use and delivering on promises instead of overloading it with features.</p>
<p>That said, if the demand increases, we will surely put it back on the roadmap.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yalcin</title>
		<link>http://blog.physiopulse.com.au/2009-10/selling-products-from-your-website/comment-page-1/#comment-16</link>
		<dc:creator>Yalcin</dc:creator>
		<pubDate>Wed, 13 Jan 2010 04:20:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.physiopulse.com.au/?p=207#comment-16</guid>
		<description>Sure thing! if your business is purely selling stuff online, there are many options - and Magenta is very nice indeed. However it requires resources to maintain and operate. A PayPal solution as above can be done in minimal time and would be sufficient for most of our clients.

We are currently planning an eShop module. However if our clients wanted to get serious about online retailing, we would be happy to set them up with a specialist store with Magenta (or another suitable product).</description>
		<content:encoded><![CDATA[<p>Sure thing! if your business is purely selling stuff online, there are many options &#8211; and Magenta is very nice indeed. However it requires resources to maintain and operate. A PayPal solution as above can be done in minimal time and would be sufficient for most of our clients.</p>
<p>We are currently planning an eShop module. However if our clients wanted to get serious about online retailing, we would be happy to set them up with a specialist store with Magenta (or another suitable product).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan</title>
		<link>http://blog.physiopulse.com.au/2009-10/selling-products-from-your-website/comment-page-1/#comment-15</link>
		<dc:creator>Jan</dc:creator>
		<pubDate>Sun, 13 Dec 2009 04:07:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.physiopulse.com.au/?p=207#comment-15</guid>
		<description>Wouldn&#039;t magenta be better? Magenta is open source and there are many templates for it. It can also handle a variety of payment methods.</description>
		<content:encoded><![CDATA[<p>Wouldn&#8217;t magenta be better? Magenta is open source and there are many templates for it. It can also handle a variety of payment methods.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

