A mislabeled supplement batch met an insurance deadline at the worst time

The situation

Every quarter, without exception, a sample from each production run at the Etobicoke facility went out for independent lab testing before the batch was cleared for distribution. Yaa, a pharmacist, had insisted on the practice from the company's earliest days making joint supplements for dogs and cats, well before that kind of testing was something distributors expected as standard. Emeka, a veterinarian, reviewed every formulation change personally. Mykola ran operations and had built the quarterly test into the production calendar so firmly that nobody on the floor thought of it as optional. It was simply what the company did, the way it had grown from a two-person side project into a manufacturer doing somewhere between five and twenty million dollars a year in revenue, sold through veterinary clinics and a handful of specialty retailers.

The plan, that quarter, was unremarkable. A new production run of a joint supplement for larger dog breeds had gone out for testing on schedule, the same as every run before it, while the company moved ahead with the rest of its calendar: renewing its general liability and product liability insurance, due within the month, and finalizing terms on a new distribution agreement with a national pet supply retailer that had been under negotiation for weeks. Both were routine pieces of a growing business. Neither was expected to collide with anything else.

The test results came back with a problem. One ingredient, a joint-supporting compound dosed by animal weight range, was measured at a concentration meaningfully above what the label specified for that batch, the result of a calibration error on one piece of production equipment that had gone unnoticed through the run. It was not an extreme deviation, and nothing in the data suggested acute danger at typical dosing, but it was well outside the tolerance the company held itself to, and outside what the label promised.

The batch had not yet shipped to customers. It was sitting in the company's own warehouse, cleared for release but not yet released, when the test result landed on Mykola's desk three days before the insurance renewal deadline and five days before the distribution agreement was set to be signed.

None of the three owners had ever dealt with a situation quite like this one. They had handled minor formulation tweaks and the occasional supplier substitution before, always through their existing quality process, but nothing that raised the question of whether customers, clinics, or regulators needed to be told something before it became a bigger problem than it already was.

The legal problem

The first question was straightforward in principle and harder in practice: what does a manufacturer owe the market when it finds a problem with its own product before that product has caused any harm, and before most of it has even left the building? A company that discovers a defect has obligations that scale with the risk, from a quiet internal correction for something trivial up to formal notification and a public recall for something that could hurt a customer or their animal. Getting the scale wrong in either direction creates its own exposure, either by overreacting to a minor calibration slip in a way that damages trust and relationships with retailers unnecessarily, or by underreacting to something that later turns out to matter.

The second problem was where the real complexity sat. The company's product liability insurance was up for renewal within days, and most policies of this kind require the policyholder to disclose known or suspected issues that could give rise to a claim before renewing, not after. Renewing the policy without disclosing the batch issue risked the insurer later denying coverage on the basis that a known problem had been withheld at the time of renewal. But disclosing a recall in progress, right at renewal, also risked the insurer treating the file differently, adjusting terms, or asking questions that would take time the company did not have before the policy lapsed.

Layered on top of that was the pending distribution agreement, which included an audit clause giving the new retailer the right to review quality records for any batch shipped under the agreement, including the right to walk away from the deal if a material quality issue surfaced during the review period. The batch in question had not shipped and would not ship under the new agreement, since it predated the contract, but the retailer's due diligence team was actively reviewing the company's quality systems that same week as part of finalizing terms, and a recall discovered independently, rather than disclosed proactively, would have looked very different to a party deciding whether to trust the company with a national rollout.

Two separate legal problems, an insurance disclosure obligation and a due-diligence-sensitive contract negotiation, were running on their own clocks and intersecting in the same narrow window as the batch issue itself.

The order in which these three things were handled mattered as much as the substance of any one of them. Disclosing to the insurer before understanding the true scope of the batch issue risked overstating the exposure and triggering a heavier underwriting response than the facts warranted. Waiting too long to disclose risked the opposite problem. Getting the sequence right, confirm the facts, contain the batch, then disclose, needed to happen inside a window measured in days, not weeks.

What we did

