At 9:07 on a Monday, a retailer sends four words: “Three bad units. Credit?” By lunchtime, the buyer has twelve chat screenshots, two box photographs and no reliable answer to the first question: which three units? That fictional example is ordinary enough to be useful. A complaint rarely arrives as a neat technical record. Someone has to turn it into one, preferably before devices, boxes and carton labels are separated.
9:10 — give the message a case number
Call this one RB-1105-03. The exact format is unimportant; using it everywhere is not. It goes in the subject line, the complaint log, the photo filenames and any return label. If the retailer later finds a fourth unit, that unit becomes 03-D rather than “the other red one.”
The next entry comes from the package, not the chat. Copy Razzbar, the full model name, flavor, capacity tier, nicotine statement where applicable, and package version. The Razzbar range includes several capacity tiers. A message saying “the big Razz one” may be perfectly clear across a shop counter and useless after it reaches purchasing.
Before leaving the identity block, add the purchase order or invoice, the receiving date and the warehouse location. Compare the box wording with the current product catalog. Nothing technical has been decided at this point. The buyer is merely proving that the photographed unit came from the order now on screen.
In the example, the retailer typed “160K strawberry.” The box image shows a different capacity tier. The buyer fixes that identity error now. Had it survived into the supplier email, every later question would have started from the wrong product.
9:25 — ask for a small, usable photo set
“Send more photos” tends to produce more files, not better evidence. Ask for five named views: complete device, front of box, specification side of box, outer-carton or batch mark, and the reported condition. A hand may hold the label flat, but it should not cover the reference being recorded.
The files for the first unit might read:
– 03-A-device
– 03-A-box-front
– 03-A-box-side
– 03-A-carton
– 03-A-detail
Keep the originals. A messaging-app screenshot may be smaller, stripped of useful file information and cropped just above the batch mark. The neatest photograph is not always the most useful one.
There is a place for video. An indicator that responds only sometimes is difficult to show in a still image. Start the clip with unit A next to its box; then show the event. Without that opening frame, a ten-second video of a blinking light can be detached from its product as soon as it is forwarded.
Some supported packages carry a security code. Use the official product verification process, record the result and date, and mask the usable code in any copy sent outside the case team. The result helps establish identity. It does not establish why a light failed, liquid appeared in a box or a draw became intermittent.
9:50 — replace the verdict with a timeline
The retailer has written “dead battery.” Leave that phrase in the original message, but do not promote it to a finding. Ask what happened, and when. The working note may look like this:
> 3 November: customer opened package. Indicator lit during first charge. 5 November: customer connected the same cable; no indicator response. 6 November: retailer received the unit. Warehouse inspection not completed.
Not elegant. Very useful.
Use labels for the source of each statement. “Customer reported” means nobody on the distributor’s team has checked it. “Warehouse observed” belongs to what staff saw on the returned item. “Confirmed” should wait for an agreed check or supplier review. Otherwise, a customer’s guess can become “confirmed battery failure” simply by being copied through three departments.
Fill in what the reporter can genuinely recall: rough use period, charging history, cable, power source and whether the event happened twice. Leave voltage, temperature, runtime and charge time alone unless somebody recorded them. A blank cell may look unfinished. A guessed number looks finished and sends the review in the wrong direction.
There is one hard stop. Heat, swelling, leakage or physical damage ends the counter-top experiment. Put the unit aside in line with supplier instructions and local rules; don’t open it, pierce it or try a repair. Staff can still photograph the exterior, capture the package references and write down why normal handling stopped.
10:20 — ask different questions for stock and returns
Unit A has been used. Unit B is still sealed inside a stained box. Treating them as one symptom would erase the difference.
For the used unit, ask where the trouble entered the story. At opening? On the first charge? On Friday, after several days? If another cable was tried and the instructions permitted it, name that cable. “Black Type-C cable from counter two” can be checked later. “Charged normally” cannot.
For sealed stock, start at the loading door. When did the carton arrive, where did it sit, and did anyone see crushing, moisture or stains? Add warehouse transfers. A dry carton isn’t a clean bill of health. It is simply one observation from the journey.
Keep packaging and operating complaints separate. A wrong flavor label, leaking unit box, intermittent draw and crushed master carton are four records, even if all four reached the desk in one morning. They can be connected later if evidence supports it. The log should not make that leap on its own.
11:00 — check whether three cases are really one pattern
The word “batch” often appears too early. Three complaints deserve attention; they do not automatically describe every unit in a shipment. Put each unit on its own row with model, flavor, package version, batch reference, observed condition, date and status.
Then add the denominator when it is available. Four reports among 40 units and four among 4,000 units create different commercial questions. Neither fraction identifies the cause. Both are better than “a lot of customers complained.”
Sameness matters. Four units bearing one batch reference and showing the same recorded indicator behavior may justify a grouped escalation. Unit A with no indicator response and unit B with a stained unopened box do not form that group just because their case numbers are consecutive.
The supplier wording should preserve the limit. “Four units marked batch X showed no indicator response during the documented check” is a report that can be reviewed. “Batch X contains defective batteries” is a conclusion the photographs and timeline have not proved.
11:30 — send one email that can be read once
Begin with the order reference and RB-1105-03. Follow with exact product identity, affected quantity, batch reference and the short sequence of events. List the attachments in order. End with the decision needed: return instructions, handling guidance, package-identity confirmation, replacement review or advice about which samples to retain.
Use the official after-sales support channel. Resist the temptation to forward the whole customer chat. If the question concerns box identity and a batch mark, a home address and telephone number add noise and risk. Keep only the personal details the distributor’s own service process calls for.
Razzbar’s quality-control overview describes checks from components through assembly and shipment inspection. That context does not identify the unit on this desk. The case still needs its order, model, package, batch reference and evidence.
The email can be brief. Its file list should be boring: 03-A-front, 03-A-carton, 03-A-detail. Boring names beat IMG_1847, screenshot-new and finalvideo2 every time.
When the reply arrives, close the loop
Enter the response date, decision and next owner. Tie an approved return, credit, replacement or further check to a quantity and order. If the request is declined, retain the reason. If one image is missing, write “outer-carton mark required”; do not let the status sit at “pending” for six weeks.
After closure, steal one lesson from the file. Maybe receiving needs a carton-label photograph. Maybe the service form lacks a place for the batch image. Don’t redesign the department around one return. Make the smallest change that would have saved time this morning.
Conclusion
By noon, RB-1105-03 should answer four things without reopening the chat: which unit, which order, what happened and when. That is enough for a supplier to begin a sensible review. It is also enough to stop three messy reports from becoming an unsupported claim about the whole batch.
FAQ
What should the first email contain
Give the case and order references, exact product identity, affected quantity, batch reference, dated event note, attachment list and requested decision.
Is one device photograph sufficient
Usually not. Add the unit box, the relevant carton or batch mark, and a separate close view of the reported condition.
May a retailer open a damaged device
No. Do not open, pierce or repair it. Stop routine handling when a unit is hot, swollen, leaking or damaged, then follow supplier instructions and applicable local rules.
Do three failed units prove a batch defect
No. They support review of those cases. A batch pattern needs matching identity, references, symptoms and dates, plus a meaningful comparison with units received or sold.
Which habit prevents the most confusion
Use the same case number in the log, subject line, filenames and return record. It keeps the product, evidence and decision connected after the original chat is buried.

