Item master data cleansing that respects variants and units
The same item can appear under several descriptions or supplier codes. Similar names can also describe different sizes. A custom item workflow can standardize usable fields without treating every near match as the same product.
How could item data be harmonized and checked for duplicates?
A project can combine formatting rules with item-specific evidence: manufacturer and part number, GTIN where available, dimensions, unit and pack quantity. Exact identifiers can narrow candidates; conflicting variants stay separate. Similarity scores help reviewers find candidates rather than prove interchangeability.
Item rules that need a business definition
Descriptions, units and attributes
Agree naming patterns, whitespace, abbreviations, unit labels, categories and required technical attributes. Converting a unit label is different from converting quantities; dimensional conversions need explicit rules.
Duplicate candidates with context
Compare manufacturer numbers and available identifiers alongside dimensions, material, variant and packaging. Do not merge two products just because their descriptions resemble one another.
Controlled corrections
Preview field changes and proposed duplicate groups. Retain source item IDs, exclude obsolete or locked items as agreed and require separate approval for any consolidation.
How it works
- 1
Select an item scope
Choose item groups, number ranges or a limited sample. Confirm whether the task covers an ERP item master, a PIM catalogue or a supplier feed.
- 2
Define the item standard
Agree preferred descriptions, unit mappings, mandatory attributes and matching evidence. Decide which fields may be filled, replaced or left unchanged.
- 3
Review differences and matches
Inspect before-and-after fields and duplicate candidates. Confirm whether a pack of ten and a single unit represent distinct saleable items.
- 4
Publish approved master data
Apply only supported, approved fields in the agreed system and report successes, exclusions and errors. Test source restrictions before a larger rollout.
Same bolt, or a different pack?
“HEX BOLT M8 X 30” and “Hex bolt M8×30” could share a manufacturer number. One record may still represent 100 pieces while the other represents one. A custom rule can normalize the description and flag the relationship while blocking an automatic merge across pack sizes.
Item processing is a custom implementation option. Stock movements, valuations, price lists, bills of materials and substitutions are outside this example unless explicitly scoped; identifier matches are not product certification.
Frequently asked questions
Which item fields could be standardized?
Does SAP or Salesforce connectivity already include items?
Can exact duplicates be processed automatically?
Will cleanup change stock or financial values?
What should your data process do differently?
Use the Contact page to describe your systems, record types and the problem you want to solve. We will agree the scope, access and acceptance criteria before implementation.