Systems and records
Supplier substitution approval dataset: when the cheaper supplier is not approved
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
A procurement task should treat a cheaper supplier that lacks approval as ineligible for the current order, not as a better option. The correct answer buys from an approved source, or uses a documented exception with the right authority, and opens qualification for the cheaper supplier in parallel. A good supplier substitution approval dataset records the constraint that ruled the cheaper option out, the evidence for it and what was delivered.
Provenance trail
Supplier substitution
Key takeaways
- A cheaper supplier without approval for the item, revision, site or customer is a qualification candidate, not an option for the current order.
- Purchasing systems enforce this through source lists and approved supplier list statuses, and public procurement through qualification requirements.
- Each task freezes the approval state on the decision date and asks for the action, the governing constraint and the authority needed.
- Exceptions are valid only when documented and approved in advance by someone holding the authority, with customer agreement where required.
- Include a similar but unapproved option in tasks, because similarity tools find candidates but say nothing about approval.
- Show prices as relative differences and pseudonymize suppliers and customers.
Why the cheaper alternate cannot simply be swapped in
Approval is a constraint and price is a preference, and a constraint is checked first. A supplier approval is usually scoped to a specific item or category, a specific manufacturing site, a specific specification revision and sometimes a specific customer. A supplier that is cheaper on the quote but missing any of those scopes is not an alternative for this order; it is a candidate for qualification.
Purchasing systems encode this directly. In SAP, a source list record can be marked fixed, which makes that vendor or agreement the preferred source within its validity period, or blocked, which stops it being suggested, and a blocked record with a validity period stops the material being ordered from that source during that window. Oracle's procurement documentation says the approved supplier list status controls whether a supplier is authorized to source an item or category and whether purchase orders for it can be approved. Public buying works the same way: under FAR 9.206-1, when a qualification requirement applies, the contracting officer need consider only offers that meet it, unless the offeror can demonstrate before award that it meets the qualification standards.
A supplier substitution approval dataset captures these decisions as tasks, so that a model or a new buyer learns that the lowest quote is the wrong answer whenever an approval constraint applies.
Which constraints make the obvious choice invalid
Six kinds of constraint regularly turn the cheapest or fastest option into the wrong one. Each lives in a different record, which is why the task has to carry the evidence rather than a summary of it.
The constraints also stack. A supplier can be on the company's own approved list and still be wrong for one customer's part, or approved for the part and still be wrong for this order because its site changed last month. A task should name every constraint that applies, and the answer key should say which one decides the case when several point the same way.
| Constraint | Where it is recorded | What it blocks | Evidence the task must include |
|---|---|---|---|
| Supplier not on the approved list for the item | ERP source list or approved supplier list | Ordering, or approving the order, from that source | List entry and status as of the order date |
| Approval tied to a site that changed | Supplier qualification file, change notice | Treating an old approval as valid for a new plant or owner | Approval scope and the change notice date |
| Specification revision not covered | Item master, drawing or specification revision log | Using an approval granted against an earlier revision | Revision in force and revision on the approval |
| Customer-specific approval required | Customer agreement, drawing notes, customer approved list | Any source the customer has not approved, whatever the company's own list says | Clause or drawing note and customer approval record |
| Open change notice from the supplier | Change notice inbox, supplier portal, quality system | Assuming the approved part is unchanged | Notice, classification and disposition |
| Approver limit exceeded | Approval workflow setup | Releasing the order on a buyer's own authority | Approver ID, limit and approval entry |
The approval constraint and substitution reasoning task
Each task gives the solver the situation as it stood on the decision date, asks it to choose a sourcing action and explain the governing constraint, and scores it against the decision that was actually made and what was delivered. The template below is the asset; a company can fill it from its own purchase history.
The inputs are frozen at the decision date. If the approved supplier list later changed, the task shows the list as it was, because the point is to test reasoning with the information the buyer had.
| Task field | Content | Typical source | Check before use |
|---|---|---|---|
| requirement | Item, quantity, need-by date, specification revision | Requisition and item master | Revision matches the drawing in force on the date |
| options | Two to four candidate sources with quoted price index, lead time and status | Quotes, supplier records | Prices shown as an index or relative difference only |
| approval_state | Approved list status per option, scope and validity dates | Source list or approved supplier list history | Status as of the decision date, not today |
| customer_constraints | Customer-approved sources and notification duties | Customer agreement, drawing notes | Clause text paraphrased, customer pseudonymized |
| open_changes | Change notices or site changes affecting any option | Supplier change notices, qualification file | Dated before the decision |
| authority | Who may approve the order or an exception, with limits | Approval workflow setup | Approver role and limit in force on the date |
| question | Which sourcing action is correct, and which constraint governs it? | Written by the task author | One correct action; ties resolved in the answer key |
| answer_key | Action, governing constraint, required approvals, follow-up | Purchase order, approval entries, deviation record | Matches what was done, or notes why it should not have been |
| outcome | Receipt, inspection result and any return or nonconformance | Receipts, inspection and quality records | Linked by PO line and lot |
What a correct answer has to contain
A correct answer names the action, the constraint that decided it and the authority needed, and it does not stop at the purchase order. Scoring only the chosen supplier rewards guessing; scoring the reasoning fields catches a solver that picked the approved source for the wrong reason.
- The action: buy from the approved source, request a documented exception, start qualification, or escalate because no compliant option meets the date.
- The governing constraint, cited from the task evidence rather than restated in general terms.
- The approvals required for the action, including the approver role when an exception or an amount limit applies.
- The follow-up that keeps the cheaper option alive, such as a qualification request with the evidence the supplier must provide.
- A statement of what the answer does not know, for example that a change notice is open and its disposition is pending.
- No invented approvals: any approval the answer relies on must exist in the task evidence.
| Answer element | Full credit | Partial credit | No credit |
|---|---|---|---|
| Action | Matches the answer key | Compliant but slower or costlier than the key without reason | Orders from an unapproved source |
| Governing constraint | Cites the deciding record from the evidence | Names the right type of constraint without the record | Cites price, lead time or similarity as decisive |
| Authority | Names the approver role and confirms the limit | Says approval is needed without naming who | Omits approval or invents one |
| Follow-up | Opens qualification or requests a notice disposition | Mentions follow-up in general terms | None |
Worked example: a cheaper resin source for a molded housing
Illustrative: a fictional contract manufacturer needs resin for a molded housing it builds for a fictional medical device customer. Three sources are quoted and the need-by date is 25 days out. The figures are invented and shown as relative differences and durations only.
The correct action is to order from source A, because source B has no approval at all and source C's approval is tied to a site that has changed under an open change notice, and the customer's agreement names approved sources for this part. The answer opens qualification for source B through the customer's approval process and asks source C for the change notice disposition. If source A could not meet the need-by date, the answer would escalate to the approver named in the workflow and the customer, not quietly order from B.
A useful variant of the same task changes one fact. Move source A's lead time to 35 days against the same 25-day need-by date, and the answer key changes from ordering A to escalating: request an expedited delivery from A, ask the customer whether a temporary deviation to C is acceptable once the change notice is resolved, and record the decision either way. Pairs of tasks that differ in a single fact test whether a solver is reading the constraints or pattern-matching the scenario.
| Option | Relative price | Lead time | Approval state on the decision date |
|---|---|---|---|
| A, current approved source | Baseline | 21 days | Approved for the item, current revision and current site; listed in the customer's approved sources |
| B, new distributor | 12 percent lower | 10 days | Not on the approved list; no customer approval |
| C, second approved source | 6 percent lower | 14 days | Approved, but approval scoped to a plant the supplier says it is relocating in an open change notice |
| Answer key | Not a factor once constraints apply | A meets the need-by date | Order A; qualify B through customer process; hold C pending notice disposition |
When the unapproved supplier can still be used
It can be used only through a documented path that someone with authority signs before the order, never by a buyer's decision at the quote stage. Typical paths are a temporary deviation agreed with the customer for a defined quantity, an expedited qualification, or an emergency exception that the organization's own procedures define in advance.
Public procurement shows the shape of that exception. FAR 9.206-1 lets an offeror that is not yet on a qualified list be considered if it can satisfactorily demonstrate before award that it meets the qualification standards. FAR 9.207 lists conditions that should be reported because they may merit removal from a qualified list, including a supplier that fails to request reevaluation after a change of plant location or ownership. Private buyers use the same logic in their own terms: the exception is evidence presented and accepted before the order, and approvals are reviewed when the supplier's circumstances change.
Authority matters as much as evidence. Business Central's purchase approval workflow, for instance, has approvers set up with amount limits and a substitute approver for each approval user. A task whose answer key relies on an exception should record whose approval it was and confirm that person held the authority at the time.
Similar is not approved: where suggestion tools fit
A tool that finds similar items or suppliers answers a different question from the one an approval answers. Microsoft's Business Central, for example, can use Copilot, in a feature still labeled a preview, to suggest substitute items by searching item descriptions, references and attributes, and the user reviews the suggestions and decides which lines to keep. That is useful for finding candidates. It says nothing about whether a candidate is approved for a given customer, revision or site.
Regulated buyers make the gap explicit. The FDA's Quality Management System Regulation, effective February 2, 2026, incorporates ISO 13485:2016 by reference, and the agency's final rule notes that ISO 13485's purchasing clause requires suppliers to be evaluated based on their ability and performance, in proportion to the risk the purchased product poses. For electronic parts, a product or process change notice from a supplier describes the change, its reasons and its projected impact, and it can invalidate an approval the buyer still has on file. Good tasks deliberately include a similar but unapproved option so that a solver relying on similarity fails.
Which past decisions to sample and how to balance them
Sample decisions where a constraint actually bit, not routine reorders. A repeat order from the only approved source tests nothing, because there was never a choice. The useful population is orders where at least one alternative was quoted, a deviation or qualification was requested, a change notice arrived, or an approval limit was reached.
Balance the set so the cheapest option is not always wrong. If every task punishes the lowest quote, a solver can learn to avoid the lowest quote rather than to read approvals. Include decisions where the cheaper source was approved and correctly chosen, where qualification had finished just before the order, and where no compliant option existed at all.
Keep the answer key honest about past mistakes. Some historical orders will have gone to an unapproved source with no exception on file. Those can still become tasks, but the answer key should state what should have happened and mark the record as a historical deviation, so the set teaches the rule rather than the lapse. A procurement lead and a quality reviewer should sign off on each answer key before it is used.
Checklist · 5 items
- Decisions with two or more quoted sources and a recorded approval state.
- Deviation, waiver and qualification requests, approved and rejected.
- Orders placed while a supplier change notice was open.
- Orders that needed an approver above the buyer's own limit.
- Cases with no compliant option, resolved by escalation.
0 of 5 ticked. Tick each item as you go.
Records to pull when building tasks from purchase history
Tasks are only as good as the history behind them, and approval history is the record most often overwritten. The approved list in the ERP shows today's state; the task needs the state on each decision date, so start from change logs or periodic exports of the source list or approved supplier list.
Supplier prices, customer names and drawing details are confidential, so the task shows prices as an index or relative difference and pseudonymizes suppliers and customers. Exclude orders where the decision record is missing: a purchase from an unapproved source with no deviation on file may be a real lapse, but it cannot be turned into a task with a defensible answer key.
- Purchase orders, receipts and inspection results, linked by PO line and lot.
- Source list or approved supplier list history with status, scope and validity dates.
- Specification and drawing revision logs for the items in scope.
- Deviation, waiver and qualification requests with their approvals and dates.
- Supplier change notices and their dispositions.
- Customer agreement clauses and drawing notes on approved sources, paraphrased.
Turning sourcing decisions into a licensable record set
Decision records like these are the part of procurement history that carries judgment: which constraint applied, who had authority and what was delivered. Customer agreements, supplier confidentiality terms and the ownership of drawings all affect whether they can be used outside the company, and those are separate from simply having access to the ERP. Counsel reviews the agreements that apply.
Where a manufacturer or distributor wants to take sourcing records further, SourceX carries the work from that rights question through contracting, preparation and delivery of a licensed dataset for AI developers. The manufacturer approves the scope and terms and signs before a single record changes hands. A short assessment of the company, with no files uploaded, comes first.
Frequently asked questions
Is it ever acceptable to buy from an unapproved supplier to meet a date?
Only through a documented exception approved in advance by someone with the authority to grant it, and with the customer's agreement where the customer controls approved sources. A buyer choosing a cheaper or faster unapproved source on their own is an unauthorized substitution, even if the parts turn out to be fine.
How is a supplier substitution approval dataset different from a parts substitution log?
A substitution log records what was swapped. The approval dataset records the decision as a task: the options, the approval state on the date, the constraint that ruled options out, the authority used and the outcome. That structure lets a reviewer check reasoning, not only the final choice.
What should the answer key say when no option is compliant?
It should say escalate, name the approver and the customer contact required, and list what would make an option compliant. A task with no compliant option is a valuable test, because many solvers will pick the least bad option instead of escalating.
Why freeze the approved supplier list at the decision date?
Because approvals change. A supplier added later would make the original decision look wrong, and a supplier removed later would make an unapproved choice look right. The task has to test the decision against what was knowable when it was made.
Can price data appear in these tasks?
Show price as a relative difference or index so the task keeps the tension between cost and compliance without exposing negotiated prices. Supplier pricing is usually confidential under supplier agreements, and actual amounts add nothing to the reasoning being tested.
Sources
- SAP source list records can be fixed, making a source preferred within its validity period, or blocked, so the source is not suggested and, with a validity period, cannot be ordered from. Source
- Oracle's approved supplier list status controls whether a supplier may source an item or category and whether purchase orders for it can be approved. Source
- FAR 9.206-1(c): where a qualification requirement applies, only offers meeting it need be considered unless the offeror demonstrates before award that it meets the standards. Source
- FAR 9.207 lists conditions to report that may merit removal from a qualified list, including failure to request reevaluation after a change of plant location or ownership. Source
- Business Central purchase approval workflows use approval users with approvers, substitute approvers and amount limits. Source
- Business Central Copilot, a preview feature, suggests substitute items from item descriptions, references and attributes for the user to review. Source
- JEDEC defines a product or process change notice as a document describing product or process changes, their reasons and projected impact. Source
- The FDA's QMSR took effect February 2, 2026, amending 21 CFR Part 820 and incorporating ISO 13485:2016 by reference. Source
- The QMSR final rule notes that ISO 13485 clause 7.4 requires supplier evaluation based on ability and performance, proportionate to risk. Source
See if your company qualifies
A short company assessment. No data uploads are needed.