A substitute that changed how the customer installs: the case to trace
Start with one hard case, because it shows which records matter. A substitution is easy to log when the replacement is identical. It is hard when the substitute ships on time but changes something downstream for the customer, and that is the record that shows judgment rather than a routine transaction.
The worked example is Illustrative: a fictional 310-person plumbing and electrical supplies distributor, not a real case or a completed deal. A mechanical contractor orders 40 commercial lavatory faucets for a school renovation. The ordered model goes on backorder for eleven weeks. Sales offers a faucet from another manufacturer that is in stock, but it needs a different mounting kit, so the contractor's plumbers have to change their rough-in sequence.
| Day | What happened | Record | System |
|---|---|---|---|
| 0 | Order line entered; requested model shows no available quantity before the job date | Availability check result and backorder line | ERP |
| 0 | Sales lists two possible substitutes and checks stock on each | Substitute list for the item, quotes for both options | ERP |
| 1 | Sales calls the contractor's project manager; the mounting difference is explained | Call log with the substitute named | CRM |
| 2 | Project manager approves the substitute and asks for 40 mounting kits | Approval email, revised quote | Email, CRM |
| 3 | Original line canceled, substitute and kits added, order shipped | Order change history, shipment record | ERP |
| 14 | Contractor reports the first floor installed with the new rough-in | Email from the site, forwarded to sales | |
| 21 | No returns; substitute marked as an approved alternate for this contractor | Customer note and item cross-reference | CRM, ERP |
Day 14 is the record companies often never think to keep. The ERP shows a clean swap and a shipped order. Only the email shows that the substitute was acceptable because the customer changed its own process. A history that has days 0, 3 and 21 but not 1, 2 and 14 tells you what was shipped, not why it worked.
Which backorder substitution records help a company explain how exceptions were handled?
The records that join the shortage, the authorized choice and the checked result. In the case above, that is three record classes: availability snapshots, customer approvals and shipped orders, plus the notes that connect them.
- Availability snapshot. What the system showed when the decision was made: available quantity, expected receipt date, the job date. Many ERPs calculate availability at the moment of the check, so ask whether anything saved the result. SAP documents that when the original product is entered in an order, the system checks whether it is subject to substitution before it checks availability, which tells you the order of events the history should reflect.
- The substitute offered. The alternate item and why it was chosen. In SAP S/4HANA, product substitution runs on the condition technique and substitution reasons decide whether the swap is automatic or offered for manual choice. An automatic swap leaves a different trail from a salesperson's judgment call.
- Customer approval. Who at the customer accepted, when, and on what conditions. This is usually a CRM activity or an email, rarely an ERP field.
- Shipped order and outcome. The changed order line, the shipment, and whether anything came back. Returns, credits or a later "approved alternate" flag are the checked result.
Microsoft's Business Central has an Inventory Sales Back Orders report that lists lines whose outstanding quantity cannot be met by the shipment date, with order number, customer, shipment date and quantity on back order. That is the start of the chain, not the whole of it. For the general pattern of exception records, see exception handling data for AI agents and the decision records data type.
What separates a useful substitution history from a thin one?
Most distributors have some substitution records. What matters is whether the chain can be followed without someone's memory. Use this test when the sales operations director describes what exists.
| Question | Useful history | Thin history |
|---|---|---|
| Was availability saved at decision time? | A saved snapshot or backorder report on the order | Availability recalculated today, so the shortage cannot be seen |
| Is the substitute's reason recorded? | A substitution reason code or a sales note | A changed item number with no reason |
| Is the customer's approval findable? | A CRM activity or email linked to the order number | An approval given by phone and never logged |
| Is the outcome recorded? | Returns, credits or an approved-alternate flag | Nothing after shipment |
| Do the records share a key? | Order number or quote number appears in every system | Each system uses its own reference |
A history can be thin and still worth a conversation, but the partner should describe it honestly. "Five years of backorder lines with substitute reason codes, approvals mostly in email" is a useful metadata answer. "Lots of substitution data" is not.
Ask the sales operations director about coverage and rights
The sales operations director usually knows coverage: which systems hold the backorder lines, where approvals are logged, how many years go back and roughly how many substitutions happen a year. Ask only for those facts. Never ask for orders, quotes, customer emails or exports.
Rights and authority sit elsewhere. Substitution records contain customer contacts, pricing and supplier details, and supplier price files often carry their own confidentiality terms; see distributor supplier price file confidentiality. If approvals sit in a CRM, field history settings decide how much of the trail still exists; see Salesforce field history tracking retention. The person who can authorize a licensing discussion is the CEO, or the owner in an owner-run distributor, and the company's counsel decides what could ever be included.
The introduced 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. See who qualifies, the industries hub, specialty distribution and wholesale distribution data.
Until SourceX reviews it, nobody knows whether buyers want this history, what rights review concludes about customer contacts and supplier data, how much de-identification is needed, or whether an offer follows. 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. More for ERP advisors is on the ERP consultants page, and approval workflows are covered in assessing procurement approvals and exception workflows.
Go deeper on backorder substitution decisions
- Backorder substitution decisions records across systems: a map of the keys that join ERP, CRM and email records for one substitution.
- Who can license backorder substitution decisions records: a short answer on which executive to introduce.
- Preserve backorder substitution decisions records: an inventory guide for what to list before an inventory platform rollout.
- Backorder substitution decisions referral brief template: a fill-in brief for writing the company introduction.
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 distributor can follow its substitutions from shortage to approval to outcome, register as a partner, check the distributor against who qualifies, and read the program terms before you introduce the executive who can authorize the discussion.