Inventory movements and jobs
Clark Wilkins, Simplexable
2018.03.27
<p>At times, coordination between the inventory team and the front office can become difficult. In a recent &#8220;real-world&#8221; example, a client had a job where a single SKU was shipped three times (different items) to deal with customer claims of DOAs or warranty failures. The problems arise when the front-office billing staff are trying to figure out what was sent, what was returned, and what (if any) items are outstanding or require rebilling.</p>

<p>To deal with this, we released a new job view today, <b>inventory movement</b>, that shows:</p>

<ul>
	
	<li>What was attached to the job?<sup>1</sup></li>
	<li>What is the current status of each attached item?</li>
	<li>Was an exchange item received?<sup>2</sup> If so, what's the status of it?</li>
	
</ul> 

<p>The desktop and mobile versions are shown below for the job with three connected items, one of which has an exchange item.</p>

<img src = "images/blog/041.jpg" border = "1" >

<div class = "label">desktop view</div>

<img src = "images/blog/042.jpg" border = "1" >

<div class = "label">mobile view</div>

<p>These lists are immediately available in the <tt>inventory movements</tt> view.<sup>3</sup>


<div class = "label">

	<div>NOTES</div>
	
	<ol>
	
		<li>As of v16.158 (2017.12.16), we switched over to a permanent relationship connection &#8212; even if the item gets detached.</li>
		<li>As of v16.114 (2017.06.10), we instituted a new system to record these relationships, but, for practical reasons, it was not implemented retroactively.</li>
		<li>This only shows up in the views list if there's something relevant to display.</li>
	
	</ol>

</div>