# Marketplace appeal completeness scorecard | SourceX

Canonical: https://refer.sourcex.si/resources/marketplace-appeal-to-resolution-completeness-checklist
Last updated: 2026-11-04

A marketplace-appeal-to-resolution trail breaks when evidence cannot be dated against the decision it was meant to change. The clearest case is an appeal that cites a superseded product document: unless the ERP or document store kept revision dates, nobody can later show the cited file was already out of date. Six checks score whether a seller's records survive that test, covering SKU tagging, dated attempts, document revisions, denials, reasoning and history capture, each answered from configuration and habit rather than content.

This scorecard is one of three tools in the [marketplace-appeal-to-resolution guide](/guides/chain-marketplace-appeal-to-resolution).

## Scoring: two points, one point, zero

Give each check a number. **2** means the record is kept, dated and joinable for most of the years the seller would discuss. **1** means it is kept for some years, some SKUs or some team members. **0** means it is not kept, or the person answering cannot say. Twelve points is the ceiling.

Points are for practice, not features. A helpdesk that can hold a SKU field earns nothing until the seller confirms the team fills it in, and from which year. Note who answered each check. A written answer such as "revisions kept since 2021, per the quality manager" is worth more than any total.

## The six checks

| Check | What breaks without it | How to ask it at metadata level | 2 points | 1 point | 0 points |
|---|---|---|---|---|---|
| 1. SKU tagging | Tickets titled "pan appeal" cannot be joined to a product page | Do case tickets carry the product code in a structured field? | Field used on nearly every case | Since a recent year, or free text only | No SKU on tickets |
| 2. Dated attempts | Only the final listing status survives | Are issue, submission and decision dates kept anywhere outside the portal? | Each attempt dated in the team's own log | Some dates, or recent cases only | Dates live only in the portal, if at all |
| 3. Document revisions | A new file overwrites the old one, so a stale citation is invisible | Are superseded test reports and certificates kept with effective dates? | All revisions kept and dated | Kept from a recent year, or without dates | Overwritten |
| 4. Denials kept | The second appeal survives, the first is lost | Is every attempt recorded, including rejected ones? | Every attempt kept with its outcome | Denials kept sometimes | Only successes remembered |
| 5. Reasoning | Strategy was decided in chat or by phone | Where does the team discuss why evidence was chosen or changed? | In ticket comments with dates | Partly in tickets, partly in chat | Nowhere written |
| 6. History capture | Old problems vanish once fixed | Did the brand log each change over time? | Alert or case log for years | Log for recent months | No log |

Check 6 matters more than it looks. Amazon's developer documentation centers on a product page's present problems and on alerts when they are created, fixed or updated, and it notes that some problems have no defined type. A portal shows the current state; years of earlier problems usually exist only if the brand logged them. Check 5 is easier to score when the helpdesk is Zendesk, because its ticket audits keep a read-only history of every update, including comments and field changes.

## The superseded-document test

The six checks score each record type. This test scores the joins between them in one question, asked of the quality or compliance owner: "For the last appeal that failed, can you say which document revision was cited and which revision was current that day?"

| Answer | What it shows | Effect on the score |
|---|---|---|
| Both revisions named, with dates | Revisions, submissions and dates all join | Confirms checks 2 and 3 |
| Cited revision known, current one uncertain | Submissions kept; revision dates missing | Drop check 3 to 1 point |
| Neither known | The trail shows outcomes without reasons | Drop checks 3 and 5 to 0 |
| "That never happens" | Untested assumption | Mark unknown and ask for the next failed appeal |

A pass on this test is worth noting. Internal decisions with their reasons are the kind of work that is [thin in public training data](/questions/what-data-is-missing-from-ai-training), and a trail that can explain its own failures holds exactly that. The [before-and-after reading](/guides/marketplace-appeal-to-resolution-missing-context) shows one such failure with and without its context.

## A scored seller (Illustrative)

A fictional 160-person cookware seller: Amazon as its main channel, an ERP holding item records and supplier reports, and Zendesk for marketplace cases. Answered by the marketplace operations lead and the quality manager.

| Check | Points | Note from the call |
|---|---|---|
| 1. SKU tagging | 2 | SKU field required on marketplace tickets since 2021 |
| 2. Dated attempts | 2 | Team case log records each submission and decision |
| 3. Document revisions | 1 | Revisions kept with dates since 2022; overwritten before |
| 4. Denials kept | 2 | Log includes every attempt |
| 5. Reasoning | 1 | Ticket comments for most cases; some decided in chat |
| 6. History capture | 0 | No issue log before the case log began |
| Superseded-document test | Confirms 2 and 3 | Last failed appeal: cited revision B, revision C current |

Eight of twelve points. Described honestly, that is a joined appeal trail from 2022, with reasoning for most cases and no portal-side history before the team's own log. The answers also fill most of the [metadata packet](/resources/marketplace-appeal-to-resolution-metadata-packet).

## Before you introduce the seller

The person who can authorize a licensing discussion is the CEO, or the owner in an owner-run seller, not the marketplace lead who answered the checks. The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

SourceX licenses business data directly from companies and pays them for it. We are their counterparty from agreement through delivery and payment. Partners never ask for or handle raw records, and they sign the Channel Partner Agreement before introducing. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. SourceX licenses business data directly from companies and pays them for it. We are their counterparty from agreement through delivery and payment.](/resources/ai-training-data-marketplace) and [data broker vs data marketplace](/compare/data-broker-vs-data-marketplace); sector context is on the [ecommerce page](/industries/ecommerce).

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the scorecard shows an appeal trail you can describe with its gaps named, [register as a partner](/register), confirm the seller against [who qualifies](/who-qualifies) and read the [terms](/terms) before you introduce its sponsor.

## Sources

- https://developer-docs.amazon.com/sp-api/docs/manage-listings-issues
- https://developer-docs.amazon.com/sp-api/docs/notification-type-values
- https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits/
- https://refer.sourcex.si/terms
