At a glance
The count of your private-label ASINs where someone else has appeared as a competing offer. On a brand you own and control, you should be the only seller on the listing. When a third party shows up, it is a hijack candidate: a counterfeiter, an unauthorised reseller, or an arbitrageur who bought your stock and is reselling it. Any number above zero on a private-label ASIN deserves attention, because hijackers undercut your price, win your Buy Box, and put your brand reputation in someone else’s hands.
| What it counts | The number of your private-label ASINs that currently have one or more competing offers from other sellers. It is a real-time count of listings where you are no longer the sole offer. |
| Why it matters on private label | For a private-label brand, you should be the only seller. A third-party offer means either a hijacker (often counterfeit or grey-market stock), an unauthorised reseller, or an arbitrageur reselling units they bought from you. All three threaten price, Buy Box, and brand control. |
| What it is NOT | This is not about legitimate multi-seller ASINs (generic products many sellers list). It targets ASINs that are yours alone by brand. On a shared catalogue ASIN, competing offers are expected and not a hijack. |
| Buy Box link | A hijacker’s whole goal is usually to win the Buy Box by undercutting you. So this card is the leading indicator for Buy Box loss on private-label ASINs; pair with the Buy Box cards. |
| Brand Registry | Enrolment in Amazon Brand Registry is the primary defence. It gives you tools (Report a Violation, Transparency, Project Zero) to remove hijackers. Coverage gaps leave ASINs exposed. |
| FBA vs FBM | A hijacker can be FBA or FBM. An FBA hijacker selling counterfeit stock is the most damaging because it can win the Buy Box with Prime eligibility and ship goods you did not make under your brand. |
| Reading the value | On private-label ASINs, the target is zero. Any non-zero count is a worklist. Track which ASINs and how long the offer has persisted. |
| Currency / unit | number |
| Time window | RT (real-time / latest snapshot) |
| Alert trigger | >0 on private-label ASINs |
| Roles | owner, marketing, operations |
Calculation
Calculated automatically from your Amazon Seller Central data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A private-label supplements brand on Amazon US, Brand Registry enrolled, snapshot 30 Apr 26. All numbers illustrative.| Private-label ASIN | Your price | Competing offer price | Offer fulfilment | Buy Box holder | Likely cause |
|---|---|---|---|---|---|
| Whey protein 1kg | $39.99 | $34.50 | FBM | Hijacker | Arbitrageur reselling bought units |
| Creatine 500g | $24.99 | (none) | n/a | You | Clean |
| Multivitamin 90ct | $19.99 | $18.00 | FBA | Hijacker | Possible counterfeit, FBA-shipped |
| Pre-workout 300g | $29.99 | (none) | n/a | You | Clean |
| ASINs with third-party offers | 2 flagged |
- Any non-zero count fires the alert. Two private-label ASINs with competing offers breaches
>0 on private-label ASINs. On a brand you own, this is never normal; Vortex IQ Nerve Centre flags it immediately so you can act while the hijacker is fresh. - The FBA hijacker on the multivitamin is the most dangerous. An FBA-fulfilled competing offer can win the Buy Box with Prime eligibility and ships goods you did not make under your brand. If those units are counterfeit, every bad review and safety complaint lands on your listing. This is the one to escalate first.
- The protein hijacker is likely arbitrage. A 39.99 product, FBM, often means someone bought your units (on sale, via a coupon, or wholesale) and is reselling at a margin. It still steals your Buy Box and trains buyers to wait for the cheaper offer.
- The Buy Box consequence is immediate. Both hijackers undercut you, so both can take the Buy Box. Watch Buy-Box Win Rate (top-50 ASINs) and Estimated Revenue Lost to Buy-Box Loss; the revenue impact shows there.
- Brand Registry is the enforcement lever. Because this brand is enrolled, it can use Report a Violation, test buys, and (for counterfeits) Transparency or Project Zero to remove the offers. A brand not enrolled has far weaker tools, which is why coverage matters.
Sibling cards merchants should reference together
A hijack is a Buy Box and brand problem; read this with:| Card | Why pair it with ASINs with Third-Party Offers |
|---|---|
| Buy-Box Win Rate (top-50 ASINs) | Hijackers steal the Buy Box; this card shows the resulting win-rate hit. |
| Estimated Revenue Lost to Buy-Box Loss | Quantifies the revenue a hijacker is costing you. |
| Top Buy-Box-Loss ASINs | Cross-check whether the hijacked ASINs are the ones losing Buy Box. |
| Brand Registry Coverage | Your enforcement toolkit depends on enrolment; gaps explain why a hijacker is hard to remove. |
| Buy-Box Loss Burst | A sudden Buy Box collapse often coincides with a hijacker appearing. |
| Negative Feedback Spike | Counterfeit hijackers generate complaints that land on your listing. |
Reconciling against Amazon Seller Central
Where to look in Amazon Seller Central:Open the product detail page for each ASIN and check the “Other Sellers on Amazon” / offers section, or use Manage Inventory and the Buy Box / offer-count indicators. Brand Registry enrolled sellers can use Brand Dashboard and Report a Violation to see and act on competing offers.There is no single native “count of hijacked ASINs” report; this card aggregates the offer-count signal across your private-label ASINs for you. Timing, settlement, and reporting-lag table:
| Topic | Detail |
|---|---|
| Timezone | This is a point-in-time offer snapshot, not a windowed metric, so timezone has little effect. The card reads the latest available offer state. |
| Offer-state latency | A hijacker can appear or vanish within hours. The card refreshes on the standard data cadence, so a brand-new offer may take a refresh cycle to appear and a removed one to clear. |
| Private-label classification | The card needs to know which ASINs are yours-alone (private label) versus shared-catalogue. Misclassification can flag a legitimately shared ASIN or miss a hijacked one; review the brand mapping if results look off. |
| Buy Box vs offer presence | An offer can exist without holding the Buy Box. The card counts the presence of competing offers, not only Buy-Box-winning ones. |
| Reason | Direction | Why |
|---|---|---|
| Refresh latency | Either | A hijacker that appeared minutes ago may not yet be in the card; one removed minutes ago may still show until the next refresh. |
| Private-label scoping | Either | If an ASIN is mis-tagged as private label (or not), the count includes or excludes it differently from your manual view. |
| Regional offer visibility | Either | Offer presence can vary by marketplace; the card reflects the marketplace it is reading. |
| Suppressed / inactive offers | Either | An offer that is out of stock or suppressed may or may not surface depending on Amazon’s display state. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
ebay.active-listings | No direct peer. eBay listings are seller-specific (you own your listing), so there is no shared-ASIN hijack mechanic. | Conceptual only; eBay brand abuse looks different (counterfeit listings, not shared offers). |
shopify.total_revenue | Independent channel. A DTC store cannot be hijacked the way an Amazon ASIN can. | No reconciliation; arbitrageurs sometimes source from your DTC sales, so tightening DTC discounting can reduce Amazon arbitrage. |
Known limitations / merchant FAQs
A third-party offer appeared on my private-label ASIN. What do I do first? Identify the offer type. If it is FBA and you suspect counterfeit, escalate via Brand Registry (Report a Violation, and Transparency or Project Zero if enrolled) and consider a test buy to confirm. If it is an arbitrageur reselling genuine units, you can tighten the leaks (reduce deep discounts and wholesale that feed arbitrage) and still report unauthorised use of your brand. Is every competing offer a hijack? Only on ASINs that are genuinely yours alone (private label). On shared-catalogue ASINs that many sellers legitimately list, competing offers are normal and expected. The card is meant to be scoped to your private-label ASINs; check the brand mapping if it flags a shared product. The offer is gone but the card still shows it. Why? Offer state changes fast and the card refreshes on a cadence. A removed offer can persist on the card until the next refresh, and a brand-new one can take a cycle to appear. Re-check the detail page for the live state. Why does Brand Registry matter so much here? Enrolment unlocks the enforcement tools (Report a Violation, Transparency, Project Zero) that actually remove hijackers. Without it, your options are slower and weaker. If hijacking is a recurring problem, closing Brand Registry Coverage gaps is the highest-leverage fix. Can I change the alert threshold? Yes, the>0 on private-label ASINs default is configurable per profile in the Sensitivity tab. For private label, zero is the right target and we recommend leaving it; raise it only if you knowingly allow authorised resellers on certain ASINs.