Two facilities found one moth.
One had nothing to worry about. The other had an established infestation already underway.
Same insect. Same kind of sighting. Completely different story.
Here’s the strange part: the moth itself couldn’t have told either of them apart. It won’t eat a single thing. Adult Indian meal moths have fully formed mouthparts — they’ve just never once been observed using them to feed, even in a lab. If there’s a population behind it, whatever damage it caused already happened before this thing ever grew wings. The moth is just the last piece to show up.
It’s not a warning. It’s a receipt.
So if the insect looks the same either way — how do you actually tell the two apart? That’s where Sprague’s investigation starts.
What a customer sees. What an investigation finds.
A customer sees one moth and does one of two things: dismisses it, or calls for an immediate treatment. Neither answers the question that actually matters for the business — is this an isolated event, or has something been quietly costing inventory and audit standing for weeks?
The answer isn’t in the moth. It’s in what’s around it.
That’s exactly what separated the two facilities from the start of this piece. Nothing about the moth gave it away — the answer showed up in what was happening nearby.
One of the first things we look for isn’t how many moths — it’s whether there’s any real evidence of breeding at all: larvae, webbing, cast skins. A single moth with nothing else nearby is one thing. Evidence of even one generation means breeding is already underway, and that’s the moment the math changes: product at risk, a longer window an auditor could ask about, more places the actual source could be. Multiple overlapping generations just mean it’s been going on longer.
That distinction is worth getting right before deciding how big a problem this actually is.
Why the sighting location is usually the wrong place to start
The moth itself doesn’t mark the source. Larvae travel only a short distance before settling — which means the real population is almost always closer to storage or receiving than the sighting location suggests, not farther away.
The place you found it usually isn’t the place the problem started.
That’s a meaningful distinction for a QA or operations manager deciding where to spend inspection time. Treating the spot where the moth landed spends effort on the wrong stage of the problem, in the wrong place, while the pallet or receiving area that actually needs attention goes unchecked.
This is why Sprague investigates before it treats
The instinct is to treat the spot where the moth landed. The question isn’t where it landed. It’s what changed — that’s the shift we make at Sprague, and that’s usually where the real story starts.
A new supplier. A pallet that sat two weeks longer than usual. A door propped open in the heat. Food spillage right outside that door, close enough to matter. We’ve learned that most established populations trace back to something that shifted operationally — usually something small enough that nobody flagged it at the time, and not always from inside the building.
More often than not, the answer is already sitting in a nearby monitoring device — not because it caught something unusual, but because the trend across it, and the two or three devices near it, actually got read, instead of checked in isolation. One detail worth knowing: a pheromone trap only catches males. Pair it with a light trap, which catches both, and the picture gets a lot more complete.
One indicator we watch for is a meaningful increase in activity across consecutive services — a jump large enough that it stops looking like normal week-to-week noise. That’s usually where the story changes: from a number to a corrective action.
Treatment depends on what that investigation finds — and so does the cost.
An isolated moth that wandered in calls for a fast, low-cost response: monitor, confirm, close it out. An established population changes the calculus — more inspection time, sometimes pheromone-based intervention, and a longer window to account for in any audit documentation. (More on how that specific method works in a future piece on reading your own monitoring data.)
Either way, the moth is a reason to start asking. It isn’t an instruction for what to spray, and it isn’t a number to write into a corrective action report before you know which scenario you’re actually in.
One moth. One decision worth getting right.
The next time someone spots a single moth and shrugs it off — or panics and calls for immediate treatment — the more useful reaction sits in between: find out which scenario this actually is before deciding what it costs.
Not a beginning. An ending.
And how a team responds to it — investigate or ignore, spray or ask — says more about the quality of a pest management program, and how well it holds up in front of an auditor, than the moth ever will.
Questions to ask your team
- What’s changed nearby recently — a new supplier, a pallet that sat longer than usual, a door left open more than normal?
- If this turned out to be an established population instead of a single wanderer, how much product or audit exposure would that actually represent?
- Are we reading the trend across nearby monitoring devices together, or checking each one in isolation?
- Do we know the difference between an isolated sighting and an established population well enough to make that call ourselves, or would we be guessing?
If those questions uncovered uncertainty
That’s where a facility risk assessment becomes valuable. Our team uses the same investigative approach described above to trace signals back to their source, identify contributing factors, and help prioritize next steps before a small issue becomes a larger one.