What was actually wrong
Raleigh Bikes needed a commerce platform that supported the Retail & home business model and the trading patterns of its customers.
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.
Order flow, stock and customer data crossed several back-office systems, so integration boundaries and operational handoffs likely shaped how the platform was built.
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.
Self-serve buying has to behave predictably at peak without leaking edge cases into the order pipeline.
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
Unclear product, pricing or fulfilment information can create friction before an order is placed.
Most relevant to Retail & home teams running B2C, D2C and marketplace 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.
Five things, in order.
- 01Mapped the buying journey before the interfaceStarted with how customers actually order on this site, then let the journey shape the interface decisions, not the other way round.
- 02Rebuilt the commerce foundation around how the business operatesRebuilt the commerce surface inside the operating business, not as a standalone project.
- 03Brought product data into one governed workstreamProduct information, enrichment and catalogue structure were treated as a delivery workstream that enabled the commerce change. Technical data and downloads had to remain connected to the product context buyers used to identify the right item.
- 04Scoped the rules per audience, not per platformAccount-led ordering and self-serve buying were shaped as distinct journeys on the same foundation. Local catalogue, depot, inventory, delivery and pricing rules had to remain coherent for the buyer context in front of the screen.
- 05Moved the project into support with the operating context intactHandover preserved the operational decisions made during build, so support could keep moving the platform forward without re-learning the business.
Platforms and integrations
Difficult parts
Results
In the client's words
As a business outsourcing web development for the first time this was a new experience for a lot of us but iWeb made sure we were prepared from the start in terms of what would be needed and when to ensure the project was delivered on time and to a high standard. The communication and problem solving bought to every stage of the process from the design to delivery ensured everything ran smoothly and delivered great results. An area that particularly impressed us when working with iWeb throughout the project was the level of expertise they bought in challenging our ideas and processes to ensure we were constantly delivering a great product. I believe this has resulted in a much better web experience for our customers and is already delivering greater business results.”
Ongoing support
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.
Projects with a similar shape
A designer furniture commerce platform built around mobile journeys, product data and order management.
Furniture buyers supported through stronger mobile journeys, cleaner product data and tighter order flow.
A homewares PIM project built around catalogue enrichment and retail product data.
Homewares trading supported by cleaner product data, catalogue enrichment and connected ecommerce.
A discount retail PIM project built around product data, governance and channel readiness.
Retail product teams supported by faster catalogue preparation and more controlled product data.