Decision Basis
Approved drawings, BOM, firmware, golden sample, test criteria, order, lot, and change records.
After-Sales and Quality Response
How to Report and Resolve a Product Quality Issue
Share the model, order lot, affected quantity, symptom, and field evidence. Yuli first confirms the affected scope, then organizes sample analysis, root-cause verification, corrective action, and closure.
Response timing, responsibility, and disposition follow the contract, purchase order, and quality agreement. Each case is tracked against the project, model, order, production lot, submitted evidence, and agreed response process.
Scope
Start with the delivered revision, then isolate the source of the issue
The review compares approved drawings, BOM, firmware, golden samples, inspection criteria, purchase orders, lots, and change records so that different product revisions are not mixed in one analysis.
Yuli Scope
Hardware, firmware, cold-press manufacturing, production tests, and agreed packaging supplied by Yuli.
Customer Scope
Product and mechanical definition, brand and instructions, channel, end use, platform accounts, and customer-nominated materials.
Issue-Response Process
Six steps take an issue from intake to verified closure
01
Issue Intake
Record project, model, order, lot, quantity, symptom, occurrence rate, environment, and first-detection time.
02
Containment
Confirm affected stock, goods in transit, and shipped quantity. Yuli checks work in process and same-lot materials, then both parties agree the immediate containment action.
03
Evidence and Samples
Collect photos, video, logs, test data, failed units, and control samples, including transport and teardown condition.
04
Root-Cause Analysis
Check hardware, firmware, material, cold-press process, production tests, logistics, and use conditions against the available samples and records.
05
Corrective Verification
Define immediate and permanent actions, verify them through comparative tests or a pilot build, and review certification and production impact.
06
Closure and Prevention
Both parties confirm responsibility, disposition, affected scope, and closure criteria; update BOM, firmware, process, inspection, or supplier controls as needed.
Required Evidence
Complete evidence shortens reproduction and diagnosis.
If a failed sample is unavailable, provide repeatable steps and field data. Personal or customer information may be redacted before submission.
| Identification | Project, model, order, lot, serial number, hardware/firmware revision |
|---|---|
| Issue Description | Symptom, rate, time, environment, steps, reproducibility |
| Evidence | Photos, video, logs, measurements, failed and control samples |
| Field Action | Stock, in-transit and sold quantities, containment, and required decision date |
Responsibility and Disposition
Choose the corrective action after the cause is confirmed
Within Yuli’s Supply Scope
When the confirmed cause is within Yuli-supplied hardware, firmware, cold-press manufacturing, testing, or agreed packing, the project team implements the corrective action defined in the agreement.
Outside the Supplied Scope
For customer-defined structures, nominated parts, unapproved changes, storage, transport, or field-use conditions, both parties confirm the analysis scope and corrective plan before work begins.
Joint or Pending Analysis
Where the cause is shared or still under review, both parties agree samples, test methods, temporary disposition, and any third-party testing before closure.
RMA, 8D, and Channel Support
Use the process that fits the issue and business impact.
RMA
Before returning units for analysis, repair, or replacement, confirm the RMA number, quantity, serials, packing, transport, receipt, and disposition authority.
8D
Use 8D for recurring, volume, or customer-required issues. The report should cover team, problem definition, containment, root cause, permanent action, verification, prevention, and closure evidence.
Channel Support
The customer owns end-user and channel communication, consolidates similar issues, and protects user privacy. Yuli provides B2B technical analysis, revision data, and disposition advice to the project contact.
Submit issue evidence to start quality analysis.
Provide project, model, order, lot, affected quantity and rate, field conditions, photos or video, logs, and failed samples where available.