<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title><![CDATA[Retail Evolved Blog]]></title>
    <link>http://retailevolved.com/blog/</link>
    <description><![CDATA[Retail Evolved Blog]]></description>
    <pubDate>Sat, 19 May 2012 20:04:15 +0000</pubDate>
    <image>
      <url>http://retailevolved.com/skin/frontend/evolved/evolved/images/icon_feed.png</url>
      <title>Retail Evolved Blog</title>
      <link>http://retailevolved.com/blog/</link>
    </image>
    <generator>Zend_Feed</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[Facebook Updates OpenGraph Page Requirements]]></title>
      <link>http://retailevolved.com/blog/facebook-updates-opengraph-page-requirements/</link>
      <description><![CDATA[<h4 class="h4">
	You MUST update your &lt;html&gt; tags if you are using the XFBML button</h4>
<b>Recently,&nbsp;</b>we&nbsp;started to receive a number of support requests indicating that the Like button was not posting correct images and descriptions to user&#39;s walls. We started digging and discovered that Facebook quietly made a change to their documentation that will have a direct impact on you if you are using an XFBML button.<br />
<br />
In the old version of our docs, it instructed you to change your opening &lt;html&gt; tag to:<br />
<br />
<div>
	<em>&lt;html&nbsp;xmlns=&quot;http://www.w3.org/1999/xhtml&quot; xml:lang=&quot;&lt;?php echo $this-&gt;getLang() ?&gt;&quot;&nbsp;xmlns:fb=&quot;http://www.facebook.com/2008/fbml&quot; xmlns:og=&quot;http://opengraph.org/schema/&quot;&nbsp;lang=&quot;&lt;?php echo $this-&gt;getLang() ?&gt;&quot;</em></div>
<br />
Well, they changed it. Now you need to change it to read:<br />
<br />
<em>&lt;html&nbsp;xmlns=&quot;http://www.w3.org/1999/xhtml&quot; xml:lang=&quot;&lt;?php echo $this-&gt;getLang() ?&gt;&quot;&nbsp;xmlns:fb=&quot;http://www.facebook.com/2008/fbml&quot; xmlns:og=&quot;http://ogp.me/ns#&quot;&nbsp;lang=&quot;&lt;?php echo $this-&gt;getLang() ?&gt;&quot;</em><br />
<br />
Note the change to <i>xmlns:og=&quot;http://ogp.me/ns#&quot;.</i><br />
<br />
This change needs to be made to the following files:<br />
<ul>
	<li>
		app/design/frontend/[package]/[theme]/template/page/1column.phtml</li>
	<li>
		app/design/frontend/[package]/[theme]/template/page/2columns-left.phtml</li>
	<li>
		app/design/frontend/[package]/[theme]/template/page/2columns-right.phtml</li>
	<li>
		app/design/frontend/[package]/[theme]/template/page/3columns.phtml</li>
</ul>
If you do not make this change, the button may not function as you expect it to. Once you are done making the change, you should run a few test URLs through the Facebook URL linter here:&nbsp;<a href="https://developers.facebook.com/tools/debug">https://developers.facebook.com/tools/debug</a>&nbsp;- it will tell you if there are any problems. You may get a warning about a locale, but that is an issue that will be addressed in a future update (don&#39;t worry, Facebook still grabs the locale from your web page).<br />
<br />
<img alt="" height="247" src="https://us2.admin.mailchimp.com/_ssl/proxy.php?u=http%3A%2F%2Fgallery.mailchimp.com%2F88e61384799da407e0daee2eb%2Ffiles%2FScreen_Shot_2011_11_07_at_10.30.04_PM.png" style="width: 400px; height: 247px; " width="400" />&nbsp; &nbsp;<br />
<br />
<br />
]]></description>
      <pubDate>Tue, 08 Nov 2011 07:00:51 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Retail Needs a Simple Data Sharing Standard]]></title>
      <link>http://retailevolved.com/blog/retail-simple-data-sharing-standard/</link>
      <description><![CDATA[<p>Current data sharing solutions are expensive and complicated - so much so, that typically only the "big box" stores can participate. It's time to move away from complexity and embrace a simple data sharing standard for retail.</p>
<h3>How it Could Save (and Earn!) Cash</h3>
<p><span style="font-weight:bold;">Eliminates most manual data entry.</span> Think about it: Much of the information you input into your system is created at the top of the supply-chain by the manufacturer. Descriptions, images, suggested pricing, UPC, manufacturer part number - just to name a few. If you buy direct, they even have your cost. A simple sharing standard would open this up to be used by distributors and retailers alike. Why should you enter data again if somebody has already done it for you?</p>
<p><span style="font-weight:bold;">Up-to-date information.</span> Have you ever lost money because a supplier forgot to send you information about a cost increase? Mistakes happen, and some are more expensive than others. Maintaining pricing information in particular can be a tedious and difficult task. In my dream world of  simple data sharing, my POS system will automatically get updated costs every night. When I get there in the morning, I will be presented with cost movements so that I can intelligently determine if I need to adjust my selling price. I know, it sounds like Minority Report style retail technology; but, this type of functionality would be commonplace if a standard were in place.</p>
<p><span style="font-weight:bold;">Your systems could talk to each other!</span> Even the smallest operations will have multiple systems nowadays. It's not uncommon for a "mom and pop" to have a POS system, accounting software, and a website. Guess what? They *all* need some of the same data. As a standard gets adopted, software developers could build import / export functionality into everything they do. Wouldn't it be nice if inputting your data once caused it to cascade automatically to all of your systems?</p>
<p><span style="font-weight:bold;">Customers would love it!</span> "What? Most customers couldn't care less about what my data looks like or how it gets there". That is, unless part of the standard enabled you to share live inventory information. Mobile, location-based services are huge right now. A customer could literally take their Christmas shopping list and find every store near them that has what they are looking for. What's more, since it is an open standard, developers could make all sorts of applications to utilize your data.</p>
<h3>What it Should Look Like</h3>
<p><span style="font-weight:bold;">Public property - no gatekeepers.</span> No private organization should claim ownership of the standard. An organization could be created to administer the standard, but adopters shouldn't even have to be aware of this organization to start implementing it. Think HTML and websites. Did you have to call the <a href="http://www.w3c.org" title="World Wide Web Consortium">W3C</a> to start developing your website? Did you even know that they existed?</p>
<p><span style="font-weight:bold;">Simple.</span> Yep, simple. Now, the term "simple" is relative. But standards like EDI and GS1 are way over the top. They try to provide rules for every possible scenario resulting in thick rulebooks and incomprehensible jargon. Here's an idea: Instead of trying to think of every possible scenario, make the standard flexible. Let participants find creative ways to solve problems and they will. Just look at how far the web has come!</p>
<p><span style="font-weight:bold;">Free.</span> Access to the standard should be free (looking at you, <a href="https://www.nrf.com/nrf-arts/joinform.asp" title="ARTS">ARTS</a>). Adoption of the standard should not require an admission fee or annual dues. The only cost should be the cost of implementation. Again, like building  a website.</p>
<p><span style="font-weight:bold;">Privacy and Access Controls.</span> One difference between web sites and a retail standard is the need for privacy. Some information should not be available for public consumption (i.e. your cost). Participants must be able to determine who has access to what information.</p>]]></description>
      <pubDate>Fri, 28 May 2010 14:24:21 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Facebook Like Button - What you should know]]></title>
      <link>http://retailevolved.com/blog/facebook-like-button/</link>
      <description><![CDATA[<p>We just recently launched our latest extension: <a href="http://retailevolved.com/facebook-like-button.html" title="Facebook Like Button">Facebook Like Button</a>. When Facebook announced this new way of connecting with users on Wednesday, we immediately got to work on making it easy for you to add this powerful feature to your Magento catalog.</p>
<p>Our goal was to make it so that  you can add a Like button to your catalog in less than 5 minutes. If you've got 15 minutes, you can take the time to set up a Facebook application and enable the commenting feature of the Like button - something that we highly recommend.</p>
<p>You can see a sample of the commenting feature <a href="http://retailevolved.com/facebook-like-button.html" title="Facebook Like Button">here</a>. The 5-minute install version is <a href="http://magedemo.retailevolved.com/sony-vaio-vgn-txn27n-b-11-1-notebook-pc.html" title="Sample Like Button">here</a>.</p>
<p>One last note: In addition to adding a Like button to your product pages, we optimized the experience for your users by adding meta tags with the most relevant product name, image, and description and providing a central place in the Magento admin for managing your buttons.</p>]]></description>
      <pubDate>Fri, 23 Apr 2010 18:13:16 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Magento Launch Checklist]]></title>
      <link>http://retailevolved.com/blog/magento-launch-checklist/</link>
      <description><![CDATA[<p>Launching a new Magento website can be a daunting task. We've been through a few of them and are publishing the <a href="/media/uploads/configuring_magento.pdf" title="Magento Pre-Launch Checklist">Magento Pre-Launch Checklist</a> that we provide to all of our customers, free of charge.</p>
<p>This 9-page document has been refined over many Magento installations and will save you hours of research and experimentation.</p>
<p>Please <a href="/contacts" title="Contact Retail Evolved">contact us</a> if you have any questions or would like a free consultation.</p>

]]></description>
      <pubDate>Thu, 18 Mar 2010 22:24:43 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[The New Retail Evolved]]></title>
      <link>http://retailevolved.com/blog/new-retail-evolved/</link>
      <description><![CDATA[<p>We haven't posted for a while because we have been busy launching our new website. Now you'll be able to easily purchase many of our Magento extensions and services. We'll also use this as a platform for launching all of our new products.</p>
<p>If you have any questions, comments, or suggestions, you can always <a href="/contacts" title="Contact Us">contact us</a>.</p>
<p>We are going to be posting some great Magento tips and tricks over the next week so stay tuned.</p>]]></description>
      <pubDate>Fri, 05 Mar 2010 07:22:59 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Google to Allow Remote File Storage]]></title>
      <link>http://retailevolved.com/blog/google-to-allow-remote-file-storage/</link>
      <description><![CDATA[<p>According to TechCrunch (see the original article <a title="Google GDrive Launches. Just Don’t Call It That." href="http://www.techcrunch.com/2010/01/12/google-gdrive-launches-just-dont-call-it-that/" target="_blank">here</a>), Google will soon be allowing you to upload any file as part of Google Docs.</p>
<p>What does this mean for you? Here are a few ideas:</p>
<p><strong>Simple File Sharing</strong></p>
<p>When email attachments aren&#8217;t good enough, uploading a file to Google Docs is a perfect solution. There is apparently going to be a 250 MB file size limit, which is much higher than most restrictions on email attachments. The service will also allow you to share the files with anybody (Google and non-Google users alike).</p>
<p><strong>Poor Man&#8217;s VPN</strong></p>
<p>One reason to have a VPN is to enable remote file access. If you don&#8217;t have the resources or expertise to set up and manage a VPN, this service could be a very cost-effective method for accessing important files while away from the office. Am I advocating this as a true alternative to a VPN? Absolutely not,but it does make it easy to access your files from anywhere.</p>
<p><strong>File Sync Between Machines</strong></p>
<p><strong><span style="font-weight: normal;">Almost every professional has more than one computer now. Between office desktops, personal laptops, netbooks for traveling and, soon enough, tablet computers, there is a clear need to be able to easily share documents between machines. <a title="Memeo Connect" href="http://memeoconnect.com/" target="_blank">Memeo Connect</a> looks like it will be a simple solution for keeping your files synced, no matter which computer you are on.</span></strong></p>]]></description>
      <pubDate>Tue, 12 Jan 2010 18:00:00 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Must Read: The Go-Giver]]></title>
      <link>http://retailevolved.com/blog/must-read-the-go-giver/</link>
      <description><![CDATA[<p><a href="http://www.amazon.com/Go-Giver-Little-Story-Powerful-Business/dp/159184200X/ref=sr_1_1?ie=UTF8&amp;s=books&amp;qid=1261857059&amp;sr=1-1"><img style="float:left; margin-right: 10px;" title="The Go-Giver" src="http://blog.retailevolved.com/skin/frontend/evolved/evolved/images/41PYlieqCLL._AA240_.jpg" alt="The Go-Giver" width="240" height="240" /></a>A friend and mentor let me borrow a book this week called <em><a title="The Go-Giver" href="http://www.amazon.com/Go-Giver-Little-Story-Powerful-Business/dp/159184200X/ref=sr_1_1?ie=UTF8&amp;s=books&amp;qid=1261856946&amp;sr=8-1">The Go-Giver: A Little Story About a Powerful Business Idea</a></em>.</p>
<p>I would highly recommend it to anybody, whether you are in business or not. It is an extended parable about a &#8220;go-getter&#8221; that is trying to land the biggest sales deal of his career. He is introduced by a friend to a man who teaches him the 5 Principles of Stratospheric Success.</p>
<p>It&#8217;s a quick read, but will leave you thinking for a long time. For me, it easily lands in my top 5 business books of all time (a list that includes <em><a title="Good to Great" href="http://www.amazon.com/Good-Great-Companies-Leap-Others/dp/0066620996/ref=sr_1_1?ie=UTF8&amp;s=books&amp;qid=1261856973&amp;sr=1-1">Good to Great</a></em> and <em><a title="Blue Ocean Strategy" href="http://www.amazon.com/Blue-Ocean-Strategy-Uncontested-Competition/dp/1591396190/ref=sr_1_1?ie=UTF8&amp;s=books&amp;qid=1261857002&amp;sr=1-1">Blue Ocean Strategy</a></em>).</p>]]></description>
      <pubDate>Sat, 26 Dec 2009 18:00:00 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Retail Evolved Developer Blog]]></title>
      <link>http://retailevolved.com/blog/retail-evolved-developer-blog/</link>
      <description><![CDATA[<p>We just launched the Retail Evolved Developer Blog &#8211; it will have information specifically targeted towards developers. It&#8217;s located at <a title="Retail Evolved Development" href="http://blog.retailevolved.com/developers-blog.html" >http://blog.retailevolved.com/developers-blog.html</a>.</p>]]></description>
      <pubDate>Mon, 21 Dec 2009 18:00:00 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Turns and GMROII – A Powerful Relationship]]></title>
      <link>http://retailevolved.com/blog/turns-and-gmroii-a-powerful-relationship/</link>
      <description><![CDATA[<p><em>Note: This is an update to a post that was originally called &#8220;Break Even Turns&#8221;. After comments from industry experts, I have updated the post to reflect the relationship between inventory turns and GMROII (Gross Margin Return on Inventory Investment). For most locations, a GMROII of between $2.50 and $3.20 is required to truly break even.</em></p>
<p>Managing cash flow is one of the greatest challenges of retailing. To compete, retailers need to focus on stocking shelves with the right amount of the right product. Too much product and inventory becomes bloated, tying up much needed cash. Too little product and valuable sales are lost.</p>
<p>Lots of retailers focus on turns, the number of times their inventory is bought and sold. Mathematically, a turn is the average inventory of a product divided sales. For example, if you keep 10 widgets on a shelf at all times and you sell 100 widgets, you have just turned that product 10 times. A product that turns frequently is sometimes referred to as a &#8220;fast-moving&#8221; product &#8211; it leaves the shelf faster than most.</p>
<p>Turns play an important role in product selection and product pricing. A higher markup on a product means you will need fewer turns to break even on your investment. Conversely, a lower markup means more turns are required to break even.</p>
<p>To break even, most locations require a GMROII of between $2.50 and $3.20. This depends on factors like rent, wages, utilities, etc. &#8211; expenses that are not typically included in cost of a product when analyzing margins.</p>
<p>I recently decided to spend some time researching the relationship between GMROII and turns for the purpose of optimizing the purchasing of a local retailer. I wanted to answer the question: &#8220;Given a certain mark up, how many turns will it take to for a product to reach a target GMROII&#8221;?</p>
<p>Surprisingly, it&#8217;s fairly simple. Mathematically, the target GMROII divided by the Cost Markup Percentage (Markup / Cost) equals the number of turns required. Consider a widget that you purchase for $1.00 and sell for $1.50. The cost markup percentage is 50% ($.50 / $1.00). With a target GMROII of $2.50, we can determine that the widget needs to turn 5 times to reach that goal.</p>
<p>Why is this even important? Because now you (or your buyers) can determine how many widgets to stock on your shelf to get your desired return on investment, especially if you have some sales history to base your decision on.</p>
<p>For example, assume you are selling a widget with a Cost Markup Percentage of 75% (purchased for $1, sold for $1.75). Based on the GMROII Turns formula, you know that you have to turn 3.33 times to post a $2.50 GMROII. Last year, you sold 20 of these widgets. If you expect demand to stay the same (if only it were that simple), then you know that your average inventory needs to be under 6 (20 units sold divided by 3.33 needed turns) to reach your GMROII goal.</p>
<p>The above example is overly simplified, but the message still holds. The GMROII Turns formula should be applied at an annual level to accommodate for seasonality. If a widget triples in sells during fourth quarter, then you should adjust what you stock to meet that demand.</p>]]></description>
      <pubDate>Thu, 17 Dec 2009 18:00:00 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Appolicious Gives Pocket Retailer 5/5]]></title>
      <link>http://retailevolved.com/blog/appolicious-gives-pocket-retailer-5-out-of-5/</link>
      <description><![CDATA[<p>Appolicious, an iPhone app community and review site, gave Pocket Retailer 5 out of 5 bars.</p>
<p>&#8220;&#8230;this is an absolute must-have for anyone involved in the finances of a retail store&#8221;</p>
<p>See the full review <a title="Pocket Retailer Review" href="http://www.appolicious.com/articles/902-a-must-have-calculator-iphone-app-for-retailers" target="_self">here</a>.</p>]]></description>
      <pubDate>Mon, 30 Nov 2009 18:00:00 +0000</pubDate>
    </item>
  </channel>
</rss>

