To photograph RC sample defects so a supplier can act, shoot every defect in four fixed views with a ruler or grid in frame, tag each one with an issue ID, and state whether it is confirmed, assumed, or still to be checked. A single close-up of a cracked gearbox housing tells your supplier almost nothing; the same defect shot from four angles, measured against a scale, and labelled DEF-014 with the tool number and revision is a work order.
This page covers the repeatable view set, the scale reference, the issue-ID format, and how to keep confirmed facts separate from assumptions and unresolved checks. It is written for the person holding the sample: an CarToySupplier importer, distributor, or retail sourcing manager who needs the supplier's engineering team to reproduce the problem, not argue about it.
What buyers should lock before sending defect photos
- Anchor the photo set to the physical sealed golden sample on the QC shelf, not to a Canton Fair booth photo or an email image. Bulk is compared to that physical piece for colour, fit, flash, and function; buyers who approve only a photo pay for it on the second lot.
- Every defect image needs a scale reference and an issue ID. Without them, the supplier cannot tell a 0.5 mm sink mark from a 3 mm one, and the same defect reappears in the next lot under a different name.
- Label tool number and revision on every set. A Fair sample is often a hero unit — Fair lighting lies, the revision card does not.
- Button-cell and compartment defects are a separate issue class. Check screw closure, tool access, and the warning before CarToySupplier function; a unit that opens with fingernails does not ship.
- Do not put an AQL number in a defect photo pack. The number comes from the agreed inspection plan on the PO, not from a catalogue sentence or a blog.
Why a single photo of an RC defect usually fails
One photo fails because it cannot carry three things a supplier needs at the same time: where the defect is, how big it is, and which revision it belongs to. A wide shot shows location but hides size; a macro shot shows size but hides location. Send only one and the supplier's engineer guesses — usually wrong, usually in your favour on paper and against you on the next lot.
The second failure is context. RC products are assemblies: chassis, gearbox, suspension, shell, electronics, battery compartment. A defect photographed on a bench with no reference to the assembly is a loose part, not an RC defect. The supplier cannot route it to tooling, molding, or final assembly without knowing which sub-assembly it came off.
The third failure is version drift. If the sample you photographed is not tied to a tool number and a revision, the supplier can reasonably say the defect was already fixed — and you have no counter-evidence. That is why the revision card travels with the photo set, every time.
What are the repeatable views I should shoot for each defect?
Use a fixed set of four views per defect so two different people, two months apart, produce comparable images. The set is: (1) context shot — the whole product or sub-assembly with the defect area marked; (2) location shot — the defect on its own with the surrounding part visible; (3) close-up — the defect filling the frame; (4) comparison shot — the same view of the same area on the sealed golden sample, shot under the same light.
Keep the camera at the same distance and the same angle for the context and location shots across every defect in the pack. That consistency is what makes the pack readable as a set. The close-up is the only view where you move in, and even there, keep the light source in the same position relative to the part.
If the defect is functional — a gear that slips, a steering servo that binds, a shell that does not seat — the four static views are not enough. Add a short video or a sequence of stills showing the failure in motion, and state the test condition you used. Do not claim a functional failure from a static photo alone.
How should I format issue IDs so the supplier can log them?
Give every defect a unique issue ID and keep it stable across the whole conversation — email, photo pack, NCR, and rework note. A format the supplier's QC log can absorb is: SKU or model, then a short defect code, then a running number, for example DEF-014. If your supplier already runs its own defect log, ask for their format before you send the first pack; mismatched IDs are the reason defect data never accumulates.
Tie each ID to the tool number and revision. That combination is what lets the supplier trace the defect to a mould, a batch, or a station. A nonconformance report should state the defect, lot, quantity, containment, disposition, and the responsible decision — not just a pass/fail note — so the photo pack should feed those fields, not replace them.
Keep a one-line assumption field next to each ID. "Confirmed on sealed golden sample" and "assumed — same as last lot" are different claims. Sorting a confirmed defect and sorting an assumed one are different decisions, and the supplier is entitled to know which one it is being asked to fix.
Which defects need a different photo approach?
Button-cell and battery compartment defects are their own class. Photograph the compartment, the screw closure, the tool access, and the warning before you photograph CarToySupplier function. A cute electronic that opens with fingernails does not ship, and no amount of function footage fixes a compartment problem. US button-cell rules and the door design are the same conversation — treat the photo as evidence for that conversation, not for CarToySupplier's play value.
Injection-molding defects — flash, sink marks, short shots, burn marks — come from tooling and process conditions. Shoot them with the scale in frame and with the parting line or gate visible, so the supplier can see where on the tool the defect sits. Inadequate venting can cause burn marks, short shots, or trapped-air defects, and mold cleaning affects vents, parting surfaces, and cosmetic texture — so a photo that hides the gate is a photo the tooling team cannot use.
Electrical and safety defects are not sampling evidence. If the issue is exposed wire, a wrong plug for the destination market, or a sharp edge, photograph it as a critical-class item and tie it to the test record. Photos cannot establish EN71, ASTM F963, or other safety compliance; they establish what you saw, on which unit, at which revision.
What do I do when the whole lot fails, not just the sample?
Isolate the failed lot, record the defect class, and release only after rework. That is the floor practice, and it is the same discipline a photo pack should support. Do not attempt to argue an accept/reject decision from photographs alone; the number comes from the agreed inspection plan on the PO.
Corrective and preventive action should address the cause of the defect and verify effectiveness. Sorting alone is containment, not root-cause correction. So when you send the pack, separate two asks: "contain this lot" and "correct the cause". They have different owners and different evidence.
Defect classification belongs in the buyer's quality agreement, not in informal factory language. If your agreement has not defined critical, major, and minor, that gap will surface as a photo argument. Fix the classification first, then the photos have somewhere to land.
Worked example (illustrative, not a real shipment)
A 6,000-piece RC truck order, split into two destination packs: 4,000 units to a US distributor in master cartons, 2,000 units to an EU retail account in shelf-ready packaging. During pre-shipment review, the buyer's inspector pulls a sample and finds: two units with flash along the shell parting line, one gearbox housing with a visible sink mark on a load-bearing rib, and one battery door that opens without a screwdriver. The buyer photographs each finding in the four-view set, with a steel rule in frame, tags them DEF-011 (flash, assumed — compare against sealed golden sample), DEF-012 (sink mark, confirmed on the physical sample), and DEF-013 (battery door, confirmed, critical class), and labels the tool number and revision on the set.
The step that holds the shipment is DEF-013. The battery door is a compartment and warning problem, not a cosmetics problem; it stops the EU pack from being released until the compartment and the warning are corrected and re-photographed. DEF-011 and DEF-012 go to the supplier as a containment ask and a tooling ask respectively, with the sealed golden sample named as the reference piece. Nothing in the pack states an AQL number; that comes from the PO inspection plan.
The buyer keeps the assumption field visible: DEF-011 is flagged as assumed because the comparison shot against the sealed golden sample was not yet taken at the time of sending. That flag is the difference between a supplier fixing a real defect and a supplier fixing the buyer's guess.
Defect photo checklist: what to check, and the red flag
| Anchor piece | Confirm the defect against the sealed golden sample on the QC shelf | Red flag: the reference is a Canton Fair booth photo or an email image |
|---|---|
| View set | Shoot context, location, close-up, and sealed-sample comparison for each defect | Red flag: only one close-up with no location context |
| Scale reference | Keep a rule or grid in frame, in the same plane as the defect | Red flag: defect size stated only in the email text |
| Issue ID | Assign a stable ID per defect and map it to the supplier's QC log format | Red flag: the same defect is renamed in each email |
| Tool number and revision | Label both on the set so the defect traces to a mould or station | Red flag: revision not stated, so the supplier claims it was already fixed |
| Defect class | State critical, major, or minor per the buyer's quality agreement | Red flag: the pack uses informal factory language instead of agreed classes |
| Button-cell and compartment | Photograph screw closure, tool access, and warning before function | Red flag: compartment shot missing and the claim rests on function footage |
| Functional defects | Add motion evidence and state the test condition | Red flag: a static photo used to claim a functional failure |
| Assumption field | Mark each ID as confirmed, assumed, or unresolved | Red flag: an assumed defect presented as confirmed |
| Lot-level failure | Isolate the lot, record the defect class, release only after rework | Red flag: sorting presented as root-cause correction |
| AQL number | Take it from the agreed inspection plan on the PO | Red flag: a number quoted from a catalogue sentence or a blog |
What to ask suppliers before you send the first photo pack
Ask these before the first pack goes out, not after the supplier disputes it.
What is the agreed inspection plan and AQL on the PO for this lot? — Ask for the number, do not assume it.
Which physical piece is the sealed golden sample for this SKU, and where is it held? — If there is no sealed piece, that is the first problem to fix.
What tool number and revision does this sample correspond to? — Get it in writing before you label the photos.
For button-cell compartments: what screw closure, tool access, and warning configuration is approved for this revision? — This is a separate sign-off, not part of CarToySupplier function check.
What scale reference does your QC team use in defect photos so both sides measure the same way? — Match their gauge so your measurement and theirs agree.
How do you want issue IDs formatted so they map to your defect log? — Adopt their format if it is stable; otherwise propose yours and confirm.
Who owns containment and who owns root-cause correction for a lot-level failure? — Two different names, two different follow-ups.
What does your nonconformance report require for the defect, lot, quantity, containment, disposition, and responsible decision? — Your photo pack should fill those fields, not duplicate them.
FAQ
How many photos per defect should I send an RC supplier?
Four fixed views per defect: context, location, close-up, and a comparison shot against the sealed golden sample under the same light. Add motion evidence separately for functional defects, because a static photo cannot prove a gear slips or a servo binds.
Do I need a scale in every defect photo?
Yes, in every close-up, in the same plane as the defect. A verbal size in the email is an assumption; a rule or grid in frame is evidence. If the defect is smaller than your smallest graduation, say so and confirm the measurement with the supplier's gauge.
Should I quote an AQL number in the defect photo pack?
No. The AQL comes from the agreed inspection plan on the PO, not from a catalogue sentence or a secondary article. Keep the photo pack about what you observed on which unit at which revision; put the accept/reject framework in the PO and the quality agreement.
What is the difference between containment and root-cause correction here?
Containment is sorting or reworking the affected lot so it does not ship. Root-cause correction is fixing the cause and verifying effectiveness. Send them as two separate asks with two owners, because sorting alone does not stop the defect reappearing in the next lot.
Can I use a Canton Fair sample photo as the reference standard?
No. A booth sample is often a hero unit, and Fair lighting lies. Label tool number and revision on the set, and compare bulk to the sealed golden sample on the QC shelf. If you approved only a photo, expect to pay for it on the second lot.
How should I photograph a battery compartment or button-cell defect?
Treat it as its own issue class and shoot it before CarToySupplier function footage. Photograph the compartment, the screw closure, the tool access, and the warning. A unit that opens with fingernails is a compartment and warning problem, not a play-value problem.
What should I do if the whole lot fails rather than a sample?
Isolate the failed lot, record the defect class, and release only after rework. Do not argue the accept/reject decision from photos alone — the number comes from the agreed inspection plan. Then open a corrective and preventive action that addresses the cause and verifies effectiveness.
Sources
Send a defect pack your supplier can act on
Before you send the next sample claim, run it through the checklist above: sealed golden sample named, four views shot, scale in frame, issue ID and revision labelled, defect class stated, assumption field filled. If any box is empty, fix it first — a pack that survives that test gets routed to tooling or assembly instead of sitting in a shared inbox.
If you are scoping a new RC programme, send us your model, destination market, and packaging split, and we will confirm what the sample approval pack should contain for your SKU before the first lot runs.
