# Catalog correction system map: PIM to marketplace | SourceX

Canonical: https://refer.sourcex.si/guides/catalog-correction-workflows-records-across-systems
Last updated: 2026-11-04

Five joins hold a catalog correction case together: product to listing, listing to rejection, rejection to correction ticket, correction to template change, and correction to accepted resubmission. The usual keys are the SKU mapped to a marketplace item ID, the SKU plus the issue date, a ticket ID that quotes the SKU or issue code, and a family or template ID. Each system holds only one side of each join, so a PIM export alone cannot reconstruct the case.

This system map is part of the [catalog correction workflows guide](/guides/workflow-catalog-correction-workflows). It answers one question: across the PIM, the marketplace portal, the operations tracker and the template library, which identifiers let someone rebuild a correction from start to finish, and who owns each system?

## The systems and what each one holds

Four systems usually share the work. Each holds records the others never see.

| System | Record it holds | Linking key | Typical owner |
|---|---|---|---|
| PIM | Product versions with author, timestamp, old and new values | SKU; family ID | Catalog operations head |
| Marketplace portal | Listing status, issue code, severity, attribute named | Marketplace item ID mapped to SKU; issue date | Ecommerce or marketplace director |
| Operations tracker | Correction ticket, assignee, decision note | Ticket ID quoting SKU or issue code | Catalog operations head |
| Template or rules library | Title templates, attribute mappings, family rules | Template or family ID; change date | Catalog operations head |
| Feed exports | Files sent to each channel | File name and export date | IT or the ecommerce team |

Read across a row and the pattern is plain: no system holds more than one side of a join, and the owner of one system rarely knows what the next one keeps. The catalog operations head usually comes closest, because the tracker and the template library both sit with that team.

## The five joins and what breaks each one

| Join | Key | What breaks it |
|---|---|---|
| Product to listing | SKU mapped to marketplace item ID | SKUs renamed during a consolidation without a cross-reference |
| Listing to rejection | SKU plus issue date | Rejections read on screen and never saved |
| Rejection to ticket | Ticket ID quoting the SKU or issue code | Tickets describing "the big pan" in free text only |
| Ticket to template change | Family or template ID plus date | Templates rebuilt from scratch on a new platform |
| Correction to outcome | SKU plus resubmission date | Acceptance never logged; only current listing status kept |

Feed exports are a sixth, optional join. They show what was sent to each channel on a given day. If old files survive with dates in their names, they are a useful snapshot; if each run replaced the last, note the gap.

## Chronology: the join nobody configures

Keys say which records belong together. Timestamps say in what order things happened, and that order is what turns a set of records into a case.

A PIM version is a fix only if its timestamp falls after the rejection and before the accepted resubmission. A template change explains a family-wide update only if its date precedes the bulk versions. Three things commonly destroy chronology:

- **Bulk re-imports.** If a consolidation re-imports all products on one day, every product appears created that day, unless the old version history is exported first.
- **Tracker migrations.** Moving tickets to a new tool can reset created dates to the import date.
- **Time zones.** Marketplace timestamps and PIM timestamps may be in different zones. Note which, so the order survives.

When describing a client's systems, record whether each source keeps original timestamps through migrations. That one fact often decides whether the joins hold.

## How much each side keeps, according to the vendors

The PIM is usually the richest side. Akeneo, as one example, logs every product version with the author or system, a timestamp and the old and new values, covering attribute, status, family, association and category edits. The marketplace side is thinner: Amazon's Selling Partner API reports the issues a listing has now, separating ERROR issues that block an update from WARNING issues that do not, and announces issue changes through notifications. So rejections from past years exist only where the brand captured them at the time, usually in its tracker.

## One fully joined case (Illustrative)

Illustrative. A fictional 260-person cookware distributor sells a 12-inch skillet on two marketplaces. The size attribute was stored as 30 in centimeters while the title template printed 12 inches, so the listing's size field read 30 and its title read 12, and a marketplace flagged the mismatch. Here is that case with every record placed in its system and joined by its key.

| Order | System | Record | Key used to join it |
|---|---|---|---|
| 1 | PIM | Version 7: size 30 cm, title "12 in Skillet" | SKU SK-12-NS |
| 2 | Marketplace portal | Error: size value conflicts with title, May 12 | Item ID mapped to SK-12-NS; issue date |
| 3 | Operations tracker | Ticket 9032 assigned; note: store sizes in one unit, convert in templates | Ticket quotes SK-12-NS and the issue code |
| 4 | Template library | Pan title rule now converts the stored unit | Family ID PANS; change date May 14 |
| 5 | PIM | Version 8: size unit corrected | SKU SK-12-NS; timestamp after step 2 |
| 6 | Marketplace portal | Listing accepted, May 15 | Item ID; resubmission date |
| 7 | PIM | Version 9 on 54 other pans, May 28 | Family ID PANS |

The SKU, ticket number and family ID are invented. The point is the shape: four systems, four kinds of key, and a date order that only holds if every timestamp survived. A different case, told step by step with who decided each move, is in the [worked exception case](/guides/catalog-correction-workflows-exception-examples).

## Questions that test whether the joins hold

Ask the catalog operations head these, and note the answers as metadata:

1. Do tickets reference the SKU or issue code in a field, or only in free text?
2. Were rejections saved at the time, and where?
3. Is there a cross-reference from old SKUs to new ones after any consolidation?
4. Does the PIM keep version history back to its rollout, or was it reset?
5. Are template and family changes logged with dates?
6. Is acceptance recorded, or only inferred from a live listing?

Two "no" answers do not rule a company out; they tell SourceX what to expect. The distinction between a [data catalog and a data inventory](/compare/data-catalog-vs-data-inventory) helps here: a partner lists systems, keys and owners, not products. For how marketplaces of training data generally work, see the [AI training data marketplace overview](/resources/ai-training-data-marketplace); for the same join problem in freight, see [logistics exceptions and their documented resolutions](/guides/how-to-identify-logistics-exceptions-and-their-documented-resolutions).

## Qualification and the open questions

The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, 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. When the map is filled in, carry its key facts into the [referral brief template](/resources/catalog-correction-workflows-referral-brief-template). More context is on the [ecommerce industry 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 a client's PIM versions, saved rejections and tickets still share keys and original timestamps, [register as a partner](/register), check the company on [who qualifies](/who-qualifies), and read the [program terms](/terms) before you introduce its catalog operations head.

## Sources

- https://help.akeneo.com/serenity-take-the-power-over-your-products/serenity-enrich-your-product
- https://developer-docs.amazon.com/sp-api/docs/manage-listings-issues
- https://refer.sourcex.si/terms
