You find your product on a marketplace you never approved, at a price you never set, sold by a company you've never heard of. The product is real. The packaging is real. And that is exactly what makes it so hard to deal with.

This is the gray market, and for a lot of growing US brands it does more quiet damage than counterfeiting does. Counterfeits are an enforcement problem with a clear villain. Gray market goods are a channel problem, and the culprit is usually someone you have a contract with. Below is a practical guide to understanding where the leak comes from and how to close it — written for founders and operators, not lawyers.

What the gray market actually is

Gray market sellers buy authentic products through legitimate channels — an authorized distributor, a liquidator, an overseas wholesaler, a retailer clearing out stock — and then resell those goods outside the route you intended. Nothing is fake. The goods are simply diverted.

Most diversion is driven by arbitrage. You price differently by region, offer volume rebates, or run a promotional buy-in, and someone realizes they can buy at your best price in one market and resell at a profit in another. Add global e-commerce, and a pallet that was meant for a regional distributor can be listed worldwide within days.

That distinction matters because your usual tools don't fit. A takedown notice built on trademark infringement often fails against genuinely authentic goods. You need to solve this upstream instead.

Gray market vs. counterfeit — a quick comparison

• Counterfeit: fake product, unknown source, clear legal remedy, brand-safety and consumer-safety risk.
• Gray market: real product, known source somewhere in your channel, weak legal remedy, margin and control risk.

Both erode trust, and in practice they overlap: once your product is trading through opaque channels, counterfeit units get mixed in. If counterfeits are your bigger worry, our guide to anti-counterfeiting software covers that side in more depth.

What the leak actually costs you

Precise numbers are hard to come by, because diverted goods leave no clean paper trail. But the available industry estimates are large enough to take seriously. Analysts at i2o Retail put gray market activity in the IT sector alone at more than $20 billion globally, and one widely cited industry estimate places the cost to US brands as high as $63 billion. A 2026 analysis by MetricsCart found that 53% of unauthorized sellers advertise below the brand's minimum advertised price.

Treat those as directional, not gospel. The costs you can measure yourself are usually these four:

• Margin compression. Once an unauthorized listing undercuts your MAP, your authorized partners ask for matching discounts.
• Channel conflict. Your best retail partners are the ones most likely to complain — and most expensive to lose.
• Support costs. Diverted units arrive without warranty coverage, in the wrong language, or past their freshness window, and the customer calls you.
• Review damage. A poor experience from an unauthorized seller lands on your product page, not theirs.

Why this is a data problem before it's a legal one

The instinct is to reach for lawyers. But most brands cannot name the source of the leak, and without that, enforcement is guesswork. The real question is not "who is this seller?" — it's "which of my partners sold them the stock?"

Answering that is a traceability problem. And traceability is a solvable engineering problem, which is good news: it means you can build your way to an answer rather than litigate your way to one.

Five steps to close the leak

1. Map your channel before you police it

Write down every route your product can take to a customer: direct, distributors, sub-distributors, retail, marketplace, refurb, returns, liquidation, samples. Most brands discover two or three routes they had forgotten about — returns and liquidation are the usual offenders. You cannot detect an anomaly until you've defined what normal looks like.

2. Serialize at the unit or lot level

This is the step that changes everything. Assign a unique serialized code — printed, QR, or NFC — to each unit or at minimum each lot, and record which account it shipped to. When you make a test purchase from an unauthorized listing and scan the code, "somebody is leaking" becomes "account #4 in the Midwest is leaking." That's an actionable fact, and it's usually enough to end the behavior in one phone call.

Serialization sounds heavy, but a lot-to-account mapping is a modest project: a code scheme, a print or label workflow, a database, and a scan endpoint. Our work on brand protection software almost always starts here, because the data it produces makes every downstream step cheaper.

3. Monitor listings continuously, not occasionally

Manual marketplace checks decay fast. A monitoring job that crawls your key marketplaces daily, records seller names, prices, and stock levels, and flags anything below MAP or outside your approved seller list gives you a timeline instead of a snapshot. Timelines are what reveal patterns — a seller who appears three days after each quarterly shipment to a particular region tells you a lot.

This is a natural fit for automation and lightweight AI-assisted classification: matching messy seller names, clustering listings that likely belong to the same operator, and separating genuine violations from noise.

4. Make your agreements enforceable, then enforce them

A MAP policy sets a pricing floor for advertising. An authorized-seller policy defines who may resell at all. Neither works unless your distribution agreements include resale restrictions, audit rights, and a real consequence — usually loss of rebate or termination. Enforcement should be consistent and unemotional: warn, document, then act. Brands that enforce selectively teach their channel that the policy is negotiable.

Talk to counsel before you finalize any pricing policy; the rules around what a brand may and may not require of resellers are genuinely nuanced in the US.

5. Give buyers a reason to verify

A scannable code on the package that confirms authenticity, activates a warranty, or registers the product turns your customers into a distributed detection network. Every scan tells you where a unit ended up. Brands that pair verification with something the customer actually wants — extended warranty, a how-to guide, reorder discount — see far better scan rates than those that offer a bare authenticity checkmark.

Build or buy?

Off-the-shelf monitoring platforms are a reasonable starting point if your main need is marketplace surveillance and takedown workflow. They are quick to deploy and require no engineering.

Custom is worth it when the problem is upstream: when you need serialization tied to your ERP, scan data flowing into your own dashboards, or a verification experience that lives inside your brand rather than a vendor's. It's also worth it when the data itself has strategic value — knowing exactly where units travel is useful for demand planning and sustainability reporting, not only enforcement. That kind of visibility is closely related to the supply chain transparency work more brands are being asked to demonstrate anyway.

A sensible sequence: buy monitoring now, build serialization over the next two quarters, and connect them once you can prove the leak's origin. If you're weighing that roadmap, our thinking on product development and go-to-market applies here too — ship the smallest version that produces a decision, then expand.

Start with one question

If you take one thing from this: before you spend a dollar on enforcement, make sure you can answer "where did this unit come from?" Everything else — takedowns, policies, hard conversations with distributors — gets easier once you can.

At Esipick, we've spent over a decade building traceability and brand protection systems for founders and mid-size businesses who need answers, not dashboards. If you're seeing listings you didn't authorize and can't tell where they came from, book a short call and we'll walk through your channel map with you — no pitch required. You can also explore the AI tooling behind this work at esipick.ai.