What was actually wrong.
Most commerce problems are not just front-end problems. They sit between how customers buy, how teams work, and how the systems behind the business behave.
Gardening Direct needed a commerce platform that supported the Home, garden & outdoor 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 happens if it isn't fixed.
When those gaps are left alone, the website becomes the place where operational problems show up. That can mean unclear data, pricing questions, repeated support queries and customers who cannot complete the job they came to do.
Unclear product, pricing or fulfilment information can create friction before an order is placed.
Most relevant to Home, garden & outdoor 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.
The window for seasonal categories is narrow. A site that wobbles in peak does not get a second peak that year.
Five things, in order.
Delivery is not just a list of features. The order matters, because the wrong sequence can turn technical dependencies into business risk.
- 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 foundation around the operational logic the business already depended on, without resetting what already worked.
- 03Brought product data into one governed workstreamProduct information, enrichment and catalogue structure were treated as a delivery workstream that enabled the commerce change.
- 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.
Systems, one operational truth.
Where this could have gone wrong.
Measurable, not adjectival.
The useful proof is not a bigger adjective. It is the project shape, the systems involved, the trading model supported and, where available, the numbers recorded from the work.
What the client said.
A client quote should support the case study, not carry it. The project story still needs to stay grounded in the work that was delivered.
iWeb were able to deliver the project within six months, from discovery to launch. With new features, an updated interface, and refreshed content, Gardening Direct now offers a more engaging, feature rich, user-friendly shopping experience for our customers.”
What moved into support.
A project like this does not stop mattering at launch. The same catalogue, account, integration and trading logic has to keep working once real customers and internal teams are using it.
The project did not end when the platform went live.
Support mattered because the home, garden and outdoor 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.
Surfaces from the live project.
These screens show where the operational work becomes part of the customer, account buyer or internal team experience.
Projects with a similar shape.
A gardening commerce platform rebuilt around seasonal catalogue depth, search and checkout journeys.
Garden retail trading supported by stronger search activity and updated add-to-cart activity.
An agricultural retail platform built around rural trade customers and seasonal purchasing.
Agriculture and country retail commerce implementation.
A multi-territory bulb and plant platform built around search, localisation and seasonal trading.
International plant retail supported by stronger search-led trading and mobile customer sessions.