The Same SKU, Lost and Found, Three Cycles Running

Introduction

Numbers in isolation are easy to dismiss as one-off noise. What is harder to dismiss is the same item, at the same territory, going through the same cycle three years in a row, through three different workflows, for the same underlying reason. Here is what that looks like when nothing structural changes between audits.

Year One: Complete, Except It Wasn't

A loaner kit returns from a case during a busy week. The return queue is backed up. Someone marks it complete so it can ship again for an upcoming case. Nobody compares the tray against its bill of materials. Two items that should be there are not, either used during the case and never logged, or misplaced during turnover.

The kit ships again, complete on paper. Weeks later, a routine shelf check at the original territory shows those two items missing against par level. Supply chain ships a replacement to close the gap. Nobody investigates further, because from where they sit, this looks like a normal replenishment.

At the annual field audit, the auditor cannot locate the original two items at their system location. They get written off, correctly, given what anyone in the company knew at the time.

What nobody connects yet: the territory's replenishment record now includes a shipment that, in hindsight, should never have been necessary, and the territory's reported position is already slightly overstated because of it.

Year Two: Found, Reversed, Not Investigated

During the next annual audit, the two items turn up, sitting inside a different kit entirely, where they ended up during the turnover confusion the year before, never logged as having moved. The write-off gets reversed. On the accuracy report, this reads as a good outcome: inventory that looked lost was actually fine.

What does not happen is any investigation into why a return marked complete let two items go unverified, or any check on whether the replacement shipped in year one is now sitting as excess somewhere in the territory.

Two smaller things also happen in year two that nobody connects to the first event. A rep in that territory submits a legitimate replenishment request and gets questioned on it, because the numbers already show the territory carrying more than expected. And separately, during the same audit, several items turn up that do not match any known location, so they get assigned to the catch-all holding location that was created a few years earlier as a temporary measure. Nobody reconciles that location. It is now larger than it was last year.

Year Three: Two Variances, Only One of Them Real

Nothing in the return workflow changed. This time the trigger is a rep-to-rep transfer, one rep covering a case for another, handled by phone call. The location eventually updates when someone notices the product has moved. The consignment ownership and billing assignment do not. For one full quarter, commission and territory revenue for both reps are calculated against a custody record that was already wrong.

The year three audit flags two variances on this product line. One is that transfer, a real discrepancy with a real financial consequence. The other is a tray configuration that product management modified eighteen months earlier without the change ever propagating to the bill of materials in the system, so the audit is comparing physical reality against an expectation that stopped being accurate a year and a half ago.

Both variances look identical in the audit report. Both trigger investigation. Two days of labor goes into the second one before someone recalls the configuration change and confirms the inventory was correct the whole time. Nothing in the system distinguished a real loss from a stale record, so both got the same treatment.

What This Pattern Actually Shows

A single instance of any of these looks like ordinary audit noise. Three cycles running on the same SKU, through an unverified return, an undocumented transfer, and a stale configuration, is not noise. It is a signal that the gap is structural rather than incidental.

It also shows why an annual audit cannot be the control. By the time the audit runs, the phantom order has shipped, the commission has been mis-attributed, the holding location has grown, and the investigation labor has already been spent. The audit is measuring the accumulated result of a year of unenforced movement, and then resetting the clock to do it again.

This scenario is illustrative, built from patterns common across field inventory operations. It does not describe a specific company or customer.