{"slug": "ai-product-matching-for-tracking-competitor-prices", "title": "AI product matching for tracking competitor prices", "summary": "Apify's AI Product Matcher Actor uses a machine learning model to identify the same product across competing stores despite differing titles, demonstrated on 19 Hifiman listings from Headphones.com and 98 from Audio46 that produce 1,862 possible pairs. The tool takes two scraper-collected datasets, maps fields such as title, price and description through JSON attribute mappings, and outputs a predicted_match flag of 1 or 0 plus predicted_scores for each pair. Users choose a precision setting for more reliable matches or recall for broader but less accurate suggestions.", "body_md": "To price your products competitively, you need to know what other stores charge for them. But that can be tricky when competitors use different names and descriptions for the same item.\n\nYou’d need to manually check model numbers and specifications just to confirm a match. Doing that for a few listings is manageable, but the work piles up across hundreds or thousands of products.\n\n[AI Product Matcher](https://apify.com/equidem/ai-product-matcher) on Apify helps automate that process.\n\n## What is AI product matching?\n\nAI product matching uses product details to identify the same item across different stores. For example, “Hifiman Sundara Closed-Back Headphones” and “Hifiman Sundara Closed-Back Planar Magnetic Headphones” describe the same model, despite their different titles.\n\nAfter a scraper collects the listings, AI Product Matcher uses a machine learning model to find matching products across your datasets.\n\n## How to compare competitor prices with AI Product Matcher\n\nThe example below uses **19 Hifiman listings from Headphones.com and 98 from Audio46**. Comparing every listing in the first store with every listing in the second creates **1,862 possible pairs**. The matcher processes those pairs and marks the ones it considers matches.\n\n### Step 1. Add the sample datasets\n\nThe product listings for this example were collected with [Shopify Scraper](https://apify.com/autofacts/shopify) from [Apify Store](https://apify.com/store). You can use the resulting datasets directly to try the matcher without scraping the data yourself.\n\nOpen [AI Product Matcher](https://apify.com/equidem/ai-product-matcher), select **Try for free**, and sign in to Apify Console. In the **Input** tab, find **Separate datasets** and replace the example IDs with these:\n\n| Input field | Sample data | Dataset ID | \n|---|---|---|\n| Dataset IDs from shop 1 | 19 Headphones.com listings | `hDS89Nwie71TfmGRz` | \n| Dataset IDs from shop 2 | 98 Audio46 listings | `n4shucMvwVjRdEKz7` | \n\nLeave **Pair dataset IDs** (**Pair datasets**) empty. The matcher will automatically create product pairs from the two store datasets.\n\n### Step 2. Map the correct product fields\n\nThe sample datasets store product names under `title`, while the matcher expects a field called `name`. Using Attribute mapping here will resolve this issue.\n\nPaste the JSON below into **Input attributes mapping**:\n\n```\n{\n  \"eshop1\": {\n    \"id\": \"title\",\n    \"name\": \"title\",\n    \"price\": \"price/current\",\n    \"long_description\": \"description\"\n  },\n  \"eshop2\": {\n    \"id\": \"title\",\n    \"name\": \"title\",\n    \"price\": \"price/current\",\n    \"long_description\": \"description\"\n  }\n}\n```\n\nHere, `eshop1` represents Headphones.com, and `eshop2` represents Audio46. The path, `price/current`, tells the matcher to read the `current` value inside the `price` object. Product titles also serve as IDs because they are unique within each store’s dataset.\n\nTo display product names, URLs, prices, and available variant details alongside each matching decision, paste the following JSON into **Output attributes mapping**:\n\n```\n{\n  \"eshop1\": {\n    \"name_a\": \"title\",\n    \"source_a\": \"source\",\n    \"price_a\": \"price\",\n    \"variants_a\": \"variants\"\n  },\n  \"eshop2\": {\n    \"name_b\": \"title\",\n    \"source_b\": \"source\",\n    \"price_b\": \"price\",\n    \"variants_b\": \"variants\"\n  }\n}\n```\n\nFields ending in `_a` show Headphones.com’s product details, while those ending in `_b` show Audio46’s, so you can compare their listings side by side.\n\n### Step 3. Run the matcher\n\nUnder **Precision/recall tradeoff** (**Model configuration**), select **precision** for more reliable matches. **Recall** finds more potential matches but also returns more incorrect suggestions.\n\nClick **Start** and approve the Actor’s Full permissions when prompted.\n\nOnce the run shows **Succeeded**, open **Output** to see the product pairs and their predictions:\n\n- **`predicted_match`:**` 1` means the Actor predicts a match, and`0` means it doesn’t.\n- **`predicted_scores`:** Higher scores indicate stronger support for a match. Use` predicted_match` to filter the results.\n\nThe test returned **1,862 pairs**. Checking the predictions against the reviewed product data gave these results:\n\n| Result | Pairs | \n|---|---|\n| Correctly matched the same model | 9 | \n| Correctly rejected different products | 1,824 | \n| Incorrectly matched different products | 2 | \n| Missed pairs of the same model | 26 | \n| Unresolved after review | 1 | \n| **Total** | **1,862** | \n\nThe matcher suggested 11 matches: nine were correct, but two incorrectly paired **Ananda Stealth with Edition XS**.\n\n### Step 4. Compare the matched products’ prices\n\nThe output contains all 1,862 product pairs the matcher evaluated. Before comparing prices, narrow it to the nine confirmed matches by filtering out rejected pairs and the two incorrect suggestions:\n\n1. Click **Export** (top right of the run page), choose**Excel** , and select**Download** .\n2. Open the downloaded file, click any cell in the data, then select **Data → Filter** to add filter arrows to the column headings.\n3. Click the arrow beside `predicted_match` , uncheck**Select All** , select**1** , and click**OK** . You should now see the**11 pairs** the Actor predicted as matches.\n4. To exclude the two incorrect pairs, click the arrow beside `name_b` , choose**Text Filters → Does Not Contain** , enter`Edition XS` , and click**OK** .\n\nYou should now see **nine rows**, each pairing a Headphones.com listing with an Audio46 listing for the same model. You can compare what the stores charge by reading the two price columns in that row:\n\n- **`price_a/current`:** Headphones.com’s listed price.\n- **`price_b/current`:** Audio46’s listed price.\n\nThese values are in cents, so divide each by `100` to get dollars. For example, `12900` becomes **$129.00**. The table below compares **three of the nine confirmed pairs**, with prices converted to dollars.\n\n| Product | Headphones.com listed price | Audio46 listed price | Audio46 minus Headphones.com | \n|---|---|---|---|\n| Sundara Closed-Back | $129.00 | $129.00 | $0.00 | \n| Ananda Nano | $319.00 | $319.00 | $0.00 | \n| EF400 | $299.00 | $529.00 | $230.00 | \n\nMatching the EF400 listings revealed a **$230 difference between the stores’ listed prices**. With your own catalog, these comparisons can help you easily spot where competitors charge more or less for the same product and decide which prices to review.\n\n## Try it with your own catalog\n\nFrom 117 listings across two stores, AI Product Matcher checked 1,862 possible pairs and flagged the closest matches. That gives you a starting point for comparing what your competitors are charging for the same products.\n\nTo [try AI Product Matcher](https://apify.com/equidem/ai-product-matcher) with your catalog, collect each store’s listings in a separate Apify dataset. Then replace the sample dataset IDs and adjust the mappings if your data uses different field names.\n\n## Frequently asked questions\n\n### How much does AI Product Matcher cost?\n\nThe run in this tutorial cost **$0.021, or about two cents, to compare 1,862 product pairs**, excluding scraping costs. AI Product Matcher uses [pay-per-usage pricing](https://apify.com/equidem/ai-product-matcher/pricing), so your cost depends on the computing and storage resources each run consumes.\n\n### How can I compare larger product catalogs?\n\nScrape each store into a separate Apify dataset and use the same setup shown in this tutorial. To compare your store with multiple competitors, keep your dataset under **Dataset IDs from shop 1** and run a comparison with each competitor’s dataset under **Dataset IDs from shop 2**.\n\n### Can the matcher recognize the same product in different colors?\n\nYes. The matcher is [trained to treat different color variants as the same product](https://apify.com/equidem/ai-product-matcher#how-accurate-is-the-matcher). For example, it considers a black phone and a white version of the same model a match.", "url": "https://wpnews.pro/news/ai-product-matching-for-tracking-competitor-prices", "canonical_source": "https://blog.apify.com/product-matching-ai-pricing-intelligence-web-scraping/", "published_at": "2026-11-18 12:21:38+00:00", "updated_at": "2026-11-18 13:13:02.791219+00:00", "lang": "en", "topics": ["ai-products", "ai-tools", "machine-learning"], "entities": ["Apify", "AI Product Matcher", "Headphones.com", "Audio46", "Hifiman", "Shopify Scraper"], "also_reported_by": [], "takeaway": "Mapping source fields like title to the matcher's expected name field via JSON attribute mappings lets the Actor compare two store datasets and flag matches with predicted_match (1 or 0) and predicted_scores, with a precision setting favoring reliable matches over recall.", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/ai-product-matching-for-tracking-competitor-prices", "markdown": "https://wpnews.pro/news/ai-product-matching-for-tracking-competitor-prices.md", "text": "https://wpnews.pro/news/ai-product-matching-for-tracking-competitor-prices.txt", "jsonld": "https://wpnews.pro/news/ai-product-matching-for-tracking-competitor-prices.jsonld"}}