BOM Cleaner: part number matching for messy BOM lists

BOM Cleaner does. It reads the manufacturer part number out of each line however it was written - inside a description, split by spaces, with a brand prefix or a misspelled brand - and looks it up exactly against the Automa.Net catalogue. A line is settled only when the code matches a manufacturer record; anything else is flagged for review with the reason on the row, so lists from different BOMs and supplier quotes come back in one standard format.

No. Matching is deterministic: codes are normalised and looked up against the catalogue, and a row is only settled when the evidence supports it. Where a code has to be read out of surrounding text, what comes back is a verbatim fragment of your own line, checked against the original before it is used. A line that gives nothing to read comes back unmatched rather than filled in.

Because something specific stood in the way: the match sits inside a longer code, two codes on the line point at different products, the brand only agreed at family level, the confidence fell below the threshold. Whichever it was, that reason is written on the row and you can filter the whole file by it.

It starts from the route that found the product - a manufacturer's main part number, an alternative code, a designation code or a search fallback - and is then adjusted by brand agreement, competing candidates, the strength of the code itself and whether a longer code on the same line went unmatched. Every factor that reduced it is reported as a named code on that row.

Your original columns, plus 21 columns of findings: the matched product and brand with their identifiers, the match type, the confidence, every code and brand read from the line, all competing candidates, the status, the warnings and notes, and - if you enabled it - the category with the route that assigned it. You can export everything, only your selection, or only the codes that matched nothing.

That is what matching does. Codes are normalised before lookup - separators, punctuation and case are stripped - so 6ES7193-6TP00-0TP1, 6ES71936TP000TP1 and sie6es7193 6tp00 0tp1 all reach the same article. What lands in the output is the manufacturer's own spelling of the code, not the one that happened to be in your file, which is what makes a BOM list from five suppliers comparable to itself.

BOM Cleaner is a module you run yourself on a file, as often as you like. Warehouse Golden Record is a service for a full MRO material master: deduplication across the whole catalogue, criticality segmentation, lifecycle flags and an output shaped for your ERP. Same underlying matching, different scope of work.

It is processed to match and enrich your records, and nothing else. It is not sold, not traded and not shared with other members. Access control, logging and retention follow ISO 27001 practices, and you can ask for your data to be removed at any point.