1. Assessed the severity of the batch issue against the actual test data, working with Emeka to confirm what the concentration deviation meant for animal safety at typical dosing, rather than assuming the worst or the best. This grounded every decision that followed in an honest read of the risk instead of a guess, and confirmed the batch warranted a proactive recall even though the deviation was moderate.
2. Held the batch and confirmed nothing had shipped, cross-checking shipping and inventory records against the specific batch code to verify the affected run remained entirely in the company's own warehouse, with no partial shipments to clinics or retailers. Confirming this early meant the recall could be executed as a contained internal correction rather than a public consumer notice, significantly narrowing what needed to be disclosed, to whom, and how urgently the rest of the file needed to move.
3. Drafted a recall and remedy plan before contacting the insurer, documenting the root cause, the corrective action taken on the miscalibrated equipment, and the planned disposition of the affected batch in a single written summary. Sequencing it this way mattered: disclosure with an open question invites an insurer to assume the worst and dig, while disclosure with a complete, credible account invites a straightforward renewal. The plan became the document the insurer, and later the retailer, actually relied on.
4. Disclosed the issue to the insurer ahead of the renewal deadline, on the basis that failing to disclose a known issue at renewal created a far larger risk than the disclosure itself, since an insurer that later discovered a withheld batch problem could deny coverage entirely on a much larger future claim. The renewal proceeded with the disclosure on file, preserving coverage without a gap.
5. Coordinated timing with the distribution negotiation separately, advising the company to proactively inform the retailer's due diligence contact that an unrelated batch had been caught and corrected through the company's own testing process, framed accurately as evidence the quality system worked rather than as a defect to bury. This shaped how the retailer's team read the recall when it came up in their own review, rather than letting them discover it unexplained.
6. Set up a written corrective action record tying the equipment fix, the batch disposition, and the insurer disclosure together in one file, with dates attached to each step rather than a general narrative written after the fact. That mattered because if either the insurer or the new retailer asked questions months later, the company needed a record it could hand over immediately, showing exactly what happened and when, rather than having to reconstruct memory-dependent details under pressure.
7. Traced the calibration error to its root cause on the production line, confirming with Mykola and the plant supervisor exactly which piece of equipment had drifted out of tolerance and why the standard pre-run check had not caught it, since a recall plan that does not fix the underlying cause only delays the next incident rather than preventing it.
8. Briefed all three owners together before any external communication went out, walking Yaa, Emeka and Mykola through the same facts, the same plan, and a clear division of who would speak to which counterparty, rather than letting each owner explain the situation in their own words. With three owners each capable of fielding a call from the insurer or the retailer, a shared script mattered; the risk of the insurer or the retailer hearing two different versions of the same story was real and avoidable.

The outcome

No affected product reached a customer, a clinic, or an animal. The recall, such as it was, amounted to relabeling and reworking one held batch before it ever left the warehouse, a cost the company absorbed internally without any public notice being required. This is what prevention looks like in practice: the expensive, reputational version of this story, involving a shipped batch, an adverse event report, and a public recall notice, never happened, because the quarterly testing habit Yaa had insisted on years earlier caught the problem at the one point in the process where catching it cost the least.

The insurance renewal went through without a coverage gap, and the disclosure became part of the policy file rather than a fact the company was sitting on. The distribution agreement with the national retailer closed on schedule as well, with the due diligence team's questions about the recalled batch answered before they were asked, which the company later heard had counted in its favour rather than against it during the retailer's internal review.

The episode cost the company the value of the reworked batch and some staff time diverted to documentation during an already busy week, both modest against the size of the business. It did not cost a customer relationship, an insurance dispute, or the new distribution deal, any one of which would have been a materially worse outcome. The corrective action record built during the file is still in place as the company's template for handling the next quality flag, whenever it comes.

Yaa has since credited the outcome less to any single decision and more to the fact that the company had a testing habit rigid enough to catch a problem this small before anyone outside the building ever saw it. Emeka's read is similar: the file worked because the three owners treated the recall, the insurer, and the retailer as one connected problem from the first day rather than three separate fires to put out in whatever order was most convenient.

What you can learn from this