This decision tree belongs to the catalog correction workflows guide. It gives a marketplace operations consultant one thing: a way to work out, from a few questions, whom to introduce and what to leave for later.
The tree, one question at a time
Follow each question in order. Each answer either moves you down the tree or tells you to stop and note a gap.
- Does the company have catalog correction records at all? Ask the catalog operations head whether PIM version history, saved marketplace rejections and correction tickets exist. If none were kept, stop: there is nothing to introduce.
- Who looks after them day to day? Usually the catalog operations head. That person becomes the sponsor: they explain the records and convene the decision, but rarely approve alone.
- Does anyone outside the company hold or contribute part of the history? If an agency ran corrections, or manufacturers supplied descriptions and images, mark those records as needing counsel review (branch A below).
- Does anyone below the CEO want to sponsor the case? An ecommerce or marketplace director, or the COO, often does. Either way, the CEO authorizes the discussion, so the path continues to the CEO.
- Is counsel involved? For most companies, yes. Counsel reviews seller terms, agency contracts and supplier content terms, and advises the CEO.
- Is the authorized person willing to be introduced? If yes, introduce them with the sponsor copied. If not, stop; a sponsor alone cannot carry the discussion.
A useful check at step 2: the Akeneo version history, for example, records the author or system for every change, so the sponsor can usually tell you who did the work. That shows who made the corrections. It says nothing about who can license them.
Roles on the tree, and where each one stops
| Role | What they know | Where they sit on the tree | Can they say yes? |
|---|---|---|---|
| Catalog specialist | Daily corrections and templates | Source of facts at step 1 | No |
| PIM administrator | Exports, version settings, user access | Side branch: technical facts only | No; access is not authority |
| Marketplace account administrator | Seller account settings, issue notifications | Side branch: technical facts only | No |
| Catalog operations head | Systems, history, approvals, any consolidation plan | Sponsor at step 2 | Rarely alone |
| Ecommerce or marketplace director | Channel strategy, marketplace relationships | Step 4, as a possible sponsor | No; can sponsor |
| COO | Operations and catalog budgets | Step 4, as a possible sponsor | No; can prepare the case |
| CEO | Decisions on company assets | End of the main path | Yes, usually with counsel |
| Counsel | Seller terms, agency and supplier contracts | Step 5, beside the signer | Reviews rights; advises the CEO |
Why administrators stop on a side branch: a PIM can be set to schedule and automate exports, and a seller account can pull a listing's current issues through the marketplace API. Those are capabilities. Neither tells you whether the company has decided to discuss licensing its data, and a partner should never treat an administrator's offer to "just send an export" as a step forward.
Branch A: when counsel or an outside party must sign off
Three situations send part of the history to counsel before any yes is meaningful.
| Situation | Why it matters | What to note |
|---|---|---|
| Manufacturer-supplied content | Descriptions and images may come under the supplier's own terms | Which fields the brand wrote and which it received |
| Agency-run corrections | The agency's contract decides who owns its working files and notes | Whether agency tickets sit in the brand's tools or the agency's |
| Marketplace messages | Seller terms may affect how captured rejection text can be used | Where rejections were saved and for which marketplaces |
None of these is a reason to stop. They are reasons to describe the records accurately so the rights review starts in the right place. The data rights explainer covers why rights come first.
Worked path (Illustrative)
Illustrative. A fictional 320-person outdoor equipment retailer in the UK lists tents, packs and footwear on three marketplaces.
- Step 1: the head of catalog operations confirms PIM history for six years, saved listing issues for four, and a ticket queue for fixes.
- Step 2: that head agrees to sponsor, and names the PIM administrator only as the person who knows export settings.
- Step 3: footwear brands supply their own copy and photos under wholesale terms; a design agency rewrote tent titles one season. Both go to counsel.
- Step 4: the trading director will sponsor the case but cannot authorize it, so the path continues to the CEO.
- Step 5: the in-house lawyer reviews marketplace seller terms and the wholesale agreements.
- Step 6: the CEO agrees to an introduction, with the sponsor copied.
The introduction names the CEO as the authorized contact and the head of catalog operations as sponsor. It attaches nothing. For a role-mapping example from another sector, see dispatch and service workflows in transportation.
Left open until SourceX's rights review
Even with the right person introduced, several answers belong to SourceX's review, not the partner:
- whether buyers are interested in this record set;
- SourceX licenses business data directly from companies and pays them for it. We are their counterparty from agreement through delivery and payment.
- which systems and years are selected, and how records are de-identified;
- whether an offer follows, and any reward.
The company also 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. You sign the Channel Partner Agreement before submitting the introduction, and the first valid introduction within the 90-day window is credited when the company submits a verified application.
How buyers approach data in general is outlined in how AI labs buy data; nothing here implies a particular buyer. For a sense of how support records raise similar authority questions, see licensing customer support data for AI. To describe the systems before the introduction, use the system map, then the referral brief template. Sector context is on the ecommerce industry page.
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 tree ends at the CEO and the CEO agrees to be introduced, register as a partner, confirm the company on who qualifies, and read the program terms before you make the introduction.