Marketplace catalog operations workshop / 6 MIN READ
Match the sellable item before creating another catalog page
Product-to-ASIN match dossier with identity conflicts and attach/new/escalate decision.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-07
A seller offer belongs to a specific product identity. Finding a similar page is not enough to establish that the item in the warehouse is the product represented by that page.
What you will leave with: Product-to-ASIN match dossier with identity conflicts and attach/new/escalate decision.
Use this when
- A reseller is adding a product already sold by other sellers.
- A barcode search returns several plausible catalog matches.
Not a GTIN allocation guide or permission to create a duplicate page, attach an unrelated item or bypass brand approval.
Separate the shared product from your offer
Amazon’s listing guidance separates the product detail page from sellers’ offers, which contain their commercial terms. It describes matching an offer to an existing page when the product is already present, with brand or category approval sometimes required. These facts were checked on 7 November 2026; verify the intended store and current account requirements before implementation.
Build a match dossier before preparing persuasive listing copy. Identify the actual packaged unit being sold: maker, model, edition, regional configuration, included components and quantity. Keep condition and seller fulfillment information beside that identity rather than using them to disguise a different product. The marketing team needs an evidence-backed destination, not whichever existing page already has appealing reviews.
Compare candidates against the item in hand
For each candidate, record the ASIN, marketplace and decisive matching evidence. Use authorized supplier records, manufacturer specifications and packaging identifiers. A title resemblance or matching photograph can help locate a candidate, but neither resolves a different connector, revised component or regional edition. Mark unknown values as unresolved instead of silently interpreting them in the most convenient way.
Compare all identity-bearing differences together. A two-unit pack is not established as the same sale unit merely because each component carries a familiar barcode. Conversely, a different seller price does not establish a new product. If the catalog page contradicts trustworthy product evidence, preserve the discrepancy and ask the catalog owner to investigate. Do not repair the mismatch by changing what the proposed offer claims to contain.
Make the match decision before the listing decision
Use three outcomes: supported existing match, supported need for a new product record, or unresolved identity. The second outcome needs evidence that the catalog investigation was adequate; one unsuccessful text search is a weak basis. Record search methods and rejected candidates so another operator does not restart the same ambiguous search and reach a different conclusion.
Check listing authority separately after identifying the product. Having authentic stock does not by itself prove that every category or brand process is satisfied. Route required approvals to the authorized owner. If the intended marketplace has a different catalog record, verify the local identity and configuration rather than carrying an ASIN assumption across stores. Retain the reasoning even when the operational result is to wait.
Accept the destination customers will actually encounter
Before a campaign uses the listing, have a reviewer compare the proposed offer with the shared page and the physical sale unit. Ask what a buyer would reasonably expect to receive from the complete page. Check especially model suffixes, accessories and pack counts that can be lost in condensed titles. Record the exact candidate and review date, not a search-results screenshot alone.
Keep the match dossier linked to the internal SKU record. A later supplier substitution or packaging change should reopen the relevant identity questions. Do not assume that an earlier match covers every replenishment bearing a similar description. The accepted output is a defensible relationship between one sale unit and one marketplace product, with commercial offer details and outstanding approvals clearly separated.
Make the reasoning concrete.
A fictional office-supply reseller receives a compact label printer. Search results show a visually identical printer bundled with a rechargeable battery, while the received unit includes only a mains adapter. The older bundle page has extensive reviews, making it an attractive campaign destination.
Attach to the familiar page
Opening: Use the bundle page and explain the missing battery in the seller notes.
Hypothesis: The offer can benefit from an established destination.
Risk: Customers may rely on the shared bundle description rather than the seller qualification.
Resolve the sale-unit identity
Opening: Compare manufacturer records and packaging, then look for the exact mains-only configuration.
Hypothesis: The listing decision follows the product actually supplied.
Risk: The correct record or required approval may not yet be available.
The team rejects the bundle match, records why and leaves the campaign destination unresolved until the mains-only product is identified. It does not create a duplicate merely to escape the ambiguity or borrow the bundle’s reviews.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Unit
What exact configuration and quantity will arrive?
Candidate
Which ASIN and marketplace are being evaluated?
Evidence
Which manufacturer or packaging facts establish the match?
Conflict
Which difference prevents a supported match?
Outcome
Is this an existing match, new-record case or unresolved identity?
Watch for the wrong conclusion.
- Choosing the page with the strongest reviews instead of the exact item.
- Treating seller price as a product-identity difference.
- Creating a new page after only one unsuccessful search.
Your next action
Prepare one match dossier using a fictional sale unit and two plausible catalog candidates; explain why one must be rejected.
Sources & scope
Workflows, worksheets and fictional examples are original editorial analysis. Sources support only specifically attributed platform facts. Controls vary by marketplace and can change. This lesson authorizes no account changes, transactions, communications or disclosures and claims no measured business result.
- Amazon: How to create Amazon product listings →Primary marketplace documentation · Supports: Supports the distinction between shared detail pages and seller offers, existing-page matching and possible brand/category approval. The identity dossier is original analysis.