The clean “Vendor Master” problem- when strategy meets execution.

// <![CDATA[
var gaJsHost = ((&quot;https:&quot; == document.location.protocol) ? &quot;https://ssl.&quot; : &quot;http://www.&quot;);
document.write(unescape(&quot;%3Cscript src='&quot; + gaJsHost + &quot;google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E&quot;));
// ]]>
// <![CDATA[
try {
var pageTracker = _gat._getTracker(&quot;UA-857684-6&quot;);
pageTracker._trackPageview();
} catch(err) {}
// ]]>

Attended a great talk by Matt Marthinson (see page 7 in "The Negotiator") on working capital on Tuesday. Among  other very useful things Matt explained the concept of "vendor master"  in the context of working capital in ERP systems.

The vendor master as supply chain professionals know and marketing professionals may not realize is the master data organizations maintain by individual supplier. This data really drives all kinds of things like RFP's,Purchase Orders, Payment Terms and the very welcome "check in the mail"!

With thousands of suppliers large organizations can have all kinds of messy stuff happening. Typical examples are many entries for the same supplier and outdated payment terms. The purchase order is generated from the vendor master and due to general sloppiness the order going out may be completely missing agreed payment terms. The solution?- well- have only a few  individuals handling the vendor master and ensure that it reflects the current agreement with each supplier. 

If you think about it the "Vendor Master" problem is rampant in all kinds of organizations. Marketers really are not up to speed with customer data , schools with student data, associations are not entirely sure of the member data and the list goes on.

Cleaning  master data  and aligning with current strategy sounds boring but is critical to execution  The most well thought out strategy fails when simple things like addresses and email id's have changed.

%d bloggers like this: