What was actually wrong
Huws Gray Building Supplies & Solutions needed an ecommerce platform that could carry trade account ordering, repeat purchase patterns and operational reporting expected by a Builders & trade business.
This was not a brochure storefront. Buyers arriving for a specific item needed enough product information and context to identify it with confidence, while stock, account pricing and purchase history had to support the same buying decision.
Product information, catalogue structure and supplier feeds were likely sources of operational friction, with editorial and trading teams working around fragmented data.
Trade buyers and account customers needed account-based pricing, repeat ordering and visibility of their own purchase history without friction.
Stock was not one flat number. Depot location, availability and fulfilment context had to remain meaningful so customers and order teams could rely on what the platform showed.
Business customers also needed the platform to reflect how they buy: parent and child account relationships, repeat purchase, order history, account documents and the correct pricing and stock context.
The commerce layer had to sit cleanly alongside fulfilment and ERP, without turning every operational dependency into a launch risk.
The platform change also depended on product information being structured, enriched and governed well enough to support the catalogue. Product data was a major workstream within the wider commerce delivery, not a separate outcome claim.
What was at stake
When account-based pricing, repeat ordering and purchase-history visibility slip, trade and account customers lose confidence in the site and push work back onto sales and support.
Most relevant to Builders & trade teams running B2B, B2C and trade-account operations and weighing similar platform decisions.
If catalogue and operational data drift, buyers can lose confidence in product information, pricing, stock and purchase history. That can delay or abandon an order, while internal teams absorb the uncertainty through manual checking and customer service.
For repeat buyers and trade accounts, uncertainty creates friction every time an order is placed again. Wrong-part risk, unclear account terms and a harder repeat-order path can frustrate buyers and move the burden back to account teams and support.
Trade accounts do not give second chances. A bad first experience pushes the order to a competitor and the relationship rarely comes back.
Three things, in order.
- 01Discovery and platform selectionIn their ambition to elevate digital capabilities and deliver an exceptional online experience, Huws Gray selected iWeb as their strategic digital partner. With deep expertise in Adobe Commerce (Powered by Magento) and a track record of supporting large-scale merchants, iWeb was placed to lead the transformation.
- 02Platform design and buildThe collaboration with Huws Gray covered the design, development and deployment of a scalable ecommerce platform. It needed to support complex trade workflows, multi-site branch operations, live stock and pricing visibility, and integration with back-office systems.
- 03Alignment with in-house teamsWorking closely with Huws Gray's in-house teams, the digital solution was aligned to strategic ambitions: supporting trade and retail customers more effectively, enabling operational efficiency across branch and online channels, and building a foundation for future development.
Platforms and integrations
Difficult parts
Results
In the client's words
Working with iWeb has been a game-changer for us. They understood the scale and complexity of our business from day one and delivered a platform that aligns with our ambition to serve trade and retail customers seamlessly. The feedback from our branches and customers has been fantastic — it’s set us up for that next level of growth.”
Ongoing support
The project did not end when the platform went live.
Support mattered because the builders and trade still depended on parts data, pricing imports, account behaviour, inventory feeds, integrations and customer-facing information after launch.
Keeping the build decisions and system ownership visible gave the support team a clearer basis for tracing issues and maintaining the connected trading system after launch.









