Apparel loss prevention: the part of shrinkage that is not theft

01 / FIELD NOTE

Keep the decision tied to the operating context.

Shrinkage in apparel is usually discussed as a security problem, and security is only part of it. The loss a store can see — goods leaving without payment — is the visible fraction. The rest is stock that was mislaid, miscounted, damaged, returned incorrectly, or received in a quantity that never matched the paperwork, and none of that is stopped by an alarm at the door.

That distinction matters because the two problems need different instruments. An alarm answers one question: is a tagged item crossing this boundary without having been deactivated. Inventory visibility answers a family of questions: how many of this style and size are here, where, and does that agree with the record. A store that buys only the alarm has bought the smaller half.

Electronic article surveillance is the incumbent technology and its limitation is what it does not know. A conventional system detects that something is leaving; it does not know which item, what it cost, or which style and size are now short. The store learns of the loss at the next count, without enough information to tell theft from error, which means it cannot act on the cause.

Adding identity to that detection is what changes it. When the item crossing the boundary carries a unique identifier and the security system can read it, the event is not "something left" but "this unit left". That single change connects the security event to the inventory record, and it is the connection rather than the detection that produces usable information.

Direction is the capability that makes a gate usable in a shop rather than merely present. A gate that alarms on any tag in its field will fire on stock being carried in, on goods moving between floors, and on a display near the entrance. A gate that resolves which way an item crossed, and whether its identity has been through a checkout, distinguishes a genuine removal from the ordinary traffic a busy store generates. Without direction, false alerts teach staff to ignore the system.

Where the tag sits in the garment decides how much of this works. An inlay built into a hangtag or a care label is applied by the supplier and survives to the shop floor, which makes it usable for receiving, counting and security at once. A tag added in store is a lower-cost start and only covers the part of the item’s life the store controls. Both are legitimate; they answer different spans.

The moment the tag stops mattering is checkout, and how that is handled decides whether the same tag can serve both purposes. A tag deactivated at the till removes the alarm for that item and, if the sale is posted against the same identity, also removes it from available stock in the same transaction. That is the point where loss prevention and inventory accuracy stop being separate projects.

Returns are the flow most stores handle worst. A returned garment is physically present and commercially unavailable, and both facts need recording. Without identity, a return is either put back without adjustment, which inflates availability, or removed from the record and set aside, which loses track of it. With identity, the original sale can be found and the item given a disposition — back to the floor, to a markdown rail, or out of stock.

What counts as a loss has to be defined before the system is asked to report one. A garment that is on the wrong rail is not shrink, it is misplacement. A garment received in a short quantity is a supplier discrepancy. A garment that left without payment is shrink. A count that lumps all three into one variance figure cannot be acted on, because the response to each is different — and two of the three are fixed in the back room rather than at the door.

Frequency changes what can be found. A store that counts a category weekly sees a discrepancy while the events that caused it are still recent enough to identify. A store that counts twice a year sees an accumulated figure with no traceable cause, and the only available response is to write it off. Bulk reading is what makes the weekly count take minutes rather than a day, which is what makes it happen at all.

There is a limit worth stating: a tag is not a theft prevention device by itself, and no amount of visibility stops a determined removal. What visibility does is make the ordinary, larger, more tractable losses visible — the misplacements, the receiving errors, the unrecorded returns — and give the store a record specific enough to act on. That is a smaller promise than security marketing usually makes, and a more useful one.