Item data insights16 Oct 20264 min read

The hours are the smallest number

Mika AhoProfessional Enricher

Count the hours someone spends researching missing item fields and you have a number. It is the smallest one.

It is also the only cost anyone measures. Whatever the estimate per gap, it is the good case: the search runs longer whenever the right source is not in the first few results. Multiply that by a year of new item codes and it is a role nobody was hired for. But that role is not where the money goes.

Where the cost lands

Illustrative example
4410-0218DescriptionV-BELT SPA1250 PUMP STATION 3Mfr. part number—Name and dimensions—Net weight0,00Customs code8413 91 00inheritedsearched, not found
4410-0391DescriptionV-BELT SPA 1250 PS3Mfr. part number—Name and dimensions—Net weight0,00Customs code8413 91 00inheritedThe same belt, opened again
4410-0218
  1. Same part under three codes.

    Three stock levels and three prices for one part; the volume discount is never claimed.

    Lands in procurement and working capital.

  2. The wrong variant.

    Ordered from the description and returned, while a maintenance stop waits.

    Lands in maintenance and downtime.

  3. Net weight zero.

    The shipment waits until someone weighs the part; freight is quoted on a guess.

    Lands in logistics, every shipment.

  4. Customs code inherited.

    An audit re-rates years of declarations: duty, interest, possibly a penalty.

    Lands in finance and the customs team.

  5. No name, no dimensions.

    The part cannot be listed or quoted, so the order goes to whoever answers first.

    Lands in aftermarket revenue.

  6. Empty fields at migration.

    The new system inherits every gap, and fixing it there costs more.

    Lands in the migration programme.

Take the belt above. Two codes, one part, and the second one exists because the first could not be found: no part number, no dimensions, a name that only makes sense at pump station 3. Every empty field on that row has a place downstream where it costs more than the search would have, and each place belongs to a different budget.

None of these is dramatic on its own. A belt is ordered twice, a shipment waits a day, a declaration carries the code of a similar part. The pattern is that each one is small, repeats with every item, and is paid by a department that did not create the gap and cannot see its cause. That is why the hours stay the only number on the table: they are the only cost with a name on it.

It compounds

An engineer who cannot find the part that already exists specifies a new one. A buyer who cannot tell two codes apart keeps both. So the register that is hardest to search is also the one that grows fastest, and every new row arrives with the same empty fields as the last.

What a Start shows

The Start does not estimate these costs; it counts them on your own items. You send 100 to 200 codes as they are today and within days you see which fields are empty, inherited or wrong, how often, and what the source would have been. Then you decide what each gap is worth to fix, with the number in front of you instead of the hours.

Key takeaways
  • The research behind a missing field is the smallest cost it causes.
  • The larger costs land downstream, usually in another department’s budget, which is why nobody adds them up.
  • It compounds: a part nobody can find gets opened again, so the hardest register to search grows fastest.

Further reading

Item dataItem masterSupply chain
Mika Aho
Professional Enricher

More than 20 years turning data and AI into business value and working solutions. CEO of Data Design, previously at Silo AI. At inRecipe he leads the product and the Starts.

See which of these apply to your items.

  1. 1Send 100 to 200 items as they are today.
  2. 2Within days you see which fields are empty, inherited or wrong, and how often.
  3. 3One hour to walk it through together.
Book a Start

Your ERP, PDM or PIM stays where it is. A file export is enough to start.

Estimate the research hours alone →