Web · Client work / Case study
W Furniture: many suppliers, one product catalog
A client web project for a Clovis furniture retailer, bringing supplier product data together into one commerce-style browsing experience.
Contribution
Website development, supplier-data scraping, and catalog aggregation
One catalog
A multi-supplier product range
Supplier aggregation / illustration
Project context
McKay built a website and supplier-data aggregation workflow for W Furniture. Product information was collected from the retailer's suppliers and brought into a shared catalog so the range it could sell was visible in one place.
The linked store website currently shows a business landing page. The diagram illustrates the delivered catalog project, not the current public page or a live product feed.
From supplier data to product discovery
- 01Collect supplier product data
- 02Bring listings together
- 03Present a shared catalog
- 04Explore the retailer's range
01
The brief: show what the store can offer
A furniture retailer's offering can extend well beyond the pieces a customer sees on the showroom floor. W Furniture wanted a website that brought its suppliers' products together, giving the business one place to present the range it could sell. The project joined two kinds of work: collecting product data from supplier sites and turning that collection into a usable web catalog.
02
The collection layer: turn separate sources into a shared resource
McKay scraped product information from the client's suppliers and consolidated it for the site. That made the supplier network the source of the catalog, rather than requiring the retailer to author every listing from scratch. The core contribution was connecting those separate product sources to one retailer-facing presentation: data collection on one side, a useful browsing destination on the other.
03
Design considerations: consistency across different sources
Supplier aggregation is more than a visual design problem. Different catalogs can describe similar products in different ways, so a shared browsing experience needs a coherent way to present the information. Product identity, naming, grouping, and the distinction between a product and its variations are important considerations in this kind of work. The broader lesson is that the quality of a catalog depends on both the information brought into it and the way that information is presented.
04
The web experience: discovery before transaction
The delivered experience was commerce-like: a place to see the products the store could sell across its suppliers. The scope described here centers on catalog discovery, rather than payment processing or real-time inventory. Bringing the range into one place gives the website a practical role in the shopping conversation, connecting what a customer can explore online with what the retailer can offer.
05
The result: one destination for a broader product range
The delivered work connected supplier-data collection with a storefront-style website. For the retailer, the value was a consolidated view of its offering; for someone browsing, the intended benefit was exploring that range without having to know which supplier carried each product. The case study demonstrates both the data work behind a catalog and the web experience built around it.
Delivered outcomes
- A client website with a commerce-style product catalog.
- Supplier product data collected and consolidated for the retailer.
- A single place to browse products the store could sell across its supplier range.
More in web
Have a similar problem to solve?
Discuss your project