Small seller here, just got hit by a hijacker for the first time.

Professional one – shows up out of nowhere during peak hours, vanishes by morning.

I cut my price by $2 to grab the Buy Box back. Next day they undercut me by $0.10 and took it again. I dropped another dollar. They matched it, still $0.10 below me. Price war is going nowhere.

I thought about dropping to $3.99 and then taking my listing down – but if they don’t follow the price down, it won’t do anything.

Product is a generic 1688-style item. Lots of sellers can get it. The only difference I have is custom white box packaging. I have a registered trademark (R mark), properly branded, brand registered in the right category.

I know about Test Buy + brand complaints, Transparency, Project Zero. But my situation is simple:

  • This ASIN is less than 10% of my total sales and profit. Steady old listing, not a big driver.

  • I only have one seller account. Account and brand safety are my #1 priority.

  • If removing the hijacker could put my brand or account at risk, I’d rather just abandon this ASIN entirely.

My questions:

  1. For a generic product with only custom packaging, can I do a Test Buy + counterfeit complaint without risking a brand abuse flag?

  2. Any safe, proven ways to remove a hijacker that won’t get me in trouble?

  3. Is Transparency worth the cost for a low-volume ASIN? What’s the real cost in 2026?

  4. Anyone successfully used the new Brand Catalog Lock to stop hijacking?

Appreciate any insight from people who’ve been through this.


Sellers Global editorial guidance: evidence before a removal complaint

Added by Sellers Global · 16 October 2026. The original poster's situation remains above and has not been independently verified. This supplement was prepared with AI assistance. Official sources were checked on the update date; no particular complaint outcome is promised.

A registered trademark and custom packaging do not, on their own, establish what another seller shipped. Start by separating an additional offer for genuine goods, materially different goods, inaccurate detail-page content, and a suspected counterfeit. The evidence and available remedies can differ. A price difference is not proof of infringement.

Document the product and the disputed offer

Save the marketplace, ASIN, seller identifier, offer URL, date, and the precise statement you believe is inaccurate. Keep your own product specifications, branded packaging photographs, trademark information, and supply-chain records together. Describe the difference you can demonstrate instead of beginning with a label such as “professional hijacker.”

If you arrange a test purchase, record which seller fulfilled the order and preserve the received item, packaging, labels, invoice or order record, and clear photographs. A test purchase is evidence collection; it does not guarantee that a counterfeit complaint is valid or successful. Do not invent a mismatch or manipulate a review to strengthen a report.

Choose the report that matches the evidence

Amazon's IP reporting guide explains its rights-owner reporting paths. Brand Registry's FAQs also identify support and marketplace abuse reporting routes. Use the applicable path for the specific issue and keep the allegations consistent with the evidence.

If the issue is a genuine reseller, a distribution dispute, or uncertainty over what rights apply, a counterfeit allegation is not an automatic solution. Resolve the factual and legal basis before submission. If Amazon rejects a report, keep the report ID and address the stated reason; repeatedly changing the allegation without new support does not establish that the alternative is correct.

Evaluate Transparency using the actual operational cost

Amazon's Transparency page explains that protections become active after the operational performance review and that protected units require valid codes in supported stores. Its current public pricing table lists $0.05 per code for 1–1,000,000 generated codes, with lower tiers at higher volumes, and notes that fees vary by volume and geography. Confirm the applicable quote and account terms before committing.

For a small ASIN, compare the entire workflow, not just the code price. A hypothetical 1,000 units at $0.05 would cost $50 for codes alone. That example excludes printing, applying labels, supplier coordination, rework, and handling existing uncoded inventory. It is not a quote for this poster's marketplace or a forecast of savings.

Make sure legitimate manufacturers and sellers can follow the code process. Ask the program team how it applies to the existing supply chain, fulfillment methods, and future authorized sellers. Do not infer that enrollment automatically prevents all legitimate resale or that changing stores removes the requirements.

Do not rely on an unverified “catalog lock” promise

The public official sources reviewed for this update do not establish the “Brand Catalog Lock” feature or outcome described in the question. If that control appears in your account, obtain its current official help text and ask support exactly what it restricts: detail-page contributions, brand associations, or offers. Those are different actions. Avoid paying for a service on an unverified promise that it can block every other seller.

Decide whether the ASIN is worth further work

Compare the ASIN's contribution after fees, returns, advertising, and support effort with the cost of investigation and preventive controls. Use your actual records rather than the original post's unverified share of sales. You can decide that further spending is uneconomic without making an unsupported complaint or entering a price war.

Related threads cover a disabled trademark report option, multiple-account risks, and advertising budget economics. In a follow-up, share the marketplace, documented product difference, reporting category, and support response with private information removed.