All case studies

Retail & E-commerce / Illustrative case study

From scattered supplier files to a store-ready catalogue

How a growing retailer could prepare consistent product records without making its sales team manage every spreadsheet, image and missing specification.

Illustrative scenarios showing proposed workflows and expected outcomes.

01 / The challenge

Where the work gets stuck.

New products arrive in several formats. Model names vary between supplier files, images are stored separately, and some specifications are missing. The retail team repeatedly stops listing work to clarify details. A tidy spreadsheet alone would not solve incorrect product matches or unsupported descriptions.

02 / How Wek would help

A defined process, with people in control.

Wek would begin by agreeing the scope, quality standards, systems access and approval rules with the retailer. The following steps illustrate how delivery could be organized.

  1. 01

    Define the catalogue standard

    Agree required fields, categories, variants, image requirements and the destination import format. Separate fields Wek can prepare from changes the retailer must approve.

  2. 02

    Prepare records from approved sources

    Extract and normalize product information, match identifiers and images, and draft descriptions grounded in supplier evidence. AI could assist with extraction and drafting; validation rules would check required fields.

  3. 03

    Review uncertainty

    An operator would investigate duplicates, conflicting specifications and unclear image matches. Missing information would enter a supplier follow-up queue rather than being filled with assumptions.

  4. 04

    Approve and deliver

    Quality-check the records, present exceptions for resolution and deliver an import-ready file or listing drafts. Publish only where the retailer has granted the appropriate authority.

03 / The workflow

From input to a usable output.

Catalogue workflowIllustrative example
Supplier filesProduct imagesExisting listings
Structured product recordReviewed
Product nameConsistent naming
Category & attributesMapped to your structure
Images & specificationsMatched and checked
PublishingClient approval required

Import-ready files · Listing drafts · Quality reports

An exception in practice

Two supplier files give different capacities for the same model. The record would be held for clarification, with both sources attached for review.

04 / Expected outputs & benefits

What this approach would deliver.

  • Structured product records and matched image references
  • Import-ready files or listing drafts
  • A missing-information and exception log

The intended benefit is a repeatable catalogue process with clearer approval status and less repeated checking by the retail team.

How a pilot could be measured

  • Required-field completeness
  • First-pass quality and rework
  • Time from complete inputs to approved output

Measures and targets would be agreed against the retailer’s starting position. No performance results are claimed for this scenario.

Explore Product & Catalogue Operations

Explore another workflow.

Let’s put structure around the work.

What workflow is taking too much of your team’s time?

Show us the process. We’ll explore how to structure, operate or automate it more effectively.

Discuss a Workflow