Match supplier line descriptions to internal product codes
Resolve inconsistent supplier descriptions against your item master. Prepare suggested product matches while keeping uncertain identities in a review queue.
How this works
Matching a supplier line to the correct internal item is an identity problem. Similar wording can hide a different material, size, revision or package quantity. Conversely, the same product can have a supplier abbreviation and an entirely different internal description.
Use AI to extract context and propose candidates, then compare decisive attributes with explicit rules. The first deliverable is a reviewed crosswalk. It should not silently create items, replace discontinued parts or approve invoice payment.
Before you start
Item master snapshot
Obtain active and discontinued item IDs, manufacturer references, units and distinguishing technical attributes.
Supplier identity
Use a stable supplier identifier rather than relying only on a printed company name.
Review policy
Define which exact identifiers allow a proposed match and who resolves conflicting specifications.
Prepare the inputs
- supplier_lines
- Required
line ID, source text and document reference
Preserve the original description, quantity and unit; flag unreadable characters.
- item_master
- Required
versioned item rows
Require unique internal IDs and effective status; identify missing attributes.
- approved_crosswalks
- Optional / conditional
supplier code to internal ID mappings
Include approval date, applicable version and known exceptions.
- match_rules
- Required
ordered identity and conflict checks
Separate decisive identifiers from weak similarity signals.
Implementation, step by step
Preserve and normalize the line
- Extract supplier code, manufacturer code, description, size, material, revision and packaging when present.
- Normalize typography and known abbreviations without discarding the raw value. Keep quantity and package size as different fields.
Checkpoint: Every normalized value can be traced to its original line.
Retrieve a bounded candidate set
- Start with an applicable approved crosswalk or exact manufacturer reference. Otherwise search the item master using lexical and semantic hints.
- Use supplier context to narrow candidates, but never let supplier identity override a conflicting technical attribute.
Checkpoint: Each line has candidate IDs and the reason each was retrieved.
Compare discriminating attributes
- Create a side-by-side matrix for the attributes that distinguish candidates, such as dimensions, grade, voltage or revision.
- Apply approved unit conversions mechanically; an unknown value remains unknown rather than matching everything.
Checkpoint: Conflicts and missing discriminators are visible per candidate.
Assign review status
- Recommend a match only when the agreed identity rules are met and no decisive conflict exists.
- Hold multiple plausible candidates, discontinued products, substitutions and unclear packaging for the appropriate owner.
Checkpoint: The proposed status includes its factual basis and any alternatives.
Validate and store the crosswalk
- Have the owner review the source line and candidate comparison, then record accepted, rejected or unresolved decisions.
- Retain the document, rule version and approval date with the mapping; apply a correction to similar historical lines only after checking scope.
Checkpoint: Approved mappings can be reused without losing their conditions.
Prepare downstream handoff
- Export the reviewed mapping with original quantity and unit untouched. Explain remaining exceptions to the receiving team.
- Keep product identification separate from price, order and invoice reconciliation; each has its own acceptance rules.
Checkpoint: No unresolved line is presented as a confirmed internal item.
Decisions along the way
A supplier code was reused
Check manufacturer, revision and effective date; retire the stale mapping if confirmed.
A near match differs in package size
Hold the identity or conversion until a product owner confirms the relationship.
What you will produce
item-crosswalk.csv
CSVConfirmed and proposed mappings with explicit review status.
Include: supplier_id · source_line · supplier_code · internal_item_id · match_basis · status · reviewer
match-exceptions.csv
CSVA resolvable queue for ambiguous item identities.
Include: source_line · candidate_ids · conflicting_fields · missing_evidence · next_owner
Check the result
- Sample high-confidence matches for wrong sizes, revisions and units.
- Verify repeated imports reuse stable source-line keys.
- Confirm rejected candidates do not remain in the approved crosswalk.
When something goes wrong
OCR confuses a critical code character
Request a clearer source or manual reading; do not resolve by similarity alone.
No master item fits
Raise a new-item or substitution review rather than fabricating an internal ID.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: identify a supplier line marked SEAL-20 EPDM x10.
Inputs
The master contains S20-E, a 20 mm EPDM seal sold individually, and S20-N, a 20 mm nitrile seal. The document does not explain whether x10 denotes quantity or packaging.
Expected result
Suggest S20-E on material and size evidence, but hold the quantity interpretation. Retain x10 verbatim and ask the buyer to confirm packaging before any inventory import.
Run a small pilot
Start small
One supplier with a mix of exact references, abbreviations and known ambiguous lines.
Record the baseline
Compare against independently reviewed item mappings and record manual review time.
Agree success criteria
Agree a maximum wrong-match rate and required hold behavior before allowing operational reuse.
Stop or revise
Stop reuse when item-master versions or supplier coding conventions change unexpectedly.
Keep the scope clear
- A product match does not approve a substitute, stock movement or payment.
- No model confidence score replaces evidence for a decisive product attribute.
Check before using
A purchasing or product-data owner confirms ambiguous matches before posting inventory or finance records.
Business activities
- Manage product catalogs and storefronts
- Plan inventory and production
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Supplier document lines · Internal item master · Approved product crosswalks
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow