“There’s a concern vendors will generally now keep these terms in”
Tom Stephens, CEO, Techary
Some of the big hardware vendors are now reserving the right to adjust pricing on orders up to the point of shipment. Have you seen anything like this before, and how big a disruption is this to the way the channel usually operates?
The nearest experience to relate this to is the COVID-19 pandemic. That was a focus on end-user devices, and work-from-home setups, rather than the impact across the supply chain, and with more impact to the infrastructure business than ever before.
With these being legal adjustments too, we have to instantly pivot and adapt in both our own review of terms with end-customers, to pass through these changes, but also work to navigate the impacts to the technology on the projects we work within. Different customers have different procurement cycles, and the traditional channel model worked well, with the process of having quotations valid for say 30 days, and then internal procurement plus budget sign off from the customers. Now that’s changed, and process across both resellers and end-customers have a need to be reinvented to adapt to these market changes.
Given the shortages are being caused by AI data centres, to what extent do you have sympathy with vendors who are having to tweak their Ts and Cs?
It’s a challenging time. We appreciate that the driver of these issues is caused by third-party component increases, and are largely out of control for the OEMs.
I think the vendors could help partners with some additional insight, but also appreciate that some of this may be sensitive. Most of the large OEMs forward buy memory and guarantee pricing for a period, but they haven’t shared when these contracts end, at what levels they are rebuying, and what orders are they prioritise and how. You get different answers from different people at the OEMs, and whilst the market is fluid, some of the messaging is inconsistent.
What will be the knock-on effect, for instance in terms of favouring alternative vendors, cloud-based solutions or second-user equipment?
For us it’s doing a few different things. It’s bringing forward conversations that would be throughout the year to now. The urgency does help to accelerate planning and execution. If you want to deploy a project in 2026, you best be ready to order now.
There are also alternate vendors we have worked with who are adapting to the situation better. An example, we are working with a more niche server manufacturer on custom builds for clients, albeit with extended lead times, but they are committing to quotations and pricing upon ordering – unlike some of the larger OEM changes we are seeing. It makes customers more open to alternative solutions than before.
A few other points:
We have seen multi-million $ of impact, live to quotations, and sometimes within the “quotation windows” the OEMs are publishing. It’s making the reseller role more important than ever, but it also demonstrated complexity and pressure on the channel model, with points such as:
Distributors and resellers need to turn things around quicker, to ensure the quote windows are not impacted to the customer, whilst dealing with increased volumes and ever-changing processes to adapt to these terms and condition changes.
Credit is being consumed more than ever. Distributors offer a great service to the channel, but with the lead times consistently increasing, more and more orders are being placed with a longer lead time, and impacting credit availability. Some end customers have told us resellers have asked customers for upfront payments to look to alleviate this, but that’s not something end customers are always willing to do, and not something we have done to date.
There is also a concern that vendors will generally now keep these terms in. Can we see a time ahead where they will then remove the ability to change pricing? I think they’ll stick to this approach and keep these terms contractual now, so we’ll need to see how this redefines the “new normal” for channel providers.
Natilik’s Ian Anderson weighs in on next page…
