Skip to content

Systems and records

Supplier quality dispute evidence data: which spec revision applies?

By SourceX Editorial · Reviewed by Noah Loul ·

10 sections

Short answer

Use the revision the purchase order named or incorporated, as changed by engineering changes and deviations the buyer approved before shipment and in force when risk passed to the buyer. Do not default to the latest revision in the engineering system or to the plan the receiving inspector used. Record change numbers with valid-from dates, risk transfer point and inspection plan revision so a validator can recompute the answer.

Checklist

Supplier quality dispute

This page covers supplier quality dispute evidence data: which spec revision applies.Illustrative

Key takeaways

  • The governing specification is set by the order, approved changes and deviations, and the risk transfer date, not by the current drawing.
  • Store change numbers with valid-from dates; a revision letter alone cannot show which state applied to a shipment.
  • Check that receiving inspection and supplier certificates cite the governing revision, and flag any mismatch.
  • Keep failing records with their reasons; they teach models to check dates before drawings.
  • Liability, notice deadlines and document rights are separate questions for counsel and a data rights reviewer.

Which specification version belongs in a shipment quality dispute task?

The specification that belongs in the task is the revision the purchase order or contract incorporated, as changed by any engineering change or deviation the buyer approved before the goods shipped, and effective on the date risk passed to the buyer. It is usually not the latest revision in the engineering system, and it is not automatically the revision the receiving inspector used.

Getting this wrong turns a quality dispute dataset into noise. A lot that conformed to revision C will look nonconforming against revision D, and a model trained on those records learns to reject good parts and to cite the wrong document.

This page gives a schema for recording a dispute so the governing revision can be proved from linked evidence: the fields, a validator, a valid worked record and a failing one. All records shown are illustrative and are not customer data.

Why the current revision in PLM is usually the wrong one

Engineering and ERP systems show the specification as it is now, while a dispute is about the specification as it was then. Unless the task pins the effective date, whoever builds it will pull the current drawing.

SAP's engineering change management documentation shows why dates carry the meaning. A change number carries a valid-from date that sets when a change to a bill of material takes effect, and the changed object is stored in a pre-change state and a post-change state, with the post-change state starting on the valid-from date. A dispute record that stores only a part number and a revision letter, without the change number and its valid-from date, cannot show which state applied to a given shipment.

Inspection plans and receiving instructions drift in the same way. If the receiving team updated its inspection characteristics to the new revision before old-revision stock arrived, the inspection result is a comparison against a document the supplier was never asked to meet.

What sales law and standard inspection clauses say about timing

Commercial law ties conformity to the contract description and to a point in time, and it puts deadlines on inspection and notice. These rules shape which fields a dispute record needs; whether a specific claim succeeds is for counsel.

Under UCC section 2-313, a description of the goods that is part of the basis of the bargain creates an express warranty that the goods will conform to that description, which is why the revision named or incorporated in the order matters. Section 2-513 gives the buyer a right to inspect before payment or acceptance at a reasonable place, time and manner, and when the seller ships the goods, inspection can take place after arrival. Section 2-607 requires a buyer who has accepted goods to notify the seller of a breach within a reasonable time after discovering it, or be barred from any remedy.

For international sales covered by the UN Convention on Contracts for the International Sale of Goods, Article 35 requires goods of the quantity, quality and description required by the contract, and Article 36 makes the seller liable for a lack of conformity that exists when risk passes to the buyer, even if it only becomes apparent later. Article 38 requires examination within as short a period as is practicable, and Article 39 requires notice within a reasonable time and, in any event, within two years of actual handover unless a contractual period of protection says otherwise.

U.S. federal supply contracts show what a standard inspection clause asks for. FAR 52.246-2 requires the contractor to keep an inspection system and records of all inspections and their outcome, lets the government reject or require correction of supplies that do not conform to contract requirements, and makes acceptance conclusive except for latent defects, fraud, gross mistakes amounting to fraud, or as the contract otherwise provides. Many commercial supply agreements contain similar language, so the schema records acceptance status and date explicitly.

The versioned specification and inspection evidence schema

The schema links one disputed lot to the order, the governing specification state, every approved change and deviation, and the inspection evidence on both sides. Each field has a purpose and a link it must resolve to, so a reviewer can rebuild the answer from the record alone.

