Counterfeit enforcement fails when it treats each storefront as a separate seller, because it usually is not. One operation runs dozens of storefronts across marketplaces, rotating inventory between them as takedowns land. The storefronts share tells: product photography, ship-from locations, pricing patterns, review manipulation styles. Mapping those connections turns thirty separate reports into one network case, and networks are what platforms can actually dismantle.
Storefronts are disposable; the operation behind them is not. When a marketplace removes one storefront, the operator spins up another with a new name, new email, and the same inventory photos. The economics demand it: building a new storefront costs nearly nothing, while the supplier relationships, product molds, and fulfillment pipeline behind it are expensive to rebuild. Every enforcement system that counts removed storefronts as wins is measuring the wrong thing.
The operations that last run portfolios. A mid-size counterfeit operation might maintain twenty storefronts on one marketplace and mirror inventory across three more, plus social storefronts for discovery. Takedowns that remove two storefronts a month are a rounding error against that kind of redundancy.
Start with the photography. Counterfeit operations reuse the same product images across storefronts because reshooting is work. Identical images, including identical flaws and backgrounds, across different seller names is the strongest single signal. Screenshot and archive everything; storefronts change photos once they realize they are being watched.
Then the logistics: ship-from locations, shipping times, return addresses from test buys. Then pricing: operations price their network in bands, and identical odd price points across sellers are a fingerprint. Then the text: listing copy, about-us pages, and review responses share phrasing because one person wrote them all. Any two of these together is a connection worth documenting.
The map is a simple document: each storefront as a node, each shared tell as a link, with screenshots as evidence. A spreadsheet works. For each storefront record the seller name, marketplace, storefront URL, product images (hashed or side-by-sided), ship-from location, price points, and any test-buy data. The pattern usually emerges by the tenth storefront: the same photos, the same city, the same pricing bands.
Keep the map current. Operations evolve: they change photo sets, move fulfillment, rebrand. A map from six months ago describes an operation that no longer exists in that exact form. Review and update it quarterly, or after every major enforcement action, since takedowns are when operations restructure.
The filing strategy changes once you have the map. Instead of thirty individual listing reports, file the network: one case that names the connected storefronts, documents the shared tells, and asks for action against the operation. Platforms have teams and tools for network enforcement that the standard reporting portal never shows you; the map is what gets your case routed to them.
Reference the connections explicitly in every filing. Reviewers decide quickly and will not connect the dots themselves. Storefront A shares product photography with storefronts B and C, ships from the same address as D, and was created two days after B was removed: that sentence does more work than thirty separate complaints.
Some networks are too large or too persistent for portal reporting. The escalation paths are the platform's brand protection programs, which offer dedicated contacts and network-level tools, and, for the worst cases, legal action against the operators, who are often identifiable through payment and shipping records once you know where to look. The map you built is the foundation for both: it is the document that turns a pile of complaints into a case.