Trespass: rebuilding retail and home around catalogue depth.

Trespass needed cleaner product data and a more maintainable catalogue so the Retail & home business could trade with confidence.

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.

Self-serve buying has to behave predictably at peak without leaking edge cases into the order pipeline.

A new commerce surface had to land cleanly inside an operating business, not as a standalone project.

The difficult part was not the storefront alone. Account rules, stock, pricing, order history, fulfilment and product data all had to line up behind the buying journey.

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.

Unclear product, pricing or fulfilment information can create friction before an order is placed.

Most relevant to Retail & home teams running B2C and D2C 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.

Friction in the buying flow does not show up as a complaint. It shows up as quieter weeks and a slow erosion of intent.

The project did not end when the platform went live.

Support mattered because the retail and home 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.