Skip to content
Our workOperationsApplication briefing

Product Naming & Stock File

From messy supplier product data to a clean stock-control file.

Workflow illustration

Workflow illustration, not real products. Purchase templates and supplier product data arrive as uneven rows. Each row is checked against the existing SKU and master-data list, and one matches an existing item. The naming, category and validation rules then straighten the rows into aligned name, category and SKU columns. The duplicate and an ambiguous item are held for review rather than guessed, and the remaining rows become a clean stock file. The stock team resolves the exceptions and approves the file for import or further checks.

People stay in control

Ambiguous mappings and new-rule cases are held for human review rather than guessed. Stock or buying teams remain responsible for approving new classifications and downstream use.

The challenge

New product information can arrive from different suppliers and teams with inconsistent names, descriptions, SKU structures and fields. Manual checking creates re-keying, inconsistent records and friction between buying, goods-in and stock control.

What we built

The application turns inconsistent incoming product information into a structured master-data workflow. It reads purchase templates, supplier product information and existing SKU lists, applies the organisation's naming, category and validation rules, flags ambiguous or duplicate items and creates a clean stock file ready for downstream checking or import.

Created as one of three connected applications for a retail reference architecture.

What it connects

  • Purchase templates and supplier product data
  • Existing SKU and master-data lists
  • Naming, category and validation rules

The difference it makes

  • Names, descriptions and category fields are brought into one agreed structure before they move into downstream stock processes.
  • Supplier information is transformed through repeatable rules instead of being manually rebuilt for each downstream file.
  • Records that do not fit the agreed rules are separated for review rather than silently forced into the wrong structure.
  • The output is a consistent stock-ready file, with the exceptions and decisions already visible.

Business profile

Sector
Retail
Team
Buying and stock control
Workflow
Supplier product data to a clean stock file

A standardised product file with ambiguous items surfaced for review, making the hand-off into stock control easier to trace.

Inputs and outputs

Inputs

  • Purchase templates and supplier product data
  • Existing SKU and master-data lists
  • Naming, category and validation rules

Outputs

  • Standardised product names and descriptions
  • Mapped SKU and category fields
  • Exception and duplicate flags
  • Clean stock-control import or output file