Different records.
One product identity.
Names change from supplier to supplier. The product does not. Connect equivalent records to one catalog identity, with the evidence and source context intact.
Pascore / Source recordsIllustrative exampleSelect a record to compare
Industrial drive
MPN 4820
- Voltage
- 400 V
- Power
- 4 kW
Resolve the identity.
Then build the catalog.
A supplier record describes a product from one source. A catalog identity brings equivalent records together. Keep those two layers distinct, so every new file does not become another set of duplicates.
Without a shared identity
Separate entries, scattered updates, repeated content.
With a shared identity
One product connected to its original source records.
The 230 V variant stays separate until its identity is resolved.
A match needs evidence.
Not just a similar name.
Compare identifiers and structured attributes in context. A manufacturer reference can establish a strong connection; a conflicting specification can be a reason to stop and review.
| Signal | Supplier A | Supplier B | Comparison |
|---|---|---|---|
| MPN | 4820 | 4820 | Consistent |
| Voltage | 400 V | 400 V | Consistent |
| Power | 4 kW | 4 kW | Consistent |
| Name | Industrial drive 4kW | Motor drive, 400V | Different wording |
Both records carry the same MPN. Use it with manufacturer context and the other available signals.
Signals shown here are illustrative. Matching rules depend on the identifiers and data available in your catalog.
Uncertainty has
a place to go.
Keep an ambiguous candidate in review. Compare the original record with the catalog, inspect the mismatch, and make a deliberate decision before linking them.
- Keep conflicting specifications visible
- Preserve the original source record
- Resolve the candidate without a forced match
230 V
400 V
Voltage does not match
230 V and 400 V may identify different variants. Keep these records separate while you confirm the specification.
One product.
Every source still there.
A shared identity should not erase where information came from. Follow a catalog value back to its source and keep supplier context available as records change.
- Original value
- Industrial drive 4kW
Source relationships remain attached to the product, even when a field uses a value from another source.
A clear identity.
A stronger starting point.
Enrichment, pricing and channel delivery all rely on knowing which product you are working with. Resolve that first, and carry the context into the next step.
A few practical questions.
What is product matching?
Product matching is the process of determining whether records from different sources represent the same underlying product.
What is product deduplication?
Product deduplication identifies multiple catalog records that should represent one product identity and prevents unnecessary duplicate entries.
Does Pascore delete supplier records after matching?
No. The product model is designed to retain source context and provenance while presenting one governed product identity.
What happens when Pascore cannot determine a match?
Uncertain cases can remain available for review instead of being automatically treated as confirmed matches.
Why is product matching important for distributors?
Distributors frequently receive overlapping assortments from many suppliers. Without identity resolution, the same product can appear several times with fragmented prices, descriptions, availability and supplier relationships.
Continue the product workflow
Bring the duplicates.
See the connections.
Walk through your supplier records and matching requirements with the Pascore team.
Request a demo