Channel diversion is when a brand's own, genuine product ends up on sale outside the region, distributor or sales channel it was shipped to. It goes by several names in the field: out-of-territory sales, parallel trade, grey market goods or simply diversion. What these have in common is that the product is not fake; it is just not where it is supposed to be. That is why a verification check returns "genuine". Diversion only shows up when you compare where a product was sent with where it was seen.
What forms does channel diversion take?
The same problem appears in different forms. Telling them apart matters, because each one points to a different record and a different conversation.
| Form | What happens | Typical trace in the record |
|---|---|---|
| Out-of-territory sales | A distributor or dealer sells outside its assigned territory | Codes from a batch shipped to one region are scanned in a neighbouring one |
| Parallel trade | Product shipped to one country or market is resold in another | Codes from an export batch are scanned in the home market |
| Grey market | Product appears with a seller outside the authorised network | A scan at a point that is not on the authorised retailer list |
| Channel leakage | Product reserved for a professional channel, an institution or a tender reaches retail | Codes from a salon, hospital or tender shipment are scanned on a store shelf |
"Grey market" is often used for all of these. In this guide channel diversion is the umbrella term; how to set a regional threshold for grey market scans is covered in our grey market post.
Why does channel diversion matter?
Diversion usually starts with a price gap. When product supplied to one market or channel on certain terms is sold where prices are higher, the difference is the diverter's margin. Three parties pay for it:
- The authorised distributor competes with the brand's own product in its own territory and loses confidence in the brand and its territory plan.
- The brand cannot hold its regional pricing or its channel plan, and loses sight of what each channel really sells.
- The consumer may buy a product whose storage conditions are unknown, whose warranty or service terms differ, or whose label was prepared for another market.
There is a measurement cost too. Diverted product shows up in sales reports as the wrong region's sales, so campaign, stock and demand planning rest on the wrong data.
How do you detect channel diversion?
Detection rests on putting two records side by side: where the product was shipped and where it was seen. The steps are:
- Give each product, or each batch, its own code. A barcode (GTIN) is the same on every product of the same type and says nothing about the shipment it came from. To track diversion, the code has to be distinctive at least at batch level, and preferably at product level.
- Activate the code at the end of the line. A code that is not read at line exit never appears in the record as "produced", and every later finding has nothing to stand on.
- Record the shipment when it happens. Which code, in which case and pallet, went to which distributor and which region? The target market in the production plan is not enough. Diversion begins exactly where the plan and the actual shipment part ways.
- Collect scans along the chain. Distributor and dealer receipts, field team store visits and consumer scans show where the product was seen. If scanning is part of the handover itself, the record does not thin out over time.
- Compare scan location with the shipping record. Each scan is matched against the region and channel its code was shipped to. Scans that do not match go to a separate list.
- Separate one-off events from patterns. A single scan can be a trip, a gift or a house move. What matters is many codes from the same batch being scanned in a region or channel they were never shipped to. Set the threshold separately for each region.
- Trace the finding back to its source. The record shows which batch, which pallet and which distributor delivery the diverted codes came from. A vague "our product is out there" complaint becomes a specific question about one delivery.
What data do you need?
The minimum data set is small. Three records per code are enough:
- Production record: which batch, which line, which date.
- Shipping record: which recipient, which region, which channel, which date.
- Scan record: where, when and by whom.
Linking products to cases and pallets means a single pallet scan in the field can record everything inside it. If records need to be shared between companies with the same fields, GS1's EPCIS standard describes events such as shipping and receiving in a common format; we summarised it in our EPCIS 2.0 post. Choosing scan points is the subject of our post on setting up a product tracking system.
How do diversion and counterfeits differ in the record?
Both can appear as an alert on the same screen, but they leave different traces:
- With diversion, each code is scanned once or a few times, but most of the codes are in the wrong region. They were activated at line exit and left on a real shipment.
- With a copied code, the same code is scanned again and again in different places by different people, or a code that was never activated at line exit turns up in the field.
The distinction shapes the response. Diversion is a distribution and contract matter; a copied code is a counterfeiting concern. The traces a copy leaves in the record are covered in detail in our serial number verification post.
What happens once diversion is detected?
The record is the basis for a decision, not the decision itself. A finding usually goes first to the sales and channel team: how many codes from which batch were scanned in which region, which distributor the shipment went to and when the diversion started. The conversation with the distributor starts from that concrete picture.
If the distribution agreement has a territory or channel clause, the record supports enforcing it. Whether a particular sale is unlawful is a separate assessment under the agreement and the applicable law, and that assessment belongs to the brand's legal team.
If diversion continues, the record also guides operational measures. Product going to a particular distributor can be scanned more often, batches bound for a high-risk region can move to product-level codes, and field visits can shift to the region where diversion shows up.
How does Tagvex make channel diversion visible?
Tagvex is a traceability system that gives each product, or each batch, its own copy-resistant code, tracks the distribution path and makes channel diversion visible. Product level is the default; starting at batch level and moving to product level later is also possible. The code is read and recorded at line exit. Handovers at warehouse, distributor and dealer points are gathered in the same record, and when a product is scanned with the mobile app, that scan is added too. Codes scanned outside the region they were shipped to, or in an unexpected place, are flagged, and channel diversion is reported periodically. Records can be connected to ERP and warehouse systems through an API. See the solutions page for the full scope.
Frequently asked questions
Is channel diversion the same as the grey market?
The terms are often used interchangeably. Channel diversion is the broader one: out-of-territory sales, parallel trade, product found with unauthorised sellers and product leaking from professional channels into retail all fall under it. "Grey market" usually describes sales outside the authorised network.
Do you need product-level codes to see diversion?
No. A batch-level code can show that a batch was scanned in the wrong region. Product level narrows it down to the case and the delivery it came from, and the same record also separates copied codes. We explain the difference in our post on unique unit codes versus batch codes.
Can you see diversion without consumer scans?
Yes, but less often. Distributor and dealer receipts and field team store visits also produce scan records. Consumer scans show where the product is close to its point of sale, so they make the record denser.
Does a single out-of-region scan count as diversion?
No. A single scan can be explained by travel, a gift or a move. What counts is a repeating pattern of several codes from the same batch in a region or channel they were never shipped to. Thresholds are set per region, and any change is recorded with its reason.
