Content & data

Product record matching

Compare two product records by model, capacity, and pack count.

For ecommerce teams and catalog data maintainers

Jev AI playground

Checking availability…

Text

472 / 50,000

Try different inputs · Product record matching

Load an input to edit it. Tokens are used only when you run it.

Normal input

Normalize only the explicitly permitted naming and capacity differences.

Ambiguous input

A two-unit pack is different even when the drive model and capacity match.

Missing information

Missing capacity prevents a same-product judgment; do not guess the variant.

Questions2

choiceApply the matching rule. A conflicting required attribute makes the records different even when their titles are similar. Missing attributes are not assumed equal.⌄

Question

Answer options

Yes / NoAre manufacturer, model, storage capacity, and pack count supplied for both records?⌄

Question

Advanced: edit JSON

Edit or paste a question configuration.

Runs use input tokens and are saved to your account.

Results

Your answers will appear here.

Add your text and questions, then run Jev.

Probabilities express model confidence, not a guarantee of correctness.

Set up this template

Find duplicate listings while keeping meaningful product variants separate.

What to provide

Two product records, required matching attributes, and any allowed unit or naming normalization.

Provide both records and the attributes that define a match.
State allowed normalization, including unit conventions.
Review missing attributes before merging records.

Outputs and rules

match · choice

Whether the records identify the same defined product variant.

Apply the matching rule. A conflicting required attribute makes the records different even when their titles are similar. Missing attributes are not assumed equal.

same_product: All required attributes agree after the explicitly allowed normalization.
different_product: At least one required attribute has a known conflicting value.
insufficient_information: No known conflict is shown, but a required attribute is missing or ambiguous.

complete_attributes · Yes / No

Whether the comparison includes every required attribute.

Are manufacturer, model, storage capacity, and pack count supplied for both records?

Try different inputs

Normal input

Normalize only the explicitly permitted naming and capacity differences.

Matching rule: A match requires the same manufacturer, model, storage capacity, and pack count. Ignore punctuation and word order. A known conflicting attribute means different; a required missing attribute means insufficient_information. Record A: Northline PocketDrive P8, 1 TB, graphite, 1 drive. Record B: Northline P8 PocketDrive — graphite — 1000 GB SSD — single unit. Catalog convention: For this catalog, 1 TB and 1000 GB refer to the same listed storage capacity.

Ambiguous input

A two-unit pack is different even when the drive model and capacity match.

Matching rule: Compare manufacturer, model, storage capacity, and pack count. Record A: Northline PocketDrive P8 1 TB, single unit. Record B: Northline PocketDrive P8 1 TB, twin pack.

Missing information

Missing capacity prevents a same-product judgment; do not guess the variant.

Matching rule: Compare manufacturer, model, storage capacity, and pack count. Record A: Northline PocketDrive P8 1 TB, single unit. Record B: Northline PocketDrive P8, single unit.

Use the result

Use same-product results to suggest duplicates for review. Keep conflicting variants separate and request missing specifications before a merge.

Limits to keep in mind

This compares the product details you provide. It doesn’t verify seller claims or guess missing specifications.