The versioned specification and inspection evidence schema
FieldPurposeMust link toValidation rule
po_line_id and po_dateIdentifies the commercial commitment and when it was madePurchase order linePO date is on or before ship_date
spec_ref_on_poThe part number, drawing or specification and revision the order named or incorporatedSpecification document and revisionRevision existed on po_date
change_noticesEvery engineering change or specification revision affecting the part, with change number and valid-from dateChange recordsOrdered by valid-from date; none missing between spec_ref_on_po and ship_date
deviations_waiversApproved departures from the specification for this supplier, part or lot, with approver and approval dateDeviation or waiver recordApproval date and lot scope recorded; approver role on the authority list
ship_date and risk_transfer_pointWhen the lot shipped and where risk passed under the agreed delivery termShipping documents, delivery termBoth present; risk transfer point named, not inferred
governing_spec_stateThe revision plus approved changes and deviations in force at risk transferDerived from the fields aboveRecomputed by the validator; must equal the stored value
supplier_inspection_evidenceSupplier test reports, certificates of conformance or analysis, with the revision they citeSupplier documentsCited revision equals governing_spec_state or the mismatch is flagged
receiving_inspectionInspection lot, plan revision, sample size, results, usage decision and dateInspection lot and planPlan revision equals governing_spec_state; inspection date after receipt
notice_and_acceptanceDate of nonconformance notice to supplier, acceptance or rejection status and dateQuality notification, correspondenceNotice date recorded relative to receipt and discovery
disposition_and_outcomeReturn, rework, use-as-is, price adjustment or claim, and the confirmed resultDisposition record, credit or replacement receiptOutcome confirmed by a later transaction, not only by the notification status

Validator checks that catch the wrong revision

A validator should recompute the governing specification from the linked records and fail any record whose stored answer disagrees. These checks can be run as a script over an export or by hand on a sample.

At a glance

Validator checks that catch the wrong revision

  • Revision timeline: every change notice between spec_ref_on_po and ship_date is present, sorted by valid-from date, with no gaps in the revision sequence.
  • Effective-state recomputation: apply approved changes with a valid-from date on or before the risk transfer date, then deviations approved before shipment and scoped to the lot; the result must equal governing_spec_state.
  • Inspection alignment: the receiving inspection plan revision and any supplier certificate must cite governing_spec_state, or the record carries an explicit mismatch flag.
  • Date order: po_date, ship_date, receipt, inspection, usage decision and notice must appear in a plausible order; inspection before receipt fails.
  • Authority: every deviation, waiver and disposition has an approver whose role appears on the authority list for that decision.
  • Outcome evidence: a closed quality notification needs a later credit, replacement receipt, rework record or written settlement before the outcome is labeled confirmed.

A valid worked record, labeled illustrative

This record is illustrative. A buyer's purchase order names a machined bracket at drawing revision C. An engineering change to revision D, tightening a hole-position tolerance, carries a valid-from date three weeks after the lot shipped. No deviation applies. The delivery term places risk transfer at the supplier's dock on the ship date.

At receipt, the inspection lot was created against an inspection plan already updated to revision D. Of a sample of 32 parts, 5 fell outside the revision D tolerance and all 32 were inside the revision C tolerance (illustrative counts). The usage decision, which in SAP records whether the goods in an inspection lot are accepted or rejected, rejected the lot, and a complaint against the supplier was raised as a quality notification; SAP predefines a notification type for complaints against a vendor that can reference the material, purchase order or delivery.

The validator recomputes governing_spec_state as revision C, because the revision D change took effect after risk transfer. Inspection alignment fails: the plan revision is D. The correct task answer is that the lot conformed to the specification that governed the shipment, the rejection rested on the wrong revision, and the dispute should be withdrawn or reinspected against revision C. The confirmed outcome is a reversal of the rejection and acceptance of the lot, recorded by a later usage decision and goods movement.

A valid worked record, labeled illustrative
FieldIllustrative valueValidator result
spec_ref_on_poBracket drawing, revision CPass: revision existed on PO date
change_noticesChange to revision D, valid-from three weeks after ship datePass: complete timeline
governing_spec_stateRevision C, no deviationsPass: matches recomputation
receiving_inspectionPlan at revision D; 5 of 32 sampled parts outside D toleranceFlag: plan revision differs from governing state
disposition_and_outcomeRejection reversed after reinspection to revision C; lot acceptedPass: confirmed by later usage decision

A failing record and the checks it trips

A failing record is one whose stated answer cannot be rebuilt from its own links. Keep failing records in the dataset with their failure reasons; they are the examples that teach a model to check the date before the drawing.

In this illustrative failure, a record for the same bracket stores governing_spec_state as revision D because that was the current revision when the dispute was logged. The change_notices field lists revision D but omits its valid-from date, the deviation field is empty, and the record has no risk_transfer_point. The validator fails it three times: the revision timeline is incomplete, the effective state cannot be recomputed, and the stored answer disagrees with what the order named. Labeled as is, the record would teach that the newest drawing always governs.

