Grey market leakage: finding out where your stock really goes
Product sold cheap in the wrong city, returns reappearing as new, allocations quietly resold. Unit level codes turn all three from suspicions into records.
Founder·23 August 2026·6 min read
Most brand owners can describe the symptom precisely. Your product turns up in a market at a price you never authorised. A wholesaler in another city has stock you did not sell them. Goods that were returned and written off are somehow back on a shelf.
Everyone in the chain has an explanation and none of them can be checked, because the only identity your product carries is a batch number shared by thousands of units.
The problem is identity, not honesty
When ten thousand units share one printed batch number, nothing can be traced to a consignment, a distributor or a date. Every dispute becomes a matter of who is more convincing, and the party with the paperwork usually wins regardless of what happened.
Give each unit its own identity and the argument changes character. You are no longer alleging, you are showing.
Three signals worth watching
- Geographic mismatch. Codes from a consignment shipped to one region being verified consistently somewhere else.
- Repeat scans of a single code. Either a cloned label or one code photographed and shared, both of which you want to know about.
- Dead consignments. A batch that ships and never produces a single scan, while comparable batches scan normally, which often means the stock did not reach the retail channel you think it did.
Returns are the quiet leak
Returned and expired goods are supposed to be destroyed, and are often the easiest stock in the system to divert, because it is already written off and nobody expects to see it again.
With unit level codes you can retire the specific codes that came back. If a retired code is later scanned by a customer, you know the unit re-entered the market, when, and which return it came from. That single control tends to pay for the whole system.
Having the conversation
Evidence changes the tone of a distributor conversation but it does not have to end the relationship. In most cases the leak is one person or one sub-dealer, not the partner as a whole, and a factual conversation gives them a chance to fix it themselves.
Go in with the specifics: these codes, from this consignment, verified in this market, on these dates. Ask what happened rather than announcing what you have concluded. Partners who are clean will help you find the leak; partners who are not will change their behaviour once they know units are traceable.
Set it up so the data is usable later
BrandProtection handles the identity and the record: unique codes per unit, batches tied to real products, scan analytics and CSV export you can take into a meeting.
- Name batches after the consignment and destination, not just a date, so the mapping survives staff changes.
- Record which batch went to which distributor at the time of despatch, not from memory afterwards.
- Export the scan record periodically so you have a snapshot independent of the live system.
- Decide in advance what threshold triggers a conversation, so decisions are not made in the heat of one complaint.
Channel discipline is mostly a visibility problem wearing a trust costume. Once every unit can be identified and every scan is recorded, most of the leakage stops on its own, because the people causing it work out that it is now visible.
Frequently asked questions
How do verification codes reveal grey market activity?
Because each code belongs to a batch, and each batch was shipped somewhere specific. When codes from a consignment allocated to one region are consistently scanned in another, that is diversion showing itself in data rather than rumour. The same mechanism catches returns that were supposed to be destroyed and are being resold.
What if scans are too few to draw conclusions?
Then use the batch level signal rather than the individual one. Even a low scan rate is a sample, and a sample skewed heavily to a market you never shipped to is meaningful. Scan rates also rise when the label prompt is prominent and there is a reason for the customer to check, so treat low scanning as a label design problem first.
Should distributors know units are individually coded?
Yes, and tell them early and positively. Framed as protection against fakes and against being blamed for someone else's leakage, it is welcomed by good partners. Discovered later and used only as an accusation, it damages relationships you need. The deterrent value comes from everyone knowing the units are identifiable.