Match States: Matched, Unmatched and Not Eligible
The matching workflow in Unified Catalog is organized around product states.
These states define whether a product is already connected, still waiting for a match, or cannot currently participate in matching.
Understanding these states helps users know what action is possible for each product.
The Big Picture
Not every product in the Catalog is in the same stage of the matching process. EVA uses match states to separate products that are already linked, still unmatched, or not eligible for matching.
The Main Match States
Matched Products
Matched products are products that have already been connected across channels.
When a match is applied:
- a unified product is created
- the linked Amazon and Shopify items move into the matched area
- EVA treats them as one connected product entity
These products no longer appear in unmatched sections unless the match is removed.
Unmatched Amazon ASINs
These are Amazon products that are currently not linked to a Shopify variant.
They remain available for:
- Smart Matching Suggestions
- manual matching
- future review
This state means the Amazon product exists in EVA, but no cross-channel connection has been confirmed yet.
Unmatched Shopify Variants
These are Shopify variants that are currently not linked to an Amazon product.
Like unmatched Amazon products, they remain available for:
- Smart Matching Suggestions
- manual matching
- future review
This state means the Shopify item is present in the catalog, but not yet part of a unified product.
Not Eligible Products
Not Eligible products are products that cannot currently be matched.
This state usually means the product does not meet the conditions required for matching in the current workflow.
A Not Eligible product remains visible in the catalog, but is excluded from active matching actions.
The Logic
EVA classifies products into states based on their current relationship status.
The basic logic is:
- if a valid connection exists, the product is Matched
- if no connection exists and matching is possible, the product is Unmatched
- if the product cannot currently participate in matching, it is Not Eligible
This allows the matching interface to stay organized and action-oriented.
Why This Matters
Without state logic:
- users would not know which products need action
- matched and unmatched items would mix together
- ineligible products could create confusion in the workflow
With state-based organization:
- users can focus on products that still need matching
- matched products remain clearly separated
- products that cannot be matched do not disrupt the process
Key Value Pillars
Clear workflow visibility
Users can immediately see which products still require action.
Better matching control
Matched, unmatched, and restricted items are separated logically.
Cleaner catalog management
Ineligible products do not interfere with active matching tasks.
Pro Insight
The most actionable area in Unified Catalog is the unmatched product set.
That is where users should focus first, because those products still need either Smart Matching review or manual matching.