Backorder substitution decisions: the records that explain how a distributor handled the exception

Short answer

The records that explain a backorder substitution are the availability snapshot that showed the shortage, the substitute offered and why, the customer's approval, the shipped order, and any note on how the substitute worked in use. Together they show the problem, the authorized choice and the checked result. A distribution ERP consultant asks the sales operations director about them at metadata level, then introduces the executive who can authorize a licensing discussion: the CEO, or the owner in an owner-run distributor.

Visual briefFull-size diagram
A three-lane timeline across ERP, CRM and email showing one substitution decision from the backorder on day 0 to the accepted installation on day 21, with an orange marker where the installation change, the reason the substitute worked, was recorded only in email.
Illustrative: one fictional substitution traced across three systems. The orange marker is the only record of why the substitute worked.

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.

DayWhat happenedRecordSystem
0Order line entered; requested model shows no available quantity before the job dateAvailability check result and backorder lineERP
0Sales lists two possible substitutes and checks stock on eachSubstitute list for the item, quotes for both optionsERP
1Sales calls the contractor's project manager; the mounting difference is explainedCall log with the substitute namedCRM
2Project manager approves the substitute and asks for 40 mounting kitsApproval email, revised quoteEmail, CRM
3Original line canceled, substitute and kits added, order shippedOrder change history, shipment recordERP
14Contractor reports the first floor installed with the new rough-inEmail from the site, forwarded to salesEmail
21No returns; substitute marked as an approved alternate for this contractorCustomer note and item cross-referenceCRM, 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.

QuestionUseful historyThin history
Was availability saved at decision time?A saved snapshot or backorder report on the orderAvailability recalculated today, so the shortage cannot be seen
Is the substitute's reason recorded?A substitution reason code or a sales noteA changed item number with no reason
Is the customer's approval findable?A CRM activity or email linked to the order numberAn approval given by phone and never logged
Is the outcome recorded?Returns, credits or an approved-alternate flagNothing after shipment
Do the records share a key?Order number or quote number appears in every systemEach 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

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.

  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 a backorder report the same as a substitution history?

No. A backorder report shows which lines could not ship on time. The substitution history is the decision that followed: which item was offered, who at the customer accepted it, and whether the substitute worked in use. That decision usually spans the ERP, the CRM and email.

Should the company keep every old order before the rollout?

Not on a partner's advice. Retention is the company's decision, made by people with authority over the records and with counsel where customer data is involved. The inventory only shows them what exists and when access changes.

Does the partner need to see any orders to make the introduction?

No. Discovery stays at metadata level: record types, years covered, rough volumes, systems and owners. SourceX reviews rights and content only after the company decides to talk.

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. help.sap.com/docs/SAP_S4HANA_ON-PREMISE/7b24a64d9d0941bda…

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