{"section":"tutorials","requestedLocale":"en","requestedSlug":"understanding-vtex-matcher-scoring","locale":"en","slug":"understanding-vtex-matcher-scoring","path":"docs/en/tutorials/suggestions/understanding-vtex-matcher-scoring.md","branch":"main","content":"VTEX Matcher is a tool used by marketplaces to analyze offers submitted by sellers and accelerate their cataloging process.\n\nVTEX Matcher analyzes SKUs by matching information from a seller's offer to items already listed in the marketplace catalog. Here are the attributes analyzed in an offer:\n\n- SKU name  \n- Product name  \n- Brand  \n- Category  \n- EAN or Ref ID  \n- Height  \n- Width  \n- Length  \n- Weight  \n- Image name  \n- Image URL  \n- Specifications  \n\n## Score \nReceived offers are queued to be analyzed by VTEX Matcher. Received SKUs that belong to the same product follow a prioritization rule: SKUs are analyzed in order of arrival.\n\nVTEX Matcher assigns a score to each attribute that matches existing product information in the marketplace. Then all points are added together, generating a final score for the offer.\n\nThe final score determines the product status as follows: Approved, Denied, or Pending. \n\n## Cataloging\nCheck the table below to see the statuses generated by different scores and their corresponding actions.\n\n> ℹ️ The maximum VTEX Matcher score for automatic cataloging is 95. Scores greater than 95 require manual cataloging.\n\n| Score         | Status   | Scenario                                                                                                                                                         | Action                                                                                                                                                                                                                                                                                             |\n|---------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 95 points     | Approved | Correspondence between `productName`, `brandName` and at least two of the following attributes: `EAN`, or `refId`, or `skuName`.                                 | **Associate to an existing SKU:** VTEX Matcher [automatically catalogs](/en/tutorial/sugerindo-e-aprovando-skus/#cataloging-options) items. The information about the associated item is not transferred, so the system uses attributes of the existing SKU.                  |\n| 90 points     | Approved | Correspondence between `productName`, and at least two of the following attributes: `EAN`, or `refId`, or `skuName`.                                             | **Associate to an existing SKU:** VTEX Matcher [automatically catalogs](/en/tutorial/sugerindo-e-aprovando-skus/#cataloging-options) items. The information about the associated item is not transferred, so the system uses attributes of the existing SKU.                  |\n| 85 points     | Approved | Correspondence in   `productName` and `brandName`.                                                                                                               | **Associate to an existing product:** VTEX Matcher [automatically catalogs](/en/tutorial/sugerindo-e-aprovando-skus/#cataloging-options) items. The system transfer additional information about this item to the product, complementing the information that already exists. |\n| 80 points     | Approved | Correspondence in   `productName`.                                                                                                                               | **Associate to an existing product:** VTEX Matcher [automatically catalogs](/en/tutorial/sugerindo-e-aprovando-skus/#cataloging-options) items. The system transfer additional information about this item to the product, complementing the information that already exists. |\n| From 31 to 79 | Pending  | The offer does not have an equivalent `productName` in the marketplace.                                                                                          | **Classify an offer as pending:** when VTEX Matcher classifies an offer as pending, the marketplace needs to review and catalog it via the [Received SKUs module](/en/docs/tutorials/manual-sku-cataloging).                                                         |\n| From 0 to 30  | Denied   | The offer was sent without  `imageName`  `imageUrl`, `EAN`, `width`, `height`, `length`, `weight`, `productName`, `skuName`, `brandName`, `category`, or `refId`. | **Deny offer:** offers automatically denied by VTEX Matcher are removed from the queue and can only be viewed via the [Marketplace API](https://developers.vtex.com/docs/api-reference/marketplace-apis).                                                                       |\n\n## Configuring Matcher\n\nThe criteria described in this article are standard. You can configure VTEX Matcher differently through the [automatic approval API](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/configuration/autoapproval/toggle).\n\nThe VTEX platform also allows you to use other matchers developed by internal teams or partners.\n\nBy doing so, matchers will work in parallel. This means that they do not replace each other but work in a complementary way. Whenever a product or SKU is sent to the marketplace, all matchers will be notified to start the evaluation process. Similarly, for a SKU to be stated as denied, it must be rejected by all active matchers in the store.\n\n## Learn more \n- [Cataloging received SKUs](/en/docs/tutorials/manual-sku-cataloging)\n- [API documentation for configuring Matcher](https://developers.vtex.com/vtex-rest-api/reference/getautoapprovevaluefromconfig)"}