---
title: "Amazon selling restrictions and how to check them first"
description: "An Amazon selling restriction is an answer about your own seller account rather than the product, so check every ASIN before the purchase order goes out."
question: "How do I check if I can sell a product before I buy it?"
cluster: amazon-mechanics
published: 2026-08-09
updated: 2026-08-09
tags: [selling-restrictions, gating, sellability, sp-api]
related: [amazon-brand-gating-explained, get-ungated-on-amazon, what-is-gating, scan-wholesale-price-list-for-profit]
---

Amazon selling restrictions are checked per ASIN against your own seller account, and the check belongs before the purchase order — after the stock lands there is no cheap fix.

The check itself is free and resolves in a single API call. The mistake it prevents is the entire landed cost of a case pack sitting in a warehouse you are not permitted to list from.

## What an Amazon eligibility answer depends on

An Amazon eligibility answer describes one seller account paired with one listing at one moment, which is why a screenshot from a forum or a supplier transfers nothing to yours. Amazon's Listings Restrictions API takes the ASIN, the condition, the seller and the marketplace, and returns the restrictions that apply to that combination (Amazon SP-API documentation, checked 2026-08-03).

**Table: What changes an Amazon eligibility answer for the same product**

| Input | A change that flips the answer | Who controls it |
|---|---|---|
| Seller account | An ungating approval lands, or a policy violation does | You, then Amazon |
| ASIN | Amazon merges the listing into a gated parent | Amazon |
| Condition | New is permitted while Used and Refurbished are blocked | Amazon and the brand |
| Marketplace | Eligible on amazon.com, blocked on amazon.ca | Amazon |
| Date | The brand enrolls in Brand Registry and gates its catalog | The brand |

The date row is what makes caching dangerous: eligibility is a permission, and permissions carry no expiry stamp.

## The four states worth tracking, not two

Two states — allowed and not allowed — is the wrong model for a wholesale catalog, because it merges openable rows with permanently closed ones and unanswered rows with approved ones. Forge Command derives one sellability status per catalog row from raw Amazon SP-API restriction fields rather than storing it, producing four states.

**Table: The four sellability states derived from Amazon restriction data**

| State | Interface label | What it means | Correct next action |
|---|---|---|---|
| sellable | Approved to Sell | No restriction for this account, ASIN and condition | Cost the row and buy it |
| approval_required | Applied to Sell | Gated, but an application route exists | Price the application effort first |
| restricted | Restricted | Hard block, including firearms and FFL rows | Drop the row |
| unknown | Not Checked | No ASIN matched yet, so no answer exists | Match the row before judging it |

Collapsing approval_required into restricted hides openable listings; collapsing unknown into sellable turns an unanswered question into a yes, which is the more expensive error.

## Approval available versus a hard block

Approval available means Amazon will accept an application from your account; a hard block means no application path exists from the seller side at all. The two look similar in a spreadsheet and are worth completely different money.

An approval-available row on a brand you already buy from is close to a sellable row, because Amazon usually asks for invoices from an authorized source and you already hold them. An approval-available row on a brand you have never bought from is a project: the wholesale account has to be opened before the ungating application can be filed. A hard block is worth zero regardless of margin. Sort a shortlist into those three buckets before anyone contacts a supplier — [Amazon brand gating and why you cannot list a product](/docs/amazon-brand-gating-explained) covers the causes, and [how to get ungated in an Amazon category or brand](/docs/get-ungated-on-amazon) covers the application.

## Restriction types a wholesale buyer actually hits

Six restriction types account for nearly every blocked row on a wholesale catalog, and they differ in whether an approval route exists rather than in how they look on the listing page.

Brand gating is the most common: the rights owner restricts who may create an offer, and the route out is invoices from an authorized distributor. Category gating applies to a whole category rather than one brand and has a documented application. Condition gating blocks Used or Refurbished offers on listings where New is fine, which matters when a distributor sells open-box stock. Hazmat classification is a fulfillment-route problem rather than a permission problem, and the fix is a dangerous-goods review. Regulatory restrictions such as firearms and FFL-controlled accessories have no seller-side route for most accounts. Account-level intellectual-property complaints follow the account rather than the ASIN, and the remedy is an appeal. [What gating means on Amazon and the types that exist](/docs/what-is-gating) sets out the vocabulary.

## Where the restriction check belongs in the buying cycle

The restriction check belongs at three points, and the cost of skipping it rises by roughly two orders of magnitude between the first and the last.

At the shortlist stage, run the restriction check after the ROI floor rather than before it. Amazon batches catalog, pricing and fee lookups at 20 identifiers per request, and the restriction check does not batch the same way, so it runs far closer to one row at a time — [how to scan a wholesale price list for profitable ASINs](/docs/scan-wholesale-price-list-for-profit) sets the order of operations. Before the purchase order, re-check every row you are about to buy, on the day: a case pack of 144 units at $6.10 landed is $878.40 committed on one row, and the check protecting it is free. At receiving the check is only a diagnostic, and the recovery ladder is return to supplier, sell off Amazon, or liquidate.

## Why a stored restriction answer goes stale

A restriction answer stored as a column is a snapshot of a permission, and a stored snapshot cannot tell you it has expired. That is why Forge Command computes sellability from raw SP-API restriction fields on every read rather than writing it to the row.

The failure mode is quiet. A catalog scanned in March records a brand as Approved to Sell, the brand enrolls in Brand Registry in May, and the June purchase order is built from the March answer with nothing flagging the change. Two habits contain the problem regardless of tooling: treat any eligibility answer older than the current buying cycle as unknown, and keep the Not Checked state visible in reporting instead of letting unmatched rows drift into an approved-looking bucket.

## Frequently asked questions

### Does checking a selling restriction cost anything

No. The restriction check is an ordinary Amazon SP-API call against your own seller account and carries no fee. The cost is throughput: it does not batch at 20 identifiers per request the way catalog, pricing and fee lookups do.

### Can my VA check restrictions on my behalf

Only from inside your seller account. Eligibility resolves per seller account, so a VA checking from their own account returns an answer that does not describe your permissions. Give the VA scoped access rather than accepting a result from elsewhere.

### Does Approved to Sell mean the brand has approved me

No. Approved to Sell is Amazon's answer about whether your account may create an offer on that ASIN. It says nothing about your wholesale contract, your authorized-reseller status, or a MAP policy, all of which the brand enforces independently of Amazon.

### What should I do with a row showing Not Checked

Match it before judging it. Not Checked means no ASIN has been matched to that supplier row, so there is no listing to ask Amazon about. A 10 to 15 percent no-match rate is normal on a real wholesale catalog.