Decision Basis
Approved drawings, BOM, firmware, golden sample, test criteria, order, lot, and change records.
After-Sales and Quality Response
B2B quality issues are traced to the product revision, lot, and responsible process.
Yuli quality response is based on approved drawings, BOM, firmware, golden samples, inspection criteria, and purchase orders, covering issue intake, containment, root-cause analysis, corrective verification, and closure.
The customer manages channel and end-user communication and consolidates issue evidence. Yuli investigates and supports corrections within the supplied hardware, firmware, and cold-press manufacturing scope. Warranty, RMA, replenishment, and costs follow the agreement and confirmed cause.
Scope
Compare the approved revision before assigning the issue to design, manufacturing, material, use, or logistics.
This page describes Yuli’s baseline B2B process. It does not promise a fixed warranty, unconditional returns, or standard compensation. Timing, responsibility, and cost must be defined in the contract, order, or project quality agreement.
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
Maintain one evidence trail from intake through closure.
01
Issue Intake
Record project, model, order, lot, quantity, symptom, occurrence rate, environment, and first-detection time.
02
Containment
The customer holds affected stock or shipments; Yuli checks work in process, stock, and same-lot materials, then both parties agree containment.
03
Evidence and Samples
Collect photos, video, logs, test data, failed units, and control samples, including transport and teardown condition.
04
Root-Cause Analysis
Verify hardware, firmware, material, cold-press process, tests, logistics, and use conditions; do not substitute assumptions for evidence.
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
Evidence and the agreed scope determine the result.
Yuli-Caused Issue
When evidence confirms a manufacturing, hardware, or firmware issue within Yuli’s scope, rework, rebuild, replenishment, repair, firmware correction, or another agreed action follows the contract.
Customer or Use Condition
Issues caused by customer-defined structure, nominated parts, unapproved changes, improper storage or transport, out-of-spec use, or channel handling are addressed through an agreed paid analysis or corrective plan.
Unconfirmed or Shared Cause
Agree samples, test method, third-party testing, temporary disposition, and cost handling first; assign final responsibility after the evidence is conclusive.
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.