JCB: rebuilding automotive and parts around catalogue depth and account buying.

Product information, catalogue structure and supplier feeds were likely sources of operational friction, with editorial and trading teams working around fragmented data.

This was not a standard ecommerce build. The platform had to handle parts identification, specialist catalogue depth, technical data, account buying, pricing imports, depot stock and the systems behind each order.

Trade buyers and account customers needed account-based pricing, repeat ordering and visibility of their own purchase history without friction.

Machinery parts commerce depends on more than product names and images. Buyers need catalogue structure, technical information and product relationships that help them identify the right part with confidence.

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 ERP, tax and fulfilment, 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.

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.

If parts data, technical information, price or depot availability drift, a customer can lose confidence before adding an item to the basket, choose the wrong part, or move the question back to customer service for manual checking.

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.

Once a buying habit moves elsewhere it is expensive to win back. The consequence of inaction is not dramatic; it is cumulative.

The project did not end when the platform went live.

Support mattered because the automotive and parts 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.