Backorder substitution decisions referral brief: a fill-in template with one completed example

Short answer

A company introduction about backorder substitution decisions is a one-page brief the sales operations director can forward without editing. It states the business task, the record classes, the ERP, CRM and mailboxes that hold them, the years and rough volumes covered, the open question about how well approvals and outcomes were kept, any documented access deadline, and who convenes and approves. It contains no orders, customer names, prices, emails or estimates of value. The template has ten fields, followed by one completed example.

Visual briefFull-size diagram
A two-column brief card for a distributor: the left column lists nine of the ten field labels, company, task, records, systems, coverage, volume, open question, deadline and authority, and the right column fills in Illustrative values row by row, ending with a green check on authority.
Illustrative: the completed brief for a fictional distributor. Each value is a fact about the records, never the records themselves.

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.

FieldWhat to writeFormat of a good entry
1. CompanyDistribution segment, approximate full-time headcount at peak, country"MRO distributor, about 400 full-time staff, U.S."
2. Business taskThe substitution workflow in one sentence"Offering and approving substitutes for backordered stock items"
3. Record classesKinds of records, by name"Backorder lines, cross-references, change history, approvals"
4. SystemsERP, CRM, mailboxes and any returns module, by name or type"ERP, CRM, shared sales mailbox"
5. CoverageYears held, per system if they differ"Closed orders since 2017; CRM since 2020"
6. VolumeSubstituted lines per year, read from a report"Several thousand substituted lines a year"
7. TriggerWhether substitutes are automatic, manual or both"Manual, chosen by inside sales"
8. Open questionThe gap that most limits the history"Whether site feedback left personal inboxes"
9. DeadlineA documented event that changes access, with its source"Old ERP hosting ends per contract"
10. AuthorityWho 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.

  1. Company: HVAC and plumbing supplies distributor, about 330 full-time staff at peak across 14 branches, United States.
  2. Business task: offering and approving substitutes when a stocked item goes on backorder, and checking whether the substitute worked on site.
  3. 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.
  4. Systems: an on-premises ERP for orders and items; a cloud CRM for sales activity; a shared inside-sales mailbox.
  5. 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.
  6. Volume: the backorder report shows a few thousand substituted lines a year, as read by the sales operations director.
  7. Trigger: mostly manual, chosen by inside sales; a small set of interchangeable items swap automatically.
  8. Open question: whether contractor feedback about installation changes was kept anywhere except individual salespeople's inboxes before the shared mailbox existed.
  9. 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.
  10. 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.

FieldQuestion you can usually answer from project knowledgeWhere the documented fact comes from
4. SystemsWhich ERP version and modules are liveThe implementation scope
5. CoverageWhether closed orders were migrated at the last upgradeThe previous migration plan
6. VolumeWhether a backorder report exists and who runs itERP documentation; Business Central, for example, has an Inventory Sales Back Orders report listing unfilled lines by order, customer and quantity
8. Open questionWhether CRM approval fields keep their edit historyCRM documentation; Salesforce states standard field history is kept 18 months in the interface and up to 24 months via the API
9. DeadlineWhen the hosting or license contract endsThe 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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Can the brief include the backorder report itself?

No. A report lists customers and orders, which are the records. The brief carries only what the report tells you in aggregate, such as roughly how many substituted lines a year, read by someone at the company.

How long should the brief be?

One page. If a field needs more than two lines, it usually contains detail that belongs in SourceX's later review rather than in the introduction.

Sources

  1. refer.sourcex.si/terms
  2. learn.microsoft.com/en-us/dynamics365/business-central/reports/r…
  3. help.sap.com/docs/SAP_S4HANA_ON-PREMISE/7b24a64d9d0941bda…
  4. trailhead.salesforce.com/content/learn/modules/field-audit-trail-basi…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment