What Is a Test Buy, and When Does It Help a Counterfeit Case?
Published 2026-11-14 · Reviewed 2026-11-14 · By the Ingenious AI team
The short answer
A test buy is a controlled purchase of a suspected counterfeit listing, made so the goods themselves can be examined and documented. The marketplace packet's checklist requires you to state, for counterfeits, whether a test buy was made — because a photographed fake in hand is the strongest listing-level evidence a marketplace can receive, and because claiming one you never made would poison the filing.
What is test buys in counterfeit cases?
A test buy (or test purchase) is evidence-gathering by transaction: the brand orders the suspect product through normal channels, keeps the order record, and documents what arrives — packaging, markings, quality, origin — against the genuine article. In TakedownCoop's model it belongs to the marketplace channel, where the unit of action is the individual listing.
What is test buys in counterfeit cases?
A test buy (or test purchase) is evidence-gathering by transaction: the brand orders the suspect product through normal channels, keeps the order record, and documents what arrives — packaging, markings, quality, origin — against the genuine article. In TakedownCoop's model it belongs to the marketplace channel, where the unit of action is the individual listing.
The scan behind this page works in one pass over your whole street. It generates typosquat, homoglyph, affix and TLD-swap candidates from your domain, checks every one against real DNS resolution, searches Certificate Transparency logs for lookalike certificates, and tries a public, no-login check for fake profiles using your exact brand handle. For test buys in counterfeit cases, that means the first artefact you work from is evidence — what resolved, what holds a certificate, what could not be checked — rather than a screenshot someone sent you.
How the scan ranks and records it
Prioritisation is built into the result list. A hit that resolves and holds a certificate scores 90; resolving without a certificate, 80; registered but not resolving, 50 with a certificate and 40 without; a name seen only in Certificate Transparency logs scores 35, or 30 when it neither resolves nor is registered. You therefore deal with test buys in counterfeit cases in the order an impersonator would exploit it — live doors first — while the scan states plainly which checks it could not perform.
Evidence you can hold in your hand
Most takedown evidence is about representation — this name, this page, this ad claims to be us. A test buy is about the thing itself: the listing promised your product and delivered a counterfeit, which converts an IP complaint into a demonstrated consumer harm. Marketplaces escalate demonstrated harm differently from asserted harm, which is why the checklist isolates the question — state whether one was made — rather than burying it in narrative.
The discipline cuts both ways. If you made a test buy, document it like the screenshots: order confirmation, delivery record, dated photographs of the item and its packaging beside the genuine product. If you did not, the checklist's honest answer — none made — costs the filing nothing; listings are routinely actioned on registry evidence and photographs alone. What a filing cannot survive is a claimed test buy that evaporates under a reviewer's first question.
A worked example, end to end
A fictional footwear brand, Dune Walker at dunewalker.com, reports nine marketplace listings feeding from a lookalike store. For two listings it makes test buys: the orders arrive, counterfeit in stitching, sole mould and box print, photographed beside genuine pairs with the order numbers visible. All nine reports state the non-authorisation plainly; the two test-buy reports say so, with the documentation attached, and the other seven say no test buy was made. The marketplace escalates the seller — not any single listing — on the combined file, which is exactly the case-history effect the checklist promises.
Turning evidence into a filing
A complaint says 'this is fake'; a packet proves it. The Pro packet generator turns a confirmed hit into a channel-correct evidence packet — one for the registrar, one for the host, and separate ones for Meta, Google Ads, marketplaces and app stores where they apply — each with a filing checklist written for that channel. The honesty rule is printed in every packet: TakedownCoop prepares the evidence and never claims to submit to a channel it cannot actually submit to. Filing stays with you or your agent, which is also why the evidence has to stand on its own.
- Decide per listing whether a test buy adds anything the photographs do not
- If you buy, keep the full chain: order record, delivery, dated photos beside the genuine article
- State in every counterfeit report whether a test buy was made — as the checklist requires
- Never claim a test buy you did not make
- File the test-buy documentation with the listing's case, not just the marketplace
After you file: tracking the case
What happens next is tracked, not hoped for. Each target becomes a case — domain, fake store, social profile or scam ad — moving through evidence collected, packet built, submitted, provider response, resolved or reappeared. TakedownCoop distinguishes what you attest (that you submitted, that a provider replied) from what is verified by re-scan (that the item is actually gone), and it schedules a recheck seven days after a case is submitted so silence from a provider becomes a prompt, not a dead end.
Where efforts like this usually go wrong
A second failure is overreach — padding a filing with suspicions the evidence does not carry. TakedownCoop's scan is careful to separate what it confirmed from what it could not check, and a filing should inherit that discipline exactly: claim the resolving domain, the certificate, the screenshots you actually hold, and stop there. Reviewers act fastest on filings whose every sentence they can verify, and a single inflated claim taxes all the true ones beside it.
Finally, do not let a win delete the record. Brands that close a takedown by celebrating and clearing the folder meet the reappearance defenceless; brands that keep the case — evidence, tickets, verified resolution and all — meet it with precedent. In this product the record is not paperwork after the work. Kept properly, it is most of the work, because the second filing is always the one that ends the pattern.
Keeping it from coming back
Closing the loop matters because clones come back under new names and new accounts. Re-appearance monitoring re-scans and regenerates packets; the verified-genuine page lets a cautious customer verify your real door before paying anyone; and the case timeline — every event, in order — exports as JSON or CSV when a processor, insurer or marketplace asks how you handled it. That is the co-op model applied to test buys in counterfeit cases: walk the street, knock with evidence, keep watch.
Frequently asked questions
Is a test buy mandatory for marketplace reports?
No. The checklist asks you to state whether one was made. Many listings are actioned without one.
Which channel cares about test buys?
Marketplaces — the question appears in the marketplace packet's checklist, attached to counterfeit listings specifically.
What should a test buy document?
The order, the delivery, and the item itself photographed against the genuine product — packaging, markings and the differences that prove counterfeit.
Does a test buy help the domain filings?
Indirectly: it is marketplace evidence, but its documentation strengthens the campaign's overall pattern when cases are escalated together.
Keep exploring
TakedownCoop home — run the free brand scan · All TakedownCoop guides · Pricing — Free, Pro and Agency · Get a license key · Takedown cases · My street (dashboard) · Terms · Privacy · Ingenious AI — all platforms
Related guides
- How Do You State That You Never Authorised the Seller?
- How Do Small Businesses Protect Their Brand Without a Legal Department?
- How Should an Agency Monitor Client Brands for Impersonation?
- How Do Online Sellers Fight Clone Stores?
- How Do App Developers Fight Clone Apps?
- How Can You Check If Someone Is Impersonating Your Business Online?