Guide
Catalog data does not decay slowly. It decays on a schedule.
Every stale supplier catalog has a specific cause — an export cycle, an expired price list, a withdrawn reference, a mapping nobody revisited. Each one is fixable once it is named.
Operating model guide
What an electronic supplier catalog has to carry.
A catalog is not a product list. To be safe to order from, it has to carry the item identity a buyer will recognise, the identity your systems will accept, the unit the price applies to, the price that applies to this customer, the period that price is valid for, and whether the item still exists.
Most catalog problems are one of those six fields being absent, wrong, or silently out of date. Naming which one turns a vague data quality complaint into a fixable defect.
02The cycle
The life of one catalog line.
Catalog data is not maintained once. It goes round this loop continuously, and every place it can stop is a place where a buyer eventually sees a wrong price.
- 01Supplier
The line is published
Reference, description, unit, packaging, price and availability leave the supplier’s system.
What has to be true
The supplier owns the data, because the supplier is the only party who knows it.
Where it usually breaks
A one-off export, sent by email, that nobody is responsible for repeating.
- 02◇ DecisionKelqio
It is validated
Required fields, unit coherence and price validity are checked before publication.
What has to be true
A line that cannot be bought correctly should not be publishable.
Where it usually breaks
Silent acceptance: the file loads, the line is wrong, and nobody finds out until ordering.
↳ Rejected · Supplier
Named, not silently dropped
The line goes back with the field that failed. A catalog that quietly loses lines is worse than one that refuses them.
- 03Kelqio
The contract is attached
The customer’s negotiated price, assortment and packaging are applied to the line.
What has to be true
One line can carry different conditions for different customers.
Where it usually breaks
A single public price list used for every customer, checked manually afterwards.
- 04Buyer
It is distributed and used
The line appears in search, in a cart, then in a requisition and an order.
What has to be true
The fields that mattered at publication are the fields that arrive in the order.
Where it usually breaks
Data that degrades in transit — units lost, packaging dropped, description truncated.
- 05Kelqio
It expires and is refreshed
Validity dates and last-update state make an ageing line visible before it is used.
What has to be true
Expiry is a property of the data, not a note in someone’s calendar.
Where it usually breaks
Catalogs quietly serving last quarter’s prices, discovered at invoice reconciliation.
03Decay
Six ways supplier catalog data goes wrong.
The export cycle
A catalog refreshed quarterly is wrong for most of the quarter, and everyone knows it except the buyer looking at it.
Expired conditions
A price list with no explicit end date keeps being applied. Validity has to be data, not a note in the contract.
Withdrawn references
Items the supplier no longer sells stay orderable, and the failure surfaces at confirmation instead of selection.
Unit and packaging mismatch
A price per unit against an order per box is a mapping defect that produces invoice disputes months later.
Identity drift
Supplier references, internal item codes and manufacturer references stop lining up, and matching becomes manual.
The shadow spreadsheet
Wherever a maintained spreadsheet sits beside the catalog, the catalog is not the source and everyone behaves accordingly.
04Operating model
The supplier maintains it. The layer distributes it.
Catalog quality at scale is not achieved by a central data team retyping supplier files. It is achieved by making the supplier the maintainer and making publication have consequences.
- Nordwerk Industrie
- Customers
- Groupe Vallis
Groupe Vallis — MRO 2026
Published- items in catalog
- 1 284
- Last update
- 14/04/2026 08:31
- Price list
- VALLIS-MRO-26
- Validity
- 01/01/2026 → 31/12/2026
Delivered to
- Groupe Vallis — ERP
- Groupe Vallis — Procurement
- Kelqio Catalog
Update once — every connected buyer sees it.
Incoming orders
| Order | Site | Lines | Value | Status |
|---|---|---|---|---|
| PO-88412 | Lyon 03 | 4 | 5 782,50 € | New |
| PO-88396 | Nantes 01 | 11 | 12 044,00 € | Acknowledged |
| PO-88361 | Lyon 03 | 2 | 918,20 € | Shipped |
| PO-88307 | Metz 02 | 7 | 3 260,75 € | Invoiced |
- 01
One product set per supplier
Maintained once by the supplier rather than reassembled per customer.
- 02
Customer views derived from it
Each customer’s assortment and pricing are views over that single set, not separate copies.
- 03
Validity as structured data
Price periods have start and end dates the system can act on.
- 04
Freshness as a monitored metric
The age of the data buyers see is visible, so decay is caught before it reaches an order.
Catalog management questions.
- Who should own supplier catalog data?
- The supplier should maintain it, because they are the only party who knows first when something changes. The buying organization owns the mapping, the contracted assortment and the acceptance rules.
- How often should a supplier catalog be updated?
- Frequency is the wrong frame once catalogs are connected. What matters is that a change at the supplier reaches the buyer before the buyer orders against the old value.
- What about suppliers who cannot produce structured data?
- They maintain their catalog directly in the supplier workspace. The absence of a supplier IT capability should not exclude them from the catalog.
Next step
Bring your supplier list. We’ll show you the flow.
A working session with our team, using your systems and your supplier mix — not a generic slide deck.
- 01
Where your suppliers sit today: connected, semi-connected, or not at all
- 02
How each channel would route through Kelqio into your ERP and procurement platform
- 03
What connecting the next twenty suppliers would actually involve
Enterprise integration product. No credit card, no self-serve trial — a conversation with someone who knows procurement systems.