Trigger
Marketplace returns, service tickets, overseas-warehouse inspections or reviews show a recurring fault, and serial, batch and supplier information must be traced.
SCENARIO-DETAIL / LOCALIZED DECISION BRIEF
Business trigger: Marketplace returns, service tickets, overseas-warehouse inspections or reviews show a recurring fault, and serial, batch and supplier information must be traced.
REFERENCE_ARCHITECTURE · READBACK_VERIFY

DECISION RECORD / C.08
Source-traceable reference · pp.20–21
Marketplace returns, service tickets, overseas-warehouse inspections or reviews show a recurring fault, and serial, batch and supplier information must be traced.
Aggregate customer-side fault signals by model, firmware, batch, supplier and inspection standard, then drive CAPA, resale, refurbishment, disposal and knowledge updates.
If a serial number cannot be linked or accountability evidence is insufficient, keep the case undecided and do not treat an initial warehouse inspection as final responsibility. Quarantine returns involving safety or data privacy first.
Return events retain their sources; serials and batches are traceable; specialist decisions are approved; physical disposition has scan receipts; CAPA closes only after its observation window.
Choose one frequent return type and confirm serial-number coverage, quarantine rules and the CAPA observation window.
KNOWLEDGE → COMPARISON → DIRECTION → OPTIMIZATION
The full-detail canonical evidence record remains available in Chinese. IDs, Truth classes, boundaries, and source references stay unchanged across languages.
Source-traceable reference
Compare the same operating fields before choosing a direction.
Confirm the owner, authority, human gate, and readback rule.
Define a baseline, target, owner, and observation window before claiming impact.