<?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: Labor, Sub-suppliers and Time&#8211;3 other ways to lose money in China</title>
	<atom:link href="http://silkroadintl.net/blog/2010/03/15/labor-sub-suppliers-and-time-3-other-ways-to-lose-money-in-china/feed/" rel="self" type="application/rss+xml" />
	<link>http://silkroadintl.net/blog/2010/03/15/labor-sub-suppliers-and-time-3-other-ways-to-lose-money-in-china/</link>
	<description>Your Branch Office in Asia</description>
	<lastBuildDate>Thu, 15 Dec 2011 16:52:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: David Dayton</title>
		<link>http://silkroadintl.net/blog/2010/03/15/labor-sub-suppliers-and-time-3-other-ways-to-lose-money-in-china/comment-page-1/#comment-1746</link>
		<dc:creator>David Dayton</dc:creator>
		<pubDate>Tue, 16 Mar 2010 03:54:14 +0000</pubDate>
		<guid isPermaLink="false">http://silkroadintl.net/blog/?p=793#comment-1746</guid>
		<description>I&#039;ll be honest, the back-up factory comment was tongue in cheek.  I&#039;ve never ever had a client that came to us that already had a back-up.  (If they had back-up&#039;s they wouldn&#039;t be coming to us!)  We have back-up&#039;s for (almost) everything we do simply because we&#039;ve been burned so many times that we learned our lesson.

We don&#039;t &quot;manage&quot; back-up suppliers as much as we qualify them and keep in touch with them (and use the them for other projects).  You&#039;re right, small buyers have no ability to work with one supplier and still keep another interested without an order.  Since we have numerous concurrent projects we have a much easier time keeping in contact with options and shifting quickly to someone new if things either go wrong or get delayed.

The hardest part of this though, is not finding a back up, it&#039;s actually getting the original factory to agree to 1/2 qtty.  Right now, when everything is 30 days late due to non-returning labor, they are a bit more understanding.  But at other times, when the source of the delay or problem is less defined, they are not so accommodating.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll be honest, the back-up factory comment was tongue in cheek.  I&#8217;ve never ever had a client that came to us that already had a back-up.  (If they had back-up&#8217;s they wouldn&#8217;t be coming to us!)  We have back-up&#8217;s for (almost) everything we do simply because we&#8217;ve been burned so many times that we learned our lesson.</p>
<p>We don&#8217;t &#8220;manage&#8221; back-up suppliers as much as we qualify them and keep in touch with them (and use the them for other projects).  You&#8217;re right, small buyers have no ability to work with one supplier and still keep another interested without an order.  Since we have numerous concurrent projects we have a much easier time keeping in contact with options and shifting quickly to someone new if things either go wrong or get delayed.</p>
<p>The hardest part of this though, is not finding a back up, it&#8217;s actually getting the original factory to agree to 1/2 qtty.  Right now, when everything is 30 days late due to non-returning labor, they are a bit more understanding.  But at other times, when the source of the delay or problem is less defined, they are not so accommodating.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Covner</title>
		<link>http://silkroadintl.net/blog/2010/03/15/labor-sub-suppliers-and-time-3-other-ways-to-lose-money-in-china/comment-page-1/#comment-1744</link>
		<dc:creator>Jesse Covner</dc:creator>
		<pubDate>Mon, 15 Mar 2010 03:11:57 +0000</pubDate>
		<guid isPermaLink="false">http://silkroadintl.net/blog/?p=793#comment-1744</guid>
		<description>Great post David.

I&#039;m curious...&quot;Options 3. Cut orders in half and give the other half to your back up factory (you do have a back up option, right?).  &quot; 

 What percentage of your sourcing customers actually have a back-up / secondary manufacturer?  I&#039;m working on a long-term Change Management project (ERP and Organizational change) with a multinational company.  They make a lot of &quot;custom&quot; products which require custom parts from suppliers.  But on a project basis, each part is essentially single-sourced to a supplier, and they don&#039;t systematically rotate those supplier between projects.  Stated reasoning is because the parts are custom made, and hence cannot multi-source.  BUT... we are not talking about custom tooling here.... many of the purchased-parts are basic sheet-metal parts (including custom cabinets made of sheet-metal).  I imagine a small company would have a more difficult time to manage a backup supplier.</description>
		<content:encoded><![CDATA[<p>Great post David.</p>
<p>I&#8217;m curious&#8230;&#8221;Options 3. Cut orders in half and give the other half to your back up factory (you do have a back up option, right?).  &#8221; </p>
<p> What percentage of your sourcing customers actually have a back-up / secondary manufacturer?  I&#8217;m working on a long-term Change Management project (ERP and Organizational change) with a multinational company.  They make a lot of &#8220;custom&#8221; products which require custom parts from suppliers.  But on a project basis, each part is essentially single-sourced to a supplier, and they don&#8217;t systematically rotate those supplier between projects.  Stated reasoning is because the parts are custom made, and hence cannot multi-source.  BUT&#8230; we are not talking about custom tooling here&#8230;. many of the purchased-parts are basic sheet-metal parts (including custom cabinets made of sheet-metal).  I imagine a small company would have a more difficult time to manage a backup supplier.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

