# Marketplace appeal metadata packet template | SourceX

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

A referral partner can describe a seller's marketplace-appeal-to-resolution records with one row per system: what it holds, over which dates, how it links to the SKU, who owns it and what is still unknown. None of that requires opening an appeal, a test report or a helpdesk ticket. Add three names, the person who runs appeals, the person who controls product documents and the executive who could authorize a licensing discussion, and the packet is ready to hand to SourceX.

It is part of the [marketplace-appeal-to-resolution guide](/guides/chain-marketplace-appeal-to-resolution), which explains why the chain matters.

## The blank packet: nine fields per system

Copy this table and fill one column per system. Every field is answered by the company in words or numbers, never with a file.

| Field | What to write | Where the answer comes from |
|---|---|---|
| System | Seller Central, ERP, helpdesk, shared drive, or other | Marketplace operations lead |
| Object types | Listing issues, appeals, responses; item records, test reports; tickets | Admin view of each system |
| Date span | Earliest and latest year the company states it holds | System owner, from go-live dates |
| Rough volume | Appeals a year, SKUs with documents, tickets a year, if known | Company estimate, marked as such |
| Link to the product | SKU, ASIN, ERP item number, or free text | How staff key each record |
| Version handling | Whether superseded documents are kept with effective dates | Quality or compliance owner |
| History capture | Whether past issue changes were logged by the company | Marketplace operations lead |
| Owner | Role that administers the system | Org chart |
| Unknown until review | Anything the company has not checked | The partner, honestly |

Two fields need care. **History capture** exists because Amazon's developer documentation centers on a product page's present problems and alerts when they change, and notes that some problems have no defined type. Years of appeal history may exist only if the brand logged those alerts or kept its own case record. **Version handling** decides whether an appeal that cited a superseded document can ever be explained, as the [before-and-after reading](/guides/marketplace-appeal-to-resolution-missing-context) shows.

## A filled packet (Illustrative)

A fictional 140-person kitchenware brand that sells mostly on Amazon, keeps product records and supplier documents in its ERP, and handles marketplace cases in Zendesk. Every value is invented.

| Field | Marketplace portal | ERP item records | Helpdesk | Shared drive |
|---|---|---|---|---|
| Object types | Listing issues, appeals, responses | Specifications, supplier test reports, revision labels | Case tickets, draft appeal text, decisions | PDFs attached to appeals |
| Date span | Since the account opened in 2016 | Since ERP go-live in 2018 | Since 2020 | Varies |
| Rough volume | About 40 appeals a year, company estimate | About 900 active SKUs with documents | Unknown | Unknown |
| Link to the product | SKU and ASIN | Item number mapped to product code | Product code in a ticket field since 2022; free text before | File names, if consistent |
| Version handling | Not applicable | Revisions kept from 2021; overwritten before | Not applicable | Unknown |
| History capture | Team case log since 2020 | Not applicable | Ticket audits | Not applicable |
| Owner | Marketplace operations lead | Quality manager | Marketplace operations lead | Unknown |
| Unknown until review | How far back appeal history can be retrieved | Whether pre-2021 files match what was submitted | Whether every case has a ticket | Whether files match ERP revisions |

Read the packet as a whole: a joined appeal trail is plausible from 2021 or 2022, when revisions were kept and tickets carried the SKU, and thinner before. That is a useful, honest description. If the helpdesk is Zendesk, ticket audits keep a read-only history of updates and comments, which supports the "History capture" cell; the [Zendesk systems page](/systems/zendesk) covers that tool more broadly.

## The three names

- **Who runs appeals:** the marketplace operations lead, who knows the portal, the helpdesk and the team's habits.
- **Who controls documents:** often the quality or compliance manager, who knows whether revisions are kept and dated.
- **Who can authorize:** the CEO, or the owner in an owner-run seller. Only this person can agree to explore licensing.

Write roles, not personal contact details, until the sponsor agrees to an introduction.

## What stays outside the packet

The packet describes records; it never carries them. Keep these out entirely:

- Appeal text, marketplace responses or screenshots of the portal.
- Test reports, certificates or any supplier document, even redacted.
- Ticket content, customer names or order numbers.
- Revenue lost during a suppression, or any sales figure per SKU.

If the company offers a sample "to help," decline and explain that SourceX handles any record review under its own agreement with the company. This is the difference between describing an inventory and moving data, explored in [data catalog vs data inventory](/compare/data-catalog-vs-data-inventory).

## Handing the packet over

Send the packet with your registration. Mark each unknown as unknown rather than guessing, note who answered each column, and add one line on why the chain is interesting: for example, "revisions kept since 2021, with at least one appeal that cited a superseded report." The [completeness checklist](/resources/marketplace-appeal-to-resolution-completeness-checklist) turns the same answers into a pass, partial or fail score if you want a second view.

Check the company tests first: 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 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 funds any reward separately and never deducts it from the company's payout; see [rewards](/rewards). For how direct licensing differs from listing data for sale, see [selling data directly vs through a marketplace](/compare/sell-data-directly-to-ai-companies-vs-marketplace) and [data broker vs data marketplace](/compare/data-broker-vs-data-marketplace).

## 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 you can fill most of the packet in one call and name the executive who would take the next one, [register as a partner](/register), confirm the seller against [who qualifies](/who-qualifies) and read the [terms](/terms) before you send it.

## 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
- https://refer.sourcex.si/rewards
