FOR DISTRIBUTORS & WHOLESALERS

Product catalogue workflows
for distributors.

Supplier spreadsheets rarely agree on product names, units or specifications. A focused cleanup workflow can prepare consistent records and a visible list of questions for your team.

PROPOSED PILOT / CATALOGUE PREPARATION

One supplier file.
One agreed product template.

Map product information into consistent fields, preserve source references and flag gaps before your team approves it for publishing or import.

Browse fixed-scope micro-solutions →

A deliberately narrow starting scope

One spreadsheet or CSV from one supplier.
Up to 100 product rows in an agreed template.
Up to eight agreed fields, such as SKU, name, unit and specification.
One cleaned output file and exception list.
One review round with your catalogue owner.

Image sourcing, live stock synchronisation and publishing into an ERP or store are separately scoped.

A CONTROLLED WORKFLOW

Useful structure without invented details.

Agree the field rules
Define units, identifiers and required attributes. Preserve original values where a conversion or interpretation is uncertain.
Prepare and flag
Standardise agreed formatting, surface potential duplicate SKUs and collect missing specifications for review.
Approve before import
Your team checks descriptions, prices and product claims before any catalogue goes live. The pilot does not change a production stock record.

Another useful starting point

An enquiry triage pilot can turn an incoming request into a list of requested items, quantities and unanswered questions. Availability and commercial commitments still require staff confirmation.

Describe your enquiry workflow →

Measure the right things

Agree required fields and check a sample against the original file. Review how duplicates, missing units and ambiguous product descriptions are handled before expanding the scope.

This is a proposed service workflow, not a reported client deployment.

START WITH ONE REPEATED TASK

Tell us where the work gets stuck.

A short description is enough to begin. We will define inputs, outputs, exclusions and review requirements before agreeing a build.

Open the Problem Desk →

Explore the proposed pilot

Review the product catalogue pilot boundary →

Scope and data handling are agreed before a project starts. Historical client work is listed separately from these demonstrations.

SUPPLIER CATALOGUE DATA CLEANUP

What to check before importing a supplier catalogue

Keep a copy of the source file and map its columns to an agreed product template. A clean import starts with explicit field rules, not guessed descriptions.

SKU: preserve identifiers as text, including leading zeroes. Flag duplicates instead of merging them automatically.
Unit and pack size: retain both the supplied value and the intended field. A box of 12 is not the same as one item.
Description and specification: standardise agreed formatting while retaining the source wording needed for review.
Price and currency: record them separately and flag blanks or mixed currencies. Do not silently convert them.
Review status: separate approved rows from missing, conflicting or uncertain records.

Example: a pack-size ambiguity

A supplier row says “gloves, pack 10” but lists the unit as “each”. The output should preserve both source values and ask the catalogue owner to confirm the selling unit. Publishing a guessed conversion could create a tenfold quantity error.

The proposed pilot prepares a review file and exception list. It does not update live stock, change selling prices or write directly into an ERP.

See the catalogue preparation sample · Review the fixed pilot boundary · Describe a catalogue problem

Product catalogue workflowsfor distributors.

One supplier file.One agreed product template.