# Catalog correction referral brief template | SourceX

Canonical: https://refer.sourcex.si/resources/catalog-correction-workflows-referral-brief-template
Last updated: 2026-11-04

A company introduction about catalog correction workflows is a one-page brief the catalog operations head can approve: the company's size and country, the business task, which correction records exist and since when, rough volumes, the PIM and marketplace accounts that hold them, any documented access deadline, the one unresolved question about exports, and who can authorize a licensing discussion. It shares no product file, tracker export or seller account access. Below is the template, then a completed Illustrative example.

This brief is part of the [catalog correction workflows guide](/guides/workflow-catalog-correction-workflows). Use it after you have spoken with the catalog operations head and before you contact the executive who can say yes.

## Template: eleven lines to fill in

Each line takes a short answer. Keep the wording the company would use, and write "unknown" rather than guessing.

1. **Company:** sector, country, years operating, full-time headcount at peak.
2. **Business task:** in one sentence, what the corrections are for (for example, fixing product records rejected by marketplaces and the templates that caused them).
3. **Records:** which classes exist: PIM version history, saved marketplace rejections with issue codes, correction tickets, template or rule change logs, resubmission dates, dated feed files.
4. **Coverage:** the year each record class starts, and any gap from a migration or a reset of version history.
5. **Volume:** approximate active products and logged rejections, with who estimated them.
6. **Systems:** the PIM, the commerce platform, each marketplace seller account, and the tracker or ticket tool.
7. **Outside contributors:** whether an agency ran corrections, and whether manufacturers supplied descriptions or images.
8. **Unresolved question:** the single biggest unknown about whether the history can be exported intact.
9. **Access deadline:** a documented date when a system's access ends, or "none known".
10. **Decision-maker:** the executive who can authorize a licensing discussion, and the sponsor.
11. **Not shared:** a line confirming that no files, exports or account access are included.

## How to get each line right

The lines that most often go wrong are 3, 4 and 8. A few notes help.

| Line | Common mistake | Better entry |
|---|---|---|
| 3. Records | "Product data" | "PIM version history, rejection tracker with issue codes, correction tickets" |
| 4. Coverage | "Several years" | "PIM since 2020; tracker since 2021; earlier corrections in spreadsheets" |
| 5. Volume | An exact rejection count nobody checked | "A few thousand logged rejections, per the catalog operations head; not verified" |
| 8. Unresolved question | Five open questions | One: "whether the retiring PIM exports full version history or only current values" |
| 10. Decision-maker | The PIM administrator | "COO, with the catalog operations head as sponsor" |

Line 3 deserves care because a PIM can log a great deal: in Akeneo, each product version carries its author, a timestamp and the old and new values. Writing "version history with author and before-and-after values" tells a reviewer every fix is traceable. Line 8 is often about files, since Akeneo's scheduled exports do not keep earlier versions of an exported file unless a naming pattern is set. And because a marketplace API reports the issues a listing has today, ask where past rejections were written down.

## Completed brief (Illustrative)

Illustrative. A fictional housewares brand; every line was approved by its catalog operations head.

1. **Company:** housewares brand, Canada, 13 years operating, about 140 full-time employees at peak.
2. **Business task:** correcting product records rejected by marketplaces and fixing the title templates that caused them.
3. **Records:** PIM version history, a marketplace operations tracker with issue codes, correction tickets, a template change log, resubmission dates.
4. **Coverage:** PIM since 2020; tracker since 2021; earlier corrections in spreadsheets, by the head's estimate.
5. **Volume:** about 9,000 active products; a few thousand logged rejections, per the head; not verified.
6. **Systems:** one PIM being retired in favor of the commerce platform's built-in catalog; two marketplace seller accounts that stay; a ticket tool.
7. **Outside contributors:** manufacturers supplied some descriptions and images; one agency ran a seasonal refresh.
8. **Unresolved question:** whether the retiring PIM exports full version history, or only current values.
9. **Access deadline:** PIM subscription ends June 30.
10. **Decision-maker:** the COO, with the catalog operations head as sponsor.
11. **Not shared:** no product file, tracker export or seller account access.

The deadline and the unresolved question point at the same risk: if version history does not survive the PIM's retirement, the before-and-after record of each correction is gone. That is a reason to introduce the company promptly, not a reason to advise it to copy data.

## Checks before the brief leaves your hands

- **Size and history:** 50+ full-time employees at peak (contractors excluded) and a documented operating history.
- **Geography:** 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.
- **Rights flagged, not answered:** line 7 names supplier and agency content so counsel and SourceX's rights review can start there.
- **Right signer:** line 10 names someone who can authorize. The [who can license tree](/questions/who-can-license-catalog-correction-workflows-records) helps check.
- **Paperwork:** you have signed the Channel Partner Agreement. The first valid introduction within the 90-day window is credited when the company submits a verified application.

To screen the company before writing the brief, use the [ecommerce referral screening worksheet](/resources/a-referral-screening-worksheet-for-ecommerce-businesses). For a worked rejection that shows what the records look like in practice, read the [catalog exception case](/guides/catalog-correction-workflows-exception-examples). Distributors with large catalogs often sit in portfolios covered by [specialty distribution private equity](/industries/specialty-distribution-private-equity), and a [data catalog versus data inventory](/compare/data-catalog-vs-data-inventory) comparison explains why the brief lists record classes rather than products. More sectors are on the [ecommerce industry page](/industries/ecommerce) and the [industries hub](/industries).

## 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.

When the catalog operations head has approved all eleven lines, [register as a partner](/register), confirm the brand on [who qualifies](/who-qualifies), and read the [program terms](/terms) before you send the brief to the decision-maker.

## Sources

- https://refer.sourcex.si/terms
- https://help.akeneo.com/serenity-take-the-power-over-your-products/serenity-enrich-your-product
- https://help.akeneo.com/v7-importexport-data/v7-schedule-and-automate-your-product-imports-and-exports
- https://developer-docs.amazon.com/sp-api/docs/manage-listings-issues
