Grey-Market Control Genuine products. Wrong market.

The grey market is the trade in genuine, manufacturer-made products through channels or in countries the manufacturer did not intend - for example units allocated to one national distributor that are resold in another country. The goods are real, the packaging is real and the warranty is real; only the route is unauthorised. That is what separates grey-market trade from counterfeiting, where the product itself is fake. Inside the European Economic Area the resale of goods you placed on the market is generally lawful under the exhaustion principle in Article 15(1) of the EU Trade Mark Regulation, which is why grey-market trade is usually a commercial and contractual problem rather than a straightforward trade mark case. The damage is still real: undercut pricing, distributors who lose sales they were promised, service costs you never budgeted for, and sales data that no longer shows where your products actually end up.

Because they are genuine. A verification check answers one question - is this the original item that was produced and marked, or a copy - and a diverted unit passes it, correctly. What identifies a grey-market product is not a failed check but a passed check in the wrong place: the combination of a confirmed original and a scan location outside the market that unit was allocated to. authentic.network links each serial number to its intended market when the code is produced, so both facts are available at the moment of the scan. This is also why anti-counterfeiting alone does not surface diversion. A system that only reports pass or fail will never flag a diverted unit, because on the only question it asks, the answer is yes.

Each serialised code carries the market the unit was allocated to, alongside its article, batch and production date. Every verification scan records where and when it happened. When a genuine unit is scanned outside its intended market, that mismatch is raised as a grey-market case in the dashboard, with the article and batch attached. Nothing has to be scanned at every handover along the supply chain and no logistics system has to be connected for this to work - the signal comes from checks that inspectors, retailers and customers make in the field anyway. At one global lubricant brand using authentic.network, grey-market activity accounted for around 8% of revenue. Detection depends on the code being the original: a reprinted code fails the check first, so a copy cannot be used to impersonate a legitimately allocated unit.

No. Mapping intended routes through a distribution network is a large project and it tells you what is supposed to happen, not what does. It is enough to link each serial number to the market it was allocated to, which happens once, when the codes are produced. The scans then show where products actually surface. This is the practical difference between grey-market control built on verification scans and a full track-and-trace rollout: you are not asking every partner in the chain to adopt a new process before the first result arrives. If you later want event data at each handover, that is a separate project - but it is not a precondition for seeing diversion.

Yes. Serial numbers can be linked to article number, batch and production date as well as intended market, so every grey-market case names the specific products it concerns rather than reporting that something, somewhere, is off. That matters for two reasons. Internally, article and batch narrow a leak down to a production run and an allocation, which usually points at where in your own channels it started. Externally, it is what turns a suspicion into a conversation a distributor can answer: not “your goods seem to be appearing in the wrong market” but “these units, from this batch, allocated to this market, were checked there on these dates.”

No integration is required to start. Grey-market cases are produced by comparing verification scans in the field with the intended market linked to each serial, and both of those live in the authentic.network system. There is no ERP or warehouse-management connection needed before the first cases appear. Integration becomes useful later rather than first: at LIQUI MOLY the solution runs inside the existing system landscape, connected to ERP, track and trace, grey-market control and digital services, so cases reach the teams in the tools they already use. That is an option once the programme is running, not a prerequisite for seeing whether you have a diversion problem at all.

Usually not, in itself. Article 15(1) of the EU Trade Mark Regulation sets out the exhaustion principle: once goods have been put on the market in the European Economic Area by the proprietor or with their consent, the trade mark no longer entitles the proprietor to stop them being resold there. So a genuine unit diverted within the EEA is normally a contractual and commercial problem rather than a trade mark infringement. Article 15(2) preserves the proprietor's rights where there are legitimate reasons to oppose further sale, in particular where the condition of the goods has been changed or impaired - the ground that covers repackaging, relabelling and removed identifiers. Goods first placed on the market outside the EEA are not exhausted at all, so importing them into the EEA without consent can be opposed. Note also that the burden of proof is not always the reseller's: in a dispute over a selective distribution network, the Court of Justice has held that it can fall to the trade mark proprietor to show where the goods were first placed on the market (C-367/21). Each of these turns on evidence about one specific unit.

A case names the intended market, the article and the batch, which is usually enough to point at where inside your own channels the leak started - diversion more often begins with an allocation than with an outside actor. Because cases appear with the first scans outside the intended market rather than at the end of a sales period, you can act while the route is still open instead of writing a post-mortem. The same detail changes the conversation with a distributor: not “your goods seem to be appearing in the wrong market” but “these units, from this batch, allocated to this market, were checked there on these dates” - a fact a partner can answer rather than an accusation they can deflect. Cases accumulating over time distinguish a one-off shipment from a route that keeps repeating, and after you act, the following weeks of scans show whether it actually closed.

As soon as units are checked outside the market they were allocated to. Because the signal comes from verification scans rather than from sales reporting, a case can appear while the goods are still moving, not after a reporting period closes and the numbers are reconciled. In practice this changes what you can do about it. A leak identified at the end of a quarter is a post-mortem; the same leak visible in its first weeks is still a route you can close. Cases accumulating over time also distinguish a one-off shipment that went astray from a channel that keeps reappearing - and after you act, the following weeks of scans show whether the route actually closed.