Over the last six months – and somewhat covertly – we’ve been tinkering with the engine that drives our already-industry-leading matrix pricing system.
Anyone out there who has tried to design and develop their own tool to search, price and validate SME pricing – across the entire board of energy suppliers – will no doubt have felt a great deal of pain. It’s not an easy task, and it wasn’t for us either. Most obviously, prices need to be correct. But taking into account the volume of models used by suppliers, an ever-changing landscape of products and literally hundreds of thousands of combinations of rates, it’s not straight forward. Add into this mix the necessity to automate the processing of flat files, validation of data and configuration of the characteristics of each product and you’re soon face to face with a behemoth, with long pointy claws and a poisonous wart at the end of its nose…or is that a Gruffalo (I’m a new dad; still learning).
It took iteration after iteration, after iteration…after iteration (you get the idea), but we cracked it. And multi-site matrix pricing is just one of the fundamental components of the UtilityClick platform. Thousands of quotes are generated each month by our users, saving immeasurable volumes of time and cost.
But at the start of the year, we decided to take things several leaps and bounds further, by developing a pricing API which can radically improve the speed and flexibility of matrix pricing, whilst providing the opportunity for TPIs to access the UtilityClick technology stack from external systems. 1 meter or 100 meters – it doesnt matter – a single JSON request (getting a bit technical here now!) and pricing calculations are performed in milliseconds then provided to the end user to format and deliver to their customers. Huzzah!
We’re already using this API technology internally, communicating between the UtilityClick platform and our dedicated-and-infinitely-scalable proprietary quoting service and our entire customer base will be benefiting from increased speeds by the end of summer.
As for the public-facing API, we’ll be revealing more information in due course; but until then, we’d love to hear from you if you’re interested in getting ahead of the pack and learning more.