Most private label brands only think about complaint handling after the first complaint arrives, and by then the packaging that would have helped is often already in a customer's bin. A working process, agreed before anything goes wrong, turns a stressful one-off email into a routine step both sides know how to run. For tea bags and dried fruit specifically, the process is straightforward once you know what a co-packer actually needs to investigate.
The first hour after you spot a problem
Once a defect is reported, whether from a shopper, a retail buyer or your own warehouse check, the instinct to fix it fast is right, but the first move should be to preserve evidence, not discard it. Set the affected unit aside rather than throwing it out, and if the report came from a customer, ask them to hold and photograph the pack before anything happens to it. If the issue affects an identifiable batch still in your own stock, isolate that stock so it does not keep shipping while you investigate. None of this takes long, and it is the difference between a claim your co-packer can act on and one they can only take your word for.
Batch and lot codes: the anchor for every claim
Every claim you raise is only as useful as the batch or lot code attached to it. A co-packer running production under a documented quality system keeps records tied to that code and, in many cases, a retained sample from the same run, so a code turns a vague "something was wrong with a bag I bought" into "batch X, run on this date, against this specification." Without it, the packer must search across every batch that could plausibly match, which is slower and far less conclusive. The code is usually printed on the outer envelope, the retail carton or the tag, so ask whoever found the fault to note exactly where they saw it before the packaging is lost.
Photographs that actually help a packer investigate
Not every photo is equally useful. A close-up of the defect matters, but so does a wider shot showing the sealed bag or box intact, plus a clear image of the printed batch code and date. Where relevant, a photo of the unopened outer packaging next to the opened product helps rule out mishandling after purchase versus a fault introduced during packing. Avoid photos cropped so tightly the packaging context disappears, and never edit or enhance an image before sending it — an unaltered photo, even an imperfect one, carries more weight than a retouched one.
Writing the complaint report
A short written report travels faster and gets acted on sooner than a phone call or a message thread pieced together later. It should state the batch or lot code, the product name or SKU, the approximate quantity affected, the date the product was purchased or received, a plain description of what was wrong, and the photos described above. If you know what resolution you want, whether that is a replacement, a credit or simply an explanation, say so directly rather than leaving the packer to guess. Keep a copy of every report you send; over time it becomes your own supplier quality file.
What a responsible co-packer does with a complaint
On receiving a well-documented complaint, a packer working under a quality management system pulls the retained sample tied to that batch and compares it against your report, alongside the incoming material, in-process and finished-goods records from that run. This is where a packer's own checkpoints — incoming inspection, in-process moisture and weight checks, finished-bag inspection — either confirm or rule out where in the run a fault could have entered. A packer that cannot produce these records for a specific batch is not really investigating; they are guessing, and that distinction is worth testing before you commit volume to a supplier.
Escalation when the first response falls short
If an initial reply does not resolve the issue, or the same defect shows up again in a later batch, escalate in writing rather than repeating the same message informally. Ask for the outcome of the investigation, not just an apology: what the packer found in the retained sample and records, and what corrective action, if any, follows for future runs. A supplier relationship worth keeping is one where this question gets a straight answer, even an unwelcome one, rather than a deflection.
Feeding complaints back into your own quality file
A single complaint is a data point; a pattern across several is a signal. Log every complaint with its batch code, date and resolution, and review that log periodically instead of reacting to each report in isolation. This log is also what you would hand to a retail buyer or auditor asking how you manage supplier quality as a private label brand, so it earns its keep well beyond the issue it was opened to solve. TeraVella keeps retained samples and batch records for the tea bag and dried fruit runs it packs, including private label orders, as part of the process a complaint investigation relies on.
