This system map is part of the backorder substitution decisions guide. The hub traces why a substitution worked; this page shows which system holds each piece and what key holds them together.
Five systems, the record each holds, and who runs it
A mid-sized distributor typically spreads one substitution across four or five places. The table is the map: one row per system, the record it holds, the key it can share, and the team that administers it.
| System | Record it holds | Linking key it shares | Usual owner |
|---|---|---|---|
| ERP sales orders | Order header, lines, canceled and added lines, change history, shipment | Sales order and line number | ERP administrator, order management |
| ERP item master | Item numbers, substitute and alternate cross-references, substitution reasons | Item number | Purchasing or product data team |
| CRM | Call logs, tasks, quotes, contact records | Account, contact, and the order number if typed in | Sales operations |
| Shared mailbox or personal email | Customer approval, site feedback, revised quote | Order number in the subject line, if anyone put it there | Individual staff unless filed |
| ERP returns and credits | Return authorizations, credit memos, reason codes | Original order number | Customer service or finance |
Keys are strongest on the ERP side. A standard backorder report, such as the one Microsoft documents for Business Central, already prints each unfilled line with its order number and customer, so every case starts with a usable identifier. The weak point is whether anyone carried that number into the CRM and the inbox.
The keys that join one substitution
Each join needs an identifier recorded on both sides at the time. Here is what each depends on and where it typically breaks.
| Join | ERP key | CRM or email key | Where it breaks |
|---|---|---|---|
| Order | Sales order and line number | Order number quoted in the activity or email subject | Approval logged against the account, not the order |
| Original and substitute item | Canceled line, new line, item cross-reference | Product names in the call log | A model nickname typed instead of an item number |
| Decision time | Order change timestamps | Activity and email dates | CRM activity entered days later from memory |
| Approver | Customer contact on the order header | Person who replied to the email | Approval given by a site foreman who is not a CRM contact |
| Outcome | Returns, credits, alternate flag on the item | Site feedback emails, follow-up tasks | Feedback stays in a personal inbox |
The trigger also shapes which keys exist. SAP documents substitution reasons as the setting that makes a swap automatic or leaves it for manual selection. Rule-driven swaps write the item key into the order with no CRM step, so the map has fewer nodes; hand-picked swaps add CRM and email nodes, and each needs the order number to join.
One fully joined substitution (Illustrative)
A fictional 420-person industrial MRO distributor substitutes a backordered bearing for a maintenance customer. Every identifier below is invented to show the shape of a joined case.
| Step | System | Record | Key carried forward |
|---|---|---|---|
| 1 | ERP sales orders | Order SO-77310 line 4: 60 units of item BRG-6205, no quantity available before the requested date | SO-77310 line 4 |
| 2 | ERP item master | BRG-6205 lists BRG-6205-X as a manual substitute, reason code "equivalent, different seal" | Item BRG-6205-X |
| 3 | CRM | Call log: salesperson explains the seal difference to the customer's maintenance planner; activity cites SO-77310 | SO-77310 |
| 4 | Shared mailbox | Planner approves by email, subject "SO-77310 substitute OK", asks for a different grease interval note | SO-77310, approver's address |
| 5 | ERP sales orders | Line 4 canceled, line 5 added for BRG-6205-X; change history shows user and time | SO-77310 line 5 |
| 6 | ERP shipments | Line 5 shipped two days later | SO-77310 |
| 7 | Shared mailbox | Planner reports the lubrication schedule was changed for the new seal | SO-77310 in the subject |
| 8 | ERP returns | No return against SO-77310 after 60 days | SO-77310 |
The order number runs through every step, which is what makes this case reconstructable. Step 7, the change to the customer's maintenance routine, is the reason the substitute worked, and it exists only because the planner kept the order number in the subject line. If step 4 had been a phone call, steps 3 and 5 would show what changed but not who agreed.
Where the joins break, and what survives
Most distributors have strong ERP keys and weaker ones everywhere else. Naming the breaks makes the history easier to describe accurately.
- Edited CRM fields. If approvals are recorded in CRM fields that are later edited, history settings decide what survives. Salesforce documents that standard field history is retained for 18 months in the user interface and up to 24 months via the API, unless a longer-retention add-on is in use; see Salesforce field history tracking retention.
- Email in personal inboxes. Approvals and site feedback that never reached a shared mailbox may be gone when staff leave.
- ERP migrations. A move to a new ERP often loads open orders only, leaving closed orders and change history behind; the QuickBooks to NetSuite guide covers the same open-orders-only problem.
- Emailed purchase orders. Where orders arrive by email, the original request may be a separate record from the ERP order; see AI order entry from email purchase orders.
Mapping questions for the sales operations director
The sales operations director can usually answer these from memory or a report, without opening an order:
- Which systems hold backorder lines, substitution cross-references, approvals and returns, and since when?
- Do CRM activities about substitutions cite the order number, or only the account?
- Are customer approvals kept in a shared mailbox, the CRM, or personal inboxes?
- Does the ERP keep order change history for closed orders, and for how many years?
- Roughly how many substituted lines a year, from a report?
- Who administers each system, and who owns the substitution process?
The answers feed the referral brief. Who can approve a licensing discussion is covered in who can license backorder substitution records. The decision records data type explains the general pattern, and MRO distribution gives sector context.
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 and never handle orders, emails or exports. Whether the records can be licensed, after customer and supplier terms are checked, and whether any buyer wants them, stays unknown until SourceX reviews it.
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 the sales operations director confirms that the order number reaches the CRM and the approval email for most substitutions, register as a partner, check the distributor on who qualifies and read the program terms before making the introduction.