This template is part of the backorder substitution decisions guide. Fill it after the first conversation with the sales operations director, and only with facts someone at the company can confirm.
The ten-field template
Each field takes one or two lines. Where you do not know, write "unknown"; SourceX can work with a named gap but not with a guess.
| Field | What to write | Format of a good entry |
|---|---|---|
| 1. Company | Distribution segment, approximate full-time headcount at peak, country | "MRO distributor, about 400 full-time staff, U.S." |
| 2. Business task | The substitution workflow in one sentence | "Offering and approving substitutes for backordered stock items" |
| 3. Record classes | Kinds of records, by name | "Backorder lines, cross-references, change history, approvals" |
| 4. Systems | ERP, CRM, mailboxes and any returns module, by name or type | "ERP, CRM, shared sales mailbox" |
| 5. Coverage | Years held, per system if they differ | "Closed orders since 2017; CRM since 2020" |
| 6. Volume | Substituted lines per year, read from a report | "Several thousand substituted lines a year" |
| 7. Trigger | Whether substitutes are automatic, manual or both | "Manual, chosen by inside sales" |
| 8. Open question | The gap that most limits the history | "Whether site feedback left personal inboxes" |
| 9. Deadline | A documented event that changes access, with its source | "Old ERP hosting ends per contract" |
| 10. Authority | Who convenes, who approves, who advises | "Sales operations director; CEO; counsel" |
Field 7 is specific to substitutions and worth the extra line. In SAP S/4HANA, for example, substitution reasons decide whether a substitute is applied automatically or offered for manual selection. An automatic swap leaves a clean ERP trail and little reasoning; a manual one leaves reasoning only if the CRM or email captured it. Knowing which tells SourceX where to look for the explanation of each decision.
A completed example (Illustrative)
The values below describe a fictional 330-person HVAC and plumbing supplies distributor. They are Illustrative, not a real company, case or deal.
- Company: HVAC and plumbing supplies distributor, about 330 full-time staff at peak across 14 branches, United States.
- Business task: offering and approving substitutes when a stocked item goes on backorder, and checking whether the substitute worked on site.
- Record classes: backorder lines, substitute cross-references with reason codes, order change history, shipments, returns and credits; CRM call logs; approval and site feedback email.
- Systems: an on-premises ERP for orders and items; a cloud CRM for sales activity; a shared inside-sales mailbox.
- Coverage: nine years of closed orders and change history in the ERP; CRM activity for the last five; the shared mailbox since its creation four years ago.
- Volume: the backorder report shows a few thousand substituted lines a year, as read by the sales operations director.
- Trigger: mostly manual, chosen by inside sales; a small set of interchangeable items swap automatically.
- Open question: whether contractor feedback about installation changes was kept anywhere except individual salespeople's inboxes before the shared mailbox existed.
- Deadline: a new inventory platform goes live next year; the old ERP's hosting contract sets the end of read access, which the IT manager is confirming.
- Authority: the sales operations director will convene; the CEO approves, with the COO and CFO preparing the case; outside counsel advises on customer contracts and supplier price files.
The example names who confirmed each fact. That matters more than precision: "a few thousand, read from the report by the sales operations director" is better than an exact figure nobody can trace.
What to check in your own systems knowledge first
A distribution ERP consultant often knows the client's systems well enough to sharpen fields 4, 5 and 8 without asking for anything new.
| Field | Question you can usually answer from project knowledge | Where the documented fact comes from |
|---|---|---|
| 4. Systems | Which ERP version and modules are live | The implementation scope |
| 5. Coverage | Whether closed orders were migrated at the last upgrade | The previous migration plan |
| 6. Volume | Whether a backorder report exists and who runs it | ERP documentation; Business Central, for example, has an Inventory Sales Back Orders report listing unfilled lines by order, customer and quantity |
| 8. Open question | Whether CRM approval fields keep their edit history | CRM documentation; Salesforce states standard field history is kept 18 months in the interface and up to 24 months via the API |
| 9. Deadline | When the hosting or license contract ends | The contract owner, not an estimate |
Use project knowledge only to describe the systems. Never pull a report, export or screenshot for the brief.
What the brief leaves out, and the checks before sending
Leave out customer names, contact details, order numbers, prices, supplier price files, any email or call log, login details and any estimate of value. Then check:
- Size: 50+ full-time employees at peak, contractors excluded.
- 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: the brief names the customer-contact and supplier-terms questions without answering them; SourceX's rights review does that.
- Authority: the person in field 10 can say yes; the who-can-say-yes tree helps check.
- Paperwork: the Channel Partner Agreement is signed before you submit the introduction. The first valid introduction within the 90-day window is credited when the company submits a verified application.
For covering-note wording and how to disclose your referral relationship, use the warm introduction brief or the client introduction email templates for ERP consultants. The system map explains the joins behind field 8, and specialty distribution gives sector context.
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 sales operations director has confirmed every field or marked it unknown, register as a partner, check the distributor on who qualifies and read the program terms before sending the brief on.