A second common failure is a deviation approved after the lot shipped and then applied backwards to justify acceptance. The validator should accept a later approval only if the record shows the parties agreed it applies to that lot, and should flag it for review either way.

When is the quickest disposition the wrong one?

The quickest disposition is often invalid because a constraint outside the inspection result controls it. A dispute task should include those constraints as linked facts so a model has to consider them.

  • Use-as-is looks cheapest, but the end customer's specification or a regulatory requirement may forbid accepting the deviation without customer approval.
  • Switching to an alternate supplier looks fastest, but the alternate may not be approved for this part or revision, so its parts would need their own qualification.
  • Rework in house looks obvious, but the supply agreement may give the supplier the right to correct or replace nonconforming goods first.
  • Rejecting the whole lot looks safe, but a late notice may limit the buyer's remedies under the applicable law or contract.
  • Accepting on the supplier's certificate looks efficient, but a certificate citing an outdated revision does not show conformity to the governing one.

What the schema cannot decide

The schema establishes which revision governed and whether the evidence matched it; it does not decide liability, damages or whether a notice was timely enough. Those questions depend on the contract, the applicable law and the facts, and belong with counsel and the procurement lead.

Sampling limits what any record can show. A lot accepted on a sampled inspection can still contain latent defects, and an inspection result is only as good as the measurement method and gauge behind it. Record sample sizes and methods rather than turning a sample into a statement about every part.

Drawings and specifications often belong to the buyer's customer or carry supplier proprietary data. Before any dispute record leaves the company, a data rights reviewer should confirm that the documents can be used outside the original supply relationship, and supplier and customer names should be handled under the agreements that cover them.

Quality dispute histories as licensed data

Dispute histories where the order, every revision, the inspections and the outcome are linked are among the more useful procurement and quality records for training and evaluating agents, because they test reasoning over time rather than lookups. They are also among the hardest to assemble, which is why a schema like this one matters before anything is shared.

Licensing a quality dispute history through SourceX puts sourcing, rights review, contracting, preparation and delivery in its hands. No dispute record is delivered until the company has approved the scope and terms and signed the agreement, and a brief company assessment, with no data upload, shows first whether its quality and procurement history fits.

Frequently asked questions

Does the latest specification revision apply to a quality dispute?

Usually not. The governing revision is normally the one the order named or incorporated, plus changes and deviations the buyer approved before shipment and in force when risk passed. The contract can say otherwise, so check its terms.

What if receiving inspection used a newer inspection plan?

Then the inspection result may compare the lot against a requirement the supplier was never asked to meet. Flag the mismatch, reinspect against the governing revision where possible, and record both results rather than overwriting the original.

How long does a buyer have to report a nonconformance?

It depends on the contract and the law. The UCC requires notice within a reasonable time after discovery for accepted goods, and the CISG adds an outer limit of two years from handover unless the contract sets its own period of protection. Counsel should confirm the deadline for a specific dispute.

What records prove which specification applied at shipment?

The purchase order line, the specification revision it cites, the change records with their valid-from dates, any approved deviations, and shipping documents showing the date and risk transfer point. Supplier certificates help only if they cite the same revision.

Can supplier quality dispute records be licensed for AI training?

Sometimes, after review. Drawings and specifications may belong to customers or suppliers, and quality agreements often restrict sharing, so a data rights reviewer should confirm use rights before any record is prepared.

Sources

  • FAR 52.246-2 requires the contractor to keep inspection records, lets the government reject or require correction of nonconforming supplies, and makes acceptance conclusive except for latent defects, fraud, gross mistakes amounting to fraud, or as the contract provides. Source
  • UCC 2-313: a description of the goods that is part of the basis of the bargain creates an express warranty that the goods will conform to the description. Source
  • UCC 2-513: the buyer may inspect before payment or acceptance at a reasonable place, time and manner, and after arrival when the seller ships the goods. Source
  • UCC 2-607(3)(a): a buyer who has accepted goods must notify the seller of breach within a reasonable time after discovery or be barred from any remedy. Source
  • CISG Articles 35, 36, 38 and 39: conformity to contract description, seller liability for nonconformity existing when risk passes, examination as soon as practicable, and notice within a reasonable time and at most two years from handover. Source
  • SAP quality notifications include a predefined type for complaints against a vendor and can reference a material, purchase order or delivery. Source
  • In SAP, the usage decision confirms the inspection is complete and records whether goods in the inspection lot are accepted or rejected. Source
  • SAP engineering change management uses a change number with a valid-from date; each changed object is kept in a pre-change and a post-change state, and the post-change state starts on the valid-from date. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies