A customer says a bag of treats smells different. Another reports a broken seal, unusual texture, or a pet that became unwell after eating a product. A refund may help the customer, but it does not answer the operational question: **which exact product and batch are you investigating?**
Pet product batch traceability turns a vague report into a defined review. Preserve the facts, identify the likely finished lot, connect it to production and material records, and document the scope and next steps.
This is an operational guide, not veterinary, legal, recall, or regulatory advice. Safety concerns should follow your approved procedures and receive qualified support. The FDA’s guidance on [reporting a pet food complaint](https://www.fda.gov/animal-veterinary/report-problem/how-report-pet-food-complaint) shows why product identity, lot information, purchase details, use, symptoms, and supporting evidence matter.
Start the customer complaint investigation with facts
Collect information without diagnosing the problem or suggesting a cause. Record the customer’s words, then separate the reported observation from your later analysis.
Capture:
- customer name and preferred contact method;
- product name, flavor or variety, size, and package type;
- lot or batch code, best-by date, and where each appears on the package;
- purchase date, seller, order number, and shipping date when available;
- when the package was opened and how it was stored;
- what the customer noticed and when;
- photographs of the product, package, seal, and printed codes;
- how much product remains and whether it can be retained; and
- any animal or human illness, injury, or safety concern requiring immediate escalation.
Do not rewrite “the treats seemed oily” as “excess fat caused spoilage.” The first is an observation; the second is an unverified conclusion.
Build an order-to-unit bridge when the code is missing
Customers may discard a pouch or find a code difficult to read. A missing code slows lot tracking, but it does not always stop it.
Use the SKU, sale date, fulfillment location, inventory movement, and shipment date to identify which finished lots could have supplied the order. If two lots were picked during that period, keep both in scope until another fact distinguishes them.
Ask for a clear photo rather than a guess. Similar characters—0 and O, 1 and I, or 5 and S—can point to the wrong batch. Keep the original image and note who interpreted the code.
If one lot cannot be confirmed, document the candidates and why each remains possible. Keep “unknown lot” visible rather than choosing the most convenient record.
Trace the finished lot backward through production
Once the finished lot is identified, open the connected production record. A useful backward trace should answer six questions.
1. What approved product version was made?
Confirm the recipe version, work instructions, package configuration, label version, and effective dates. If a recipe changed recently, compare the complaint lot with lots made under each version. The guide to [updating pet treat safety records before a recipe change](https://resources.buildwithkerno.com/changing-a-pet-treat-recipe-update-these-safety-records-before-the-next-batch/) explains the pre-batch controls that make this possible.
2. Which material and packaging lots were used?
Connect the finished lot to ingredient or component lots, supplier records, and relevant packaging. Record actual usage rather than assuming the oldest received lot was used.
3. What actually happened during the run?
Review actual quantities, defined process observations, yield, operator entries, equipment, cleaning records, and notes. Flag missing or unusual values without treating every difference as the cause.
4. What quality checks and exceptions were recorded?
Review in-process and finished-product checks, packaging or seal checks, deviations, rework, holds, and the release decision. A completed record does not automatically mean every result was normal.
5. Where did the finished quantity go?
Reconcile produced, rejected, sampled, destroyed, and released quantities. Connect released units to storage, orders, wholesale shipments, or marketplaces.
6. Is a retained sample available?
When your approved program uses retained samples, identify the correct sample and preserve its chain of handling. Do not open, test, or dispose of it casually once an investigation begins.
Clear [pet product ingredient, packaging, and safety records](https://resources.buildwithkerno.com/how-pet-treat-and-grooming-brands-can-keep-ingredients-packaging-and-safety-notes-organized/) make this review faster. Good pet product records still need a named owner.
Trace relevant lots forward to define the scope
Backward traceability explains what went into the complaint lot. Forward traceability asks where else those inputs went.
If an ingredient lot, packaging lot, label version, or process exception appears relevant, identify every finished batch that shared it and where those units are now: on hand, held, shipped, sold, or consumed.
This does not mean every shared lot is affected. Compare same-lot complaints, reports from other lots, retained samples, production results, supplier notices, and inventory status before changing the scope.
One complaint can be important, while similar complaints can have different causes. Use [production records and batch consistency checks](https://resources.buildwithkerno.com/achieving-batch-consistency-with-production-records/) to compare evidence instead of relying on the most plausible story.
Record containment and communication separately
An investigation record should show both what the business learned and what it did while learning.
Containment may include holding inventory, pausing fulfillment, preserving evidence, restricting a material lot, contacting a supplier, or escalating for qualified support. The right action depends on the product, complaint, evidence, and applicable requirements.
Record what was promised, who will follow up, whether a refund or replacement was issued, and when the customer received an update. Service recovery can finish while the investigation remains open.
Close the complaint only when the record states the affected scope, evidence, conclusion or limitation, actions, owner, approval, and closure date. “Handled” is not a useful disposition.
A reusable complaint-to-batch template
For the next complaint, use this five-part complaint-to-batch workflow:
1. **Intake:** exact report, product, package, lot code, purchase, storage, photos, remaining product, and escalation flags. 2. **Identification:** confirmed finished lot or documented candidate lots, plus the evidence used. 3. **Backward trace:** formula version, production record, material and packaging lots, quality checks, exceptions, release, and distribution. 4. **Forward trace and scope:** other finished lots sharing a relevant input or condition, current locations, related reports, and containment status. 5. **Decision and closure:** findings, limitations, customer communication, corrective actions, approvals, dates, and follow-up review.
Test the template now: choose one recent order, trace its finished lot back to materials, then trace one material lot forward to every finished batch that used it.
Frequently asked questions
What if the customer cannot find the lot code?
Use the SKU, order number, purchase date, seller, shipment history, and inventory records to identify candidate lots. Keep uncertainty visible until evidence supports one lot.
Should every customer complaint trigger a recall?
No automatic answer fits every complaint. Follow approved escalation procedures and obtain qualified safety, legal, veterinary, quality, and regulatory guidance for the specific facts.
How long should a complaint investigation stay open?
Set an owner, priority, next action, and review date. Keep it open until required evidence, decisions, communications, and approvals are complete or an unresolved limitation is formally documented.
What if only one package appears affected?
Preserve the package evidence and review the connected lot before assuming the issue is isolated. Compare packaging, distribution, retained samples, and other reports.
Should customer service decide which batch caused the problem?
Customer service should capture accurate facts and escalate them. A named investigation owner should confirm product identity, scope, evidence, and disposition under the business’s procedures.
Practical takeaway
Choose one recent customer question. Can you identify its lot, retrieve the production record, trace backward to materials, trace forward to other finished lots, and show the decision without asking the founder to reconstruct it?
Fix the first broken connection before the next order ships. A usable record shows whether the business can find the right batch, contain uncertainty, and learn from its evidence.
