Backorder substitution decisions across ERP, CRM and email: a system map of records and linking keys

Short answer

To reconstruct a backorder substitution across systems you need five joins: the order line, the original and substitute item, the time of the decision, the customer approver, and the outcome. The ERP holds the order and item keys; the CRM and email hold the approval and the feedback. The joins survive only where both sides recorded the same identifier, usually the sales order number. The approver join is the most fragile and the one that matters most for licensing, because it is where customer personal data sits.

Visual briefFull-size diagram
A system map in a ring: ERP order lines, item master, CRM activities, shared mailbox and returns module, with linking keys, the order number, substitute item, order number typed into the CRM, approver email and original order, travelling along the links to a joined case; the approver link is marked orange as the weakest join.
Illustrative: the keys that join one fictional substitution. The approver link is where most histories break.

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.

SystemRecord it holdsLinking key it sharesUsual owner
ERP sales ordersOrder header, lines, canceled and added lines, change history, shipmentSales order and line numberERP administrator, order management
ERP item masterItem numbers, substitute and alternate cross-references, substitution reasonsItem numberPurchasing or product data team
CRMCall logs, tasks, quotes, contact recordsAccount, contact, and the order number if typed inSales operations
Shared mailbox or personal emailCustomer approval, site feedback, revised quoteOrder number in the subject line, if anyone put it thereIndividual staff unless filed
ERP returns and creditsReturn authorizations, credit memos, reason codesOriginal order numberCustomer 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.

JoinERP keyCRM or email keyWhere it breaks
OrderSales order and line numberOrder number quoted in the activity or email subjectApproval logged against the account, not the order
Original and substitute itemCanceled line, new line, item cross-referenceProduct names in the call logA model nickname typed instead of an item number
Decision timeOrder change timestampsActivity and email datesCRM activity entered days later from memory
ApproverCustomer contact on the order headerPerson who replied to the emailApproval given by a site foreman who is not a CRM contact
OutcomeReturns, credits, alternate flag on the itemSite feedback emails, follow-up tasksFeedback 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.

StepSystemRecordKey carried forward
1ERP sales ordersOrder SO-77310 line 4: 60 units of item BRG-6205, no quantity available before the requested dateSO-77310 line 4
2ERP item masterBRG-6205 lists BRG-6205-X as a manual substitute, reason code "equivalent, different seal"Item BRG-6205-X
3CRMCall log: salesperson explains the seal difference to the customer's maintenance planner; activity cites SO-77310SO-77310
4Shared mailboxPlanner approves by email, subject "SO-77310 substitute OK", asks for a different grease interval noteSO-77310, approver's address
5ERP sales ordersLine 4 canceled, line 5 added for BRG-6205-X; change history shows user and timeSO-77310 line 5
6ERP shipmentsLine 5 shipped two days laterSO-77310
7Shared mailboxPlanner reports the lubrication schedule was changed for the new sealSO-77310 in the subject
8ERP returnsNo return against SO-77310 after 60 daysSO-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:

  1. Which systems hold backorder lines, substitution cross-references, approvals and returns, and since when?
  2. Do CRM activities about substitutions cite the order number, or only the account?
  3. Are customer approvals kept in a shared mailbox, the CRM, or personal inboxes?
  4. Does the ERP keep order change history for closed orders, and for how many years?
  5. Roughly how many substituted lines a year, from a report?
  6. 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.

  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

Is the item cross-reference enough to show a substitution happened?

It shows that a substitute was allowed, not that it was used on a given order or why. The order change history, the customer approval and the outcome records are what turn a permitted swap into an explained decision.

What if approvals were given by phone?

Then the only trace may be a CRM call log typed after the call, or nothing. Record that as a gap on the map. A history with good ERP keys and thin approvals is still worth describing honestly.

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