In this guest post, Procurement Leaders invites Forrester Research's Duncan Jones to explore whether network fees are fair charge for value or an adoption barrier.
A topic that generates a lot of discussion among users of eCommerce is the question of whether suppliers should pay to use a network, or whether the buyer should fund the cost. Ariba is the leader of the Yes camp, while many of its competitors take the opposite stance and bash what they call the "Ariba Tax" at every opportunity. But should we be thinking more carefully about this fee?
I'm currently doing a detailed analysis of the leading eProcurement software providers for a Forrester Wave to publish in May; an important requirement for candidates is an eCommerce network that enables suppliers to immediately receive purchase orders that the software has raised and to communicate back acknowledgements, shipping notices, invoices, etc.
It may be a controversial viewpoint, but I support Ariba's position that suppliers should pay for the value they receive by being part of a network, such as greater visibility to buyers and streamlined order-to-invoice processes. The network fees are really just a B2B equivalent of what Amazon charges its merchants (and at a fraction of the rate too). However, in a market in which many networks are free to the supplier, procurement chiefs should consider whether that's the right approach for them.
In particular they should ask themselves:
Bottom Line: Enabling eCommerce with suppliers saves you money and them too, but can take a lot of effort from procurement chiefs and their teams.
Enrolment can be a challenge, so choose the provider who will best help you get maximum adoption by your suppliers. That may be one of the providers who all claim to be the world's largest and believe that they can charge a fee to suppliers to let them connect with their attractive populations of buyers, or it may be one that is free to the supplier – you have to decide based on your context.
Duncan Jones is vice president and principal analyst, Forrester Research. For more of his posts, visit the Forrester blog here.