Commodity trees are essential for categorization of spend and running successful eProcurement but when it comes to eSourcing the use of commodity trees is still far behind its potential. Some companies categorize their eSourcing projects and templates but most of them fail to draw meaningful information from this.
Challenge #1 – One commodity tree
A lot of companies are faced by the challenge that they are still using multiple commodity trees in parallel. This is mainly due to the lack of a central categorization policy and due to mergers and acquisitions. Each time they take over a new company the will most likely inherit another commodity tree. The only way out of this dilemma is to take a decision for one central scheme and enforce usage on it.
Challenge #2 – Consistent usage
Many companies still leave it optional for the buyer to categorize projects, templates and suppliers. This might be a convenient approach but its wrong – in my point of view categorization should be mandatory always. People are lazy and if you give them the option to “NOT categorize” what do you expect?
Challenge #3 – Creating value from categorization
Almost all systems still lack of delivering meaningful and valuable information based on commodity trees. Here is my idea how this can be improved and how you can unleash the power of commodity trees:
Unleash the power
As a prerequisite is must be mandatory for each buyer to categorize eSourcing events, projects and templates – not more but also not less. Once you have ensured this you can use this data and teach your eSourcing system to become more intelligent.
A simple example
A buyer creates an RFQ for transport services by rail. Using e.g. UNSPSC he will categorize the RFQ as “78101600 Rail Cargo Transport” . The buyer will invite 12 suppliers from 3 different countries to bid on the RFQ.
Now here is the trick!
As the suppliers have been invited to bid on the RFQ they most likely can provide the required service. So why not automatically assign them to the category “78101600 Rail Cargo Transport”? By applying this approach your supplier database will become more intelligent with each eSourcing event that you run without any extra manual effort!
The same rule can be applied to the buyer. As he has conducted an RFQ in this category he might be a good contact person for other buyers to share knowledge. So why not automatically assign the buyer to this category also?
To really leverage this information all buyers should be able to search the eSourcing system by commodity. Just by searching for “78101600 Rail Cargo Transport” you will instantly get access to all buyers in your company who have been active in this commodity. You will get a list of all suppliers your company has already been in contact with and you will see a track record of past events which have been conducted in this field.
Everyone is talking about best practice knowledge sharing – I call this a good start!