This decision tree is part of the backorder substitution decisions guide. It answers one question for distribution ERP consultants: who can say yes to a conversation about substitution history?
Who keeps substitution records, and what each person can decide
Substitution history is spread across teams. Each knows part of it; few can commit the company.
| Role | What they keep or know | Can they authorize a licensing discussion? |
|---|---|---|
| ERP administrator or IT manager | Order lines, change history, retention settings, exports | No: technical access is not authority |
| CRM administrator | Call logs, tasks, field history settings | No |
| Purchasing or category manager | Substitute cross-references, supplier terms on product data | No, but flags supplier restrictions |
| Customer service lead | Returns, credits, complaint notes | No |
| Sales operations director | The substitution process end to end and where approvals live | Convenes; usually not alone |
| COO or CFO | Operating records and the systems budget | No, but often prepares the case for the CEO |
| CEO or owner | The company's information as an asset | Yes, and signs |
| General counsel or outside counsel | Customer contracts, supplier terms, personal data | Advises; approval sits with the CEO |
A detail worth knowing before the first call: how substitutions are configured tells you who has been making the decisions. In SAP S/4HANA, substitution reasons determine whether a substitute is applied automatically or offered for manual selection. Automatic substitution means the rule-setter, often purchasing or product data, shaped the decision; manual substitution means sales did. Either way, neither team owns the records as an asset.
The yes path: five questions
Work through in order. The introduction is the first person who answers yes to question 3.
- Does this person run one system or one team? If yes, they describe it. Ask who owns substitution handling across sales and purchasing.
- Does this person own the substitution process? If yes, this is usually the sales operations director. Ask them to convene and to bring in the CEO, who decides.
- Can this person commit company records to an agreement? If yes, this is the introduction: the CEO, who in an owner-led distributor is usually the owner.
- Does a board, parent group or private equity sponsor need to consent? Note it; SourceX will ask.
- Is counsel aware? If not, suggest the convener brings counsel to the first meeting, because customer and supplier terms decide scope.
Stopping at question 2 is the usual mistake. The sales operations director understands the records best and is rarely the person who can say yes.
Branches that need customer, supplier or legal review
Substitution records involve parties outside the company. The partner flags each branch and stops.
| Branch | Why it matters | Who decides | Possible outcome in review |
|---|---|---|---|
| Customer contacts on approvals | Names and emails of the people who approved substitutes | Counsel and the privacy lead | Pseudonymized or removed |
| Customer contracts | Some customers restrict use of their order data | Counsel, against each contract type | Restricted accounts excluded |
| Supplier specifications and price files | Manufacturer data may carry confidentiality terms | Counsel with purchasing | Often excluded; item references may remain |
| Negotiated prices on orders | Commercially sensitive for the distributor and its customers | CFO and counsel | Often removed or banded |
| Orders under dispute | Records may be on hold | Counsel | Left alone |
Where EU law applies, the GDPR defines personal data as any information relating to an identified or identifiable person, including by reference to a name or identification number. The approver on a substitution email fits. Supplier price files have their own question; see distributor supplier price file confidentiality. These branches shape scope; whether any of them rules records out is settled in SourceX's review. See why data rights matter.
Two distributors, two paths (Illustrative)
Two fictional companies show how the same tree gives different introductions. Neither is a real case.
| Question | 280-person owner-led electrical distributor | 900-person PE-backed industrial distributor |
|---|---|---|
| Who describes the records? | Sales operations manager | Sales operations director and the ERP lead |
| Who convenes? | Sales operations manager | Sales operations director |
| Who signs? | The owner, as CEO | The CEO, with the CFO preparing the case |
| Who else consents? | Nobody beyond the owner | The private equity sponsor |
| Main side branch | Supplier price files from two manufacturers | Customer contracts with national accounts |
The owner-led path is short: one convener, one signer. The sponsor-backed path adds a consent step and a contract review, which changes timing but not eligibility. In both, the ERP backorder report that lists unfilled lines by order and customer, of the kind Business Central documents, tells the convener the scale of the history without anyone opening an order.
What stays unknown until SourceX's rights review
When the CEO agrees to talk, these remain open:
- Rights: which accounts, record classes and years the distributor can license after customer, supplier and privacy checks.
- Scope: whether order history, CRM activity and approval email are all in, and in what de-identified form.
- Demand: whether any buyer wants substitution histories when SourceX reviews them.
- Terms: whether an offer follows, and its payout and schedule.
The introduced 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. Partners sign the Channel Partner Agreement before submitting introductions; the first valid introduction within the 90-day window is credited when the company submits a verified application, and one partner is credited per company. The system map helps the convener describe the records, and the referral brief template puts the answers on one page. More for advisors is on the ERP consultants page and in wholesale distribution data.
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.
Once the sales operations director has agreed to bring in the CEO, who can say yes, and flagged any customer or supplier limits, register as a partner, confirm the distributor on who qualifies and read the program terms before making the introduction.