<?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: Using Robots To Get Saks Web Orders Out A Day Faster</title>
	<atom:link href="http://storefrontbacktalk.com/supply-chain/using-robots-to-get-saks-web-orders-out-a-day-faster/feed/" rel="self" type="application/rss+xml" />
	<link>http://storefrontbacktalk.com/supply-chain/using-robots-to-get-saks-web-orders-out-a-day-faster/</link>
	<description>Techniques, Tools and Tirades about Retail Technology and E-Commerce</description>
	<lastBuildDate>Thu, 24 May 2012 17:32:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Marty</title>
		<link>http://storefrontbacktalk.com/supply-chain/using-robots-to-get-saks-web-orders-out-a-day-faster/comment-page-1/#comment-141923</link>
		<dc:creator>Marty</dc:creator>
		<pubDate>Fri, 18 Feb 2011 23:59:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=4766#comment-141923</guid>
		<description>I&#039;d agree with pass the buck.  A policy to publish pictures only if you will use them again seems senseless.  If you use the photo &#039;many&#039; times, I may not need to see it.  If you have never had to post it before, it might be REALLY useful to the reader.</description>
		<content:encoded><![CDATA[<p>I&#8217;d agree with pass the buck.  A policy to publish pictures only if you will use them again seems senseless.  If you use the photo &#8216;many&#8217; times, I may not need to see it.  If you have never had to post it before, it might be REALLY useful to the reader.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Evan Schuman</title>
		<link>http://storefrontbacktalk.com/supply-chain/using-robots-to-get-saks-web-orders-out-a-day-faster/comment-page-1/#comment-66292</link>
		<dc:creator>Evan Schuman</dc:creator>
		<pubDate>Thu, 11 Feb 2010 19:06:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=4766#comment-66292</guid>
		<description>Editor&#039;s Note: Of all of the things to disagree with me, you&#039;re choosing our internal image library policy? Ok. The costs I was referencing are not the cost of acquiring the photo. We pay those, too, but, as you point out, that wasn&#039;t the issue here. The cost is our costs to process photos in the various sizes we need and to process them through our production system. (They&#039;re used by the web site, newsletter and various mobile formats and they use different publishing systems.) It&#039;s simply our policy to only process images that we&#039;d use often. I truly doubt we&#039;d need to use that image again. We have other images that would work--images that relate to the retail involved (as we did this time) or generic assembly line and production images. If you really care about the particular of publishing cost structure, please reach out to me privately and I&#039;ll tell you whatever you want to know. But I am guessing that this exchange is fairly boring for 99.99 percent of our readers.</description>
		<content:encoded><![CDATA[<p>Editor&#8217;s Note: Of all of the things to disagree with me, you&#8217;re choosing our internal image library policy? Ok. The costs I was referencing are not the cost of acquiring the photo. We pay those, too, but, as you point out, that wasn&#8217;t the issue here. The cost is our costs to process photos in the various sizes we need and to process them through our production system. (They&#8217;re used by the web site, newsletter and various mobile formats and they use different publishing systems.) It&#8217;s simply our policy to only process images that we&#8217;d use often. I truly doubt we&#8217;d need to use that image again. We have other images that would work&#8211;images that relate to the retail involved (as we did this time) or generic assembly line and production images. If you really care about the particular of publishing cost structure, please reach out to me privately and I&#8217;ll tell you whatever you want to know. But I am guessing that this exchange is fairly boring for 99.99 percent of our readers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pass the buck</title>
		<link>http://storefrontbacktalk.com/supply-chain/using-robots-to-get-saks-web-orders-out-a-day-faster/comment-page-1/#comment-66291</link>
		<dc:creator>pass the buck</dc:creator>
		<pubDate>Thu, 11 Feb 2010 18:58:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=4766#comment-66291</guid>
		<description>I respectfully disagree. You could have asked for a file photo from the company to insert in the story - I would like to think the company would have complied, since they would be credited in the photo caption. The photo should be part of your library anyway, since it probably will not be the last time you write about these devices. The cost argument you&#039;re making does not really fly. If the expenses are what you are claiming, then you&#039;re probably wasting money. The technology that is available should not make it such an expensive venture as you suggest.</description>
		<content:encoded><![CDATA[<p>I respectfully disagree. You could have asked for a file photo from the company to insert in the story &#8211; I would like to think the company would have complied, since they would be credited in the photo caption. The photo should be part of your library anyway, since it probably will not be the last time you write about these devices. The cost argument you&#8217;re making does not really fly. If the expenses are what you are claiming, then you&#8217;re probably wasting money. The technology that is available should not make it such an expensive venture as you suggest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TRedd</title>
		<link>http://storefrontbacktalk.com/supply-chain/using-robots-to-get-saks-web-orders-out-a-day-faster/comment-page-1/#comment-66287</link>
		<dc:creator>TRedd</dc:creator>
		<pubDate>Thu, 11 Feb 2010 17:43:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=4766#comment-66287</guid>
		<description>I agree with Preston.  We need to see the possible devices that might replace us!</description>
		<content:encoded><![CDATA[<p>I agree with Preston.  We need to see the possible devices that might replace us!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Evan Schuman</title>
		<link>http://storefrontbacktalk.com/supply-chain/using-robots-to-get-saks-web-orders-out-a-day-faster/comment-page-1/#comment-66286</link>
		<dc:creator>Evan Schuman</dc:creator>
		<pubDate>Thu, 11 Feb 2010 17:41:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=4766#comment-66286</guid>
		<description>Editor&#039;s Note: Sure, we can . We just did. Seriously, there&#039;s an answer to that. Our image library consists of symbolic images. By symbolic, I mean that we can use each image multiple times for multiple stories. To us, an image might say &quot;E-Commerce&quot; or POS or credit card swipe, etc. The cost for us in processing such a photo--which would almost certainly only be used once--is not something that we can do. That said, we &lt;em&gt;could&lt;/em&gt; have linked to the vendor&#039;s site--which has plenty of pictures of the mechanical critters--but we try and avoid linking to vendor sites unless there&#039;s a very significant informational reason. Example: Let&#039;s say we do a story about how the top 100 E-Commerce performed in some test. We might link to a deep page within the vendor&#039;s site that has a grid of all of the sites and have they performed in all of the tests. But linking to a vendor site solely to display a picture of their product seemed a bad idea. But since you asked, this link is a video of the critters doing their thing. It&#039;s also a commercial for the vendor, which is why we didn&#039;t initially run it: http://www.youtube.com/watch?v=lWsMdN7HMuA</description>
		<content:encoded><![CDATA[<p>Editor&#8217;s Note: Sure, we can . We just did. Seriously, there&#8217;s an answer to that. Our image library consists of symbolic images. By symbolic, I mean that we can use each image multiple times for multiple stories. To us, an image might say &#8220;E-Commerce&#8221; or POS or credit card swipe, etc. The cost for us in processing such a photo&#8211;which would almost certainly only be used once&#8211;is not something that we can do. That said, we <em>could</em> have linked to the vendor&#8217;s site&#8211;which has plenty of pictures of the mechanical critters&#8211;but we try and avoid linking to vendor sites unless there&#8217;s a very significant informational reason. Example: Let&#8217;s say we do a story about how the top 100 E-Commerce performed in some test. We might link to a deep page within the vendor&#8217;s site that has a grid of all of the sites and have they performed in all of the tests. But linking to a vendor site solely to display a picture of their product seemed a bad idea. But since you asked, this link is a video of the critters doing their thing. It&#8217;s also a commercial for the vendor, which is why we didn&#8217;t initially run it: <a href="http://www.youtube.com/watch?v=lWsMdN7HMuA" rel="nofollow">http://www.youtube.com/watch?v=lWsMdN7HMuA</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Preston</title>
		<link>http://storefrontbacktalk.com/supply-chain/using-robots-to-get-saks-web-orders-out-a-day-faster/comment-page-1/#comment-66277</link>
		<dc:creator>Preston</dc:creator>
		<pubDate>Thu, 11 Feb 2010 16:50:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=4766#comment-66277</guid>
		<description>Dude, you CAN NOT write an article about orarge, shelf-moving robots and not post a picture!</description>
		<content:encoded><![CDATA[<p>Dude, you CAN NOT write an article about orarge, shelf-moving robots and not post a picture!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

