The short answer
Choose repair or replacement only after safety screening, applicable customer-remedy obligations, exact product identification, and a reliable diagnosis. Compare approved parts, installer competence, labor, transport, battery restrictions, expected resolution, customer downtime, warranty, and total cost. Stop ordinary service when the issue requires safety escalation, recall handling, or specialist assessment.
Sending a low-cost component can be more expensive than replacing a vehicle if the diagnosis is wrong, the customer cannot install it, or a second failure follows. Replacing every product also wastes stock and can hide recurring causes.
This guide helps importers set a consistent remedy process. Consumer rights and warranty duties vary by market and should be reviewed with qualified advisers for the actual program.
1. Screen safety and customer obligations first
Ask about injury, smoke, odor, unusual heat, swelling, electrical damage, water, impact, steering, stopping, and earlier modification. Urgent conditions need the appropriate stop-use and escalation route before ordinary repair economics are considered.
Review the relevant market’s consumer-remedy requirements, retailer obligations, warranty terms, sale date, and case facts. Commercial policy should not remove rights supplied by law. A product involved in a safety action or recall must follow the applicable corrective-action process rather than a routine parts decision. Keep this gate separate so a cheap proposed fix cannot quietly override the responsible safety or legal owner.
What to confirm before approval
- Complete safety and rights screening.
- Identify ordinary service versus special action.
- Escalate before selecting a routine remedy.
2. Confirm the product and probable cause
Collect model, batch, battery and charger, configuration, symptoms, history, approved observations, and any qualified measurements. Distinguish the reported symptom from the verified fault and the cause. No movement can arise from several systems, not just the motor.
Decide whether the available evidence is strong enough to choose a part. Repeated blind parts dispatch increases delay, freight, customer frustration, and no-fault-found stock. Use service-only diagnostics where needed and protect customers from unsafe testing. If diagnosis remains uncertain, compare specialist inspection or replacement rather than pretending one inexpensive component has a guaranteed resolution.
What to confirm before approval
- Identify exact vehicle and service revision.
- Separate symptom, fault, and cause.
- Set the evidence threshold for part dispatch.
3. Check whether repair is actually supported
Verify the exact part, paired parts, instructions, access, tools, skills, installation responsibility, post-service check, warranty, and time. A compatible component may still be unsuitable for customer installation if access or validation requires qualified work.
Review the condition of the surrounding product. Structural damage, water exposure, multiple faults, unknown modifications, missing identity, or damaged batteries may change the appropriate route. Do not turn an unsupported battery conversion, controller substitution, improvised connector, or protection bypass into a low-cost repair option. The remedy must restore the approved product, not create a new undocumented configuration.
What to confirm before approval
- Confirm part compatibility and installer role.
- Assess surrounding product condition.
- Define post-repair acceptance and documentation.
4. Calculate total resolution cost
Include part, labor, outbound freight, return freight if applicable, diagnostic time, packaging, battery handling, customer support, replacement stock, tax or administration, repeat contact, and likely failed-remedy cost. Use actual contracted rates and clearly stated assumptions.
Account for customer time, accessibility, distance from service, urgency, and the practical probability of resolution. Avoid fixed percentage rules that claim repair is always sensible below a certain fraction of retail price. The economics differ between a charger sent to a customer, a dealer wheel repair, and a complete battery-powered product return. Compare supported scenarios rather than just the purchase price of the part.
What to confirm before approval
- Use complete remedy cost.
- Include repeat-failure and support effort.
- Consider customer access and downtime.
5. Control return, replacement, and repaired stock
If a return is needed, screen battery and product condition before issuing transport instructions. Provide a compliant route, suitable packing, case ID, receiving quarantine, and disposition. Replacement products should be inspected and traceable, not automatically selected from unknown returned stock.
For repaired goods, record the fault, parts, installer, checks, condition, labels, documentation, and resale or return-to-customer status. Define whether warranty continues, restarts, or follows another legally required treatment. Do not mix repaired, new, held, and salvaged inventory. Clear status control prevents the same unresolved vehicle from entering another customer journey.
What to confirm before approval
- Screen transport before issuing labels.
- Segregate new, repaired, held, and salvage stock.
- Record checks and legal warranty treatment.
6. Measure resolution and recurring cause
Track remedy chosen, first-time resolution, repeat contacts, customer downtime, total cost, part returns, no-fault-found results, model, batch, and verified cause. Evaluate whether a low visible repair cost actually produced a reliable result.
Share patterns with engineering, quality, logistics, documentation, and the supplier. Repeated charger replacements may indicate storage or diagnostic issues; repeated body damage may implicate pack-out rather than part quality. Use those findings to change the product or process and verify the next outcome. A good repair-or-replace policy should reduce recurring causes as well as settle individual cases.
What to confirm before approval
- Measure first-time resolution and complete cost.
- Link remedies to model, batch, and cause.
- Feed patterns into corrective action.
7. Worked example: apply the decision to a real order
The following scenario is illustrative. It explains a decision method rather than reporting a CubRover customer project, measured test result, certification, or completed shipment.
A dealer receives a no-movement case and considers shipping a motor assembly. The symptom video shows lights functioning, but the exact controller revision and battery condition are not yet identified.
The support team collects model and component labels and completes approved triage. It finds that a qualified local check is needed before deciding. One path is a verified compatible repair at the dealer; another is a replacement with a screened return route. Both are costed using labor, transport, customer delay, and expected resolution rather than motor price alone.
The selected remedy is authorized and its outcome recorded. If the returned part is healthy, the diagnostic process is reviewed. This scenario illustrates decision control; it does not establish a universal economic threshold or assume a specific consumer-law result.
| Gate | Required question | Decision |
|---|---|---|
| Safety and rights | Is ordinary service appropriate? | Escalate or continue |
| Diagnosis | Is the fault sufficiently identified? | Inspect, repair, or replace |
| Feasibility | Can approved service restore the product? | Choose supported method |
| Economics | What is total resolution cost? | Authorize and verify remedy |
Questions to include in the buyer decision brief
Convert the review into questions that the supplier can answer against one named model and order. The following prompts come from the topic-specific approval checks above. They are intentionally practical: each answer should identify the responsible party, supporting record, open condition, and date by which the buyer can make the next decision.
- Screen safety and customer obligations first: Complete safety and rights screening. Identify ordinary service versus special action. Escalate before selecting a routine remedy.
- Confirm the product and probable cause: Identify exact vehicle and service revision. Separate symptom, fault, and cause. Set the evidence threshold for part dispatch.
- Check whether repair is actually supported: Confirm part compatibility and installer role. Assess surrounding product condition. Define post-repair acceptance and documentation.
- Calculate total resolution cost: Use complete remedy cost. Include repeat-failure and support effort. Consider customer access and downtime.
- Control return, replacement, and repaired stock: Screen transport before issuing labels. Segregate new, repaired, held, and salvage stock. Record checks and legal warranty treatment.
- Measure resolution and recurring cause: Measure first-time resolution and complete cost. Link remedies to model, batch, and cause. Feed patterns into corrective action.
8. Turn the review into a controlled implementation plan
A useful buyer decision has three outputs: an approved requirement, evidence supporting that requirement, and a named person who can release the next activity. Keep these connected by model, configuration, market, document revision, and effective production date. If a supplier gives a conditional answer, preserve the condition in the purchasing record rather than shortening it into an unconditional product claim.
Use a remedy authorization form that records safety screening, rights review, exact diagnosis, service compatibility, installer, total cost assumptions, transport route, customer communication, post-service check, and final outcome. Keep exceptions visible for later trend review.
- Screen safety and legal obligations.
- Identify the product and diagnose sufficiently.
- Compare supported remedies and total cost.
- Authorize transport, installation, and stock status.
- Verify resolution and feed back the cause.
Agree evidence and acceptance before work starts
Write the review method before the sample, factory testing, document check, shipment inspection, or service exercise takes place. Specify the reference, sample selection, conditions, tools, result format, acceptance boundary, and response to a failure. This makes two quotations or results comparable and prevents teams from negotiating the meaning of a pass after money and time have already been spent.
Keep a compact, traceable decision file
Retain the original requirement, dated supplier response, model and component identity, relevant photographs, calculations, reports, deviations, approvals, and release decision. A screenshot can help communication, but retain the underlying record when it matters to the decision. Distinguish a proposed target from a measured value, an engineering sample from a production reference, and an internal check from a third-party assessment.
Use one current revision where possible. Purchasing, engineering, compliance, quality, logistics, sales, and service may need different views of the information, but they should not be making decisions from different versions of the product. When a change is approved, state the first affected batch and what happens to old materials, inventory, artwork, service parts, customer instructions, and pending shipments.
Review cost and timing together with product application
The lowest visible unit price may shift cost into testing, rework, freight, storage, retail setup, support, returns, or obsolete parts. Compare the complete customer requirement and the cost of supplying it consistently. Where a number is uncertain, show the assumption and a reasonable scenario range. Do not turn an illustrative calculation into a supplier promise or a universal benchmark for the category.
Reserve time for unresolved items. A sample modification may require another review; a component change may affect evidence; a carton revision may alter loading; a late document can affect handoff. Put the owner and decision date beside each open item. A useful schedule makes these dependencies visible instead of reporting one finish date that assumes every preceding decision will happen immediately.
Close the loop after delivery
After the first shipment or implementation, compare the approved assumptions with arrival condition, assembly preparation, actual costs, receiving accuracy, customer questions, service cases, and repeat-order results. Separate an isolated event from a recurring pattern using model, batch, channel, and time in use. When a discrepancy appears, contain the affected scope, identify the cause, implement the correction, and verify the next relevant outcome.
Primary resources for the specific source facts and frameworks discussed in this guide: CPSC toy-safety business guidance; PHMSA lithium-battery transport resources; EPA battery collection and recycling guidance.
Continue the related CubRover buyer workflow: warranty program guide; spare-parts forecasting guide; troubleshooting guide.
9. Conclusion and buyer handoff
A sound repair-or-replace decision begins with safety and rights, then uses diagnosis, technical feasibility, complete cost, controlled execution, and verified resolution. Track the cause so the next customer needs less support.
Before requesting a quote, share the destination market, selected product platform, target quantity, required configuration, channel, timing, and the decision you need the supplier to support. Attach the current requirement and identify open questions. This gives the factory a clear starting point for discussing samples, evidence, inspection, documents, packaging, and commercial responsibilities.
Frequently asked questions
Is repair always cheaper?
No. Diagnosis, labor, freight, repeat contact, parts compatibility, customer downtime, and failed remedies can outweigh part cost.
Can a low-cost part be sent before diagnosis?
Use an evidence threshold appropriate to the model and issue; blind replacement can create delay and risk.
Who decides whether the customer can install a part?
The approved model-specific service program and applicable requirements define permitted work and competence.
Can damaged battery products be returned normally?
Not automatically. Screen condition and obtain the appropriate transport route before issuing instructions.
Can repaired goods be sold as new?
Handle status, disclosure, condition, legal requirements, warranty, and traceability explicitly with qualified advice.
What outcome should the program track?
First-time resolution, repeat contact, cost, downtime, no-fault-found parts, verified cause, and recurring patterns.
Connect spare parts with reliable customer remedies
Discuss the product, market, and support capability your program requires.
Send Your Requirements