What Is an ASIN Number? Amazon's Product ID, Explained

Every product in Amazon's catalog carries exactly one ASIN per marketplace: a 10-character code, usually starting with B0, that identifies the product page itself. Paste an ASIN like B0ABC12345 (an illustrative example) into Amazon's search bar and you land on one specific listing. That listing might be sold by Amazon, by you, and by fourteen other sellers all at once, which is precisely why the ASIN confuses so many sellers when it shows up in fee reports, inventory files, and reimbursement claims.

This guide covers what an ASIN number actually is, how it differs from the SKU, FNSKU, UPC, and GTIN codes that surround it, how to run an ASIN lookup, how parent and child ASINs work for variations, and why your accounting and inventory systems should be keyed on SKU rather than ASIN.

What is an ASIN number, exactly?

ASIN stands for Amazon Standard Identification Number. It is a 10-character alphanumeric identifier that Amazon assigns to every product in its catalog. For most categories the ASIN begins with B0; for books, Amazon typically reuses the book's 10-digit ISBN as the ASIN, which is a useful reminder that the ASIN was originally modeled on the ISBN system.

The crucial mental model: an ASIN identifies a product page, not your inventory. It belongs to Amazon's catalog, not to any seller. If three merchants sell the identical phone case, they all attach their offers to the same ASIN and compete for the featured offer (the buy box). ASINs are also marketplace-specific. The same physical product can carry a different ASIN on Amazon.com than on Amazon.co.uk, so never assume one ASIN travels globally.

ASIN vs SKU vs FNSKU vs UPC vs GTIN

Sellers juggle at least four identifier systems, and each answers a different question. The ASIN answers "which Amazon catalog page is this?" The SKU (stock keeping unit) answers "which item in my business is this?"; it is a code you invent, visible only to you, and it can encode supplier, cost batch, condition, or anything else you find useful. The FNSKU (Fulfillment Network SKU) answers "whose unit is sitting in this Amazon warehouse?"; it is the barcode, usually starting with X00, that Amazon prints on FBA labels so it can tell your units apart from another seller's units of the same ASIN. The UPC is a 12-digit retail barcode that exists outside Amazon entirely; it is one format of GTIN (Global Trade Item Number), the umbrella standard that also covers 13-digit EANs and ISBNs.

The relationships matter more than the definitions. A GTIN (UPC/EAN) is usually what you use to create or match an ASIN. One ASIN can have many sellers, but each of your seller SKUs maps to exactly one ASIN. And each FBA SKU gets its own FNSKU, so a single ASIN stocked by five FBA sellers has five different FNSKUs in Amazon's warehouses.

• •ASIN: Amazon's catalog ID for a product page; shared by all sellers on that listing
• •SKU: your private inventory code; one seller, one offer, your naming rules
• •FNSKU: Amazon's warehouse barcode tying physical FBA units to your SKU
• •UPC/EAN (GTIN): the universal retail barcode that exists beyond Amazon

How ASINs are created

You never invent an ASIN yourself; Amazon issues it. When you list a product, Amazon first checks whether your GTIN (usually a UPC or EAN) matches an existing catalog page. If it does, your offer attaches to that existing ASIN. You do not get a new one, and creating a duplicate page for a product that already exists violates Amazon's catalog policy. If no match exists, Amazon creates a new ASIN from the product data you submit.

Private-label and handmade sellers without barcodes can apply for a GTIN exemption in eligible categories, which lets Amazon generate an ASIN without a UPC. Brand-registered sellers also get stronger control over the content on the ASINs they own. Either way, once the ASIN exists it is permanent: it stays attached to that product page even if every seller abandons the listing.

One caution on sourcing barcodes: Amazon expects GTINs to come from GS1, the standards body that licenses them. Cheap third-party UPC resellers are a known trap; codes that don't trace back to a GS1 registration matching your brand can cause listing errors or removals later. If you're building a private-label catalog, budget for legitimate GS1 codes from the start.

Amazon FBA UPC requirements are the same requirements that apply to listing at all, since the barcode's job is done before your units ever ship: the GTIN has to be valid, has to trace to your brand's GS1 registration, and has to match the ASIN your offer attaches to. Once the shipment is created, the label that actually travels on the box is the FNSKU, not the UPC, unless you're enrolled in commingled (stickerless) inventory.

ASIN lookup: four ways to find any ASIN

An ASIN lookup rarely requires special tools. The fastest method is hiding in plain sight in the product page URL, and Seller Central gives you bulk options when you need to map hundreds of products at once.

Parent and child ASINs for variations

Products that come in sizes, colors, or pack counts use a parent-child structure. The parent ASIN is a non-buyable umbrella that groups the family so shoppers see one page with a size and color picker. Each actual variation, say a t-shirt in medium/blue versus large/black, is a child ASIN with its own price, reviews rollup behavior, sales rank data, and inventory.

This trips up reporting constantly. Sales, fees, and FBA inventory always happen at the child ASIN level, because the parent is not a real product. If your analysis stops at the parent, you can miss that one child variation is profitable while another is quietly losing money after fulfillment fees. When you file reimbursement claims or audit FBA shipments, you are always working with child ASINs and their FNSKUs, never the parent.

One ASIN, many sellers; one SKU, one ASIN

Because the ASIN belongs to the catalog, any authorized seller can attach an offer to it. A popular ASIN might show twenty offers competing on price, fulfillment speed, and seller rating for the featured offer. Amazon's referral fee, typically 8-15% of the sale price depending on category, applies to whichever seller wins the sale, calculated on that seller's price.

Your SKU, by contrast, is unambiguous. It points to one offer, from one seller (you), on one ASIN, with one cost basis. Two of your SKUs can even point at the same ASIN, say, one SKU for FBA stock and another for merchant-fulfilled stock, or separate SKUs for two purchase batches. The arrow only flows one way: SKU to ASIN is always one-to-one from your side, while ASIN to SKU is one-to-many across the marketplace.

ASIN edge cases that bite sellers

Most identifier problems surface months later, in reports that no longer add up. A few patterns account for nearly all of them.

Amazon also merges and splits ASINs over its own catalog-cleanup cycles. A merge can combine two pages (and their reviews) into one surviving ASIN; a split can strand your offer on a page with someone else's images. Your sales history follows your SKU either way, which is one more argument for treating the SKU as your permanent key and the ASIN as a mapped, changeable attribute.

When one of these goes wrong, fixing it means opening a case. There's no published Amazon Seller Support phone number you can dial: you contact Seller Support from inside Seller Central, describe the issue, and request a callback if you want to talk to a person. Bring the before-and-after mapping export, screenshots, and the specific ASINs and SKUs involved, because the first-line agent will close a vague case fast. The same route handles listing suppressions and returns disputes; there's no separate Amazon returns phone number for sellers either.

• •Duplicate ASINs: listing a product that already exists creates a policy violation and splits sales history across pages
• •Piggybacking: other sellers attaching to your private-label ASIN and undercutting you; Brand Registry is the main defense
• •Variation abuse: bolting unrelated products onto a parent to inherit reviews, a fast route to listing suppression
• •Reused SKUs: pointing an old SKU at a new ASIN, which silently corrupts cost, sales, and reimbursement history
• •Merged or changed ASINs: catalog cleanups can move your offer; regular mapping exports let you reconstruct what happened

Why accounting and inventory tools key on SKU, not ASIN

Margin lives at the SKU level. Suppose you sell a kitchen scale for $25 (an example). The ASIN tells you nothing about what that unit cost you, but your SKU can carry a landed cost of, say, $9.40 from one PO and $10.10 from the next. Cost of goods sold, inventory valuation, and per-unit profit all require the SKU-to-cost link that an ASIN simply cannot hold, because the ASIN is shared by sellers with completely different costs.

Amazon FBA storage costs make the same point from the other direction. Amazon bills a monthly storage charge based on the volume your units occupy, plus surcharges on inventory that ages past a threshold, and those costs attach to physical units, which means they attach to your SKU. Two SKUs sitting on one ASIN, an FBA offer and a merchant-fulfilled offer, carry wildly different storage costs and wildly different true margins, and no ASIN-level report will ever show you that.

Then there's the money side. Amazon marketplace payments arrive as netted settlements rather than per-order deposits, so the only way to get from a payout to per-SKU profit is to split each settlement into gross sales, fees, and refunds and match those lines back to SKU.

The same logic applies to multichannel sellers: the SKU is the only identifier that can follow a product from Amazon to Shopify to eBay, since ASINs do not exist off Amazon. Anyone selling the same catalog across eBay and Amazon learns this quickly, usually after a month of trying to reconcile two systems that name the same product differently. Any multi channel inventory management software worth using anchors on SKU for exactly this reason, and the same is true of amazon fba accounting tools: BeanHawk, for example, keys its perpetual SKU-level inventory valuation and PO landed-cost engine to SKU and treats the ASIN as an attribute of the Amazon channel, not as the unit of account. Reimbursements are the one area where ASIN-level identifiers still matter operationally: lost FBA inventory is tracked by FNSKU and child ASIN, then valued against your sourcing cost. Since March 31, 2025, Amazon values reimbursements at the seller's manufacturing or sourcing cost (using its own estimate unless you provide your cost), excluding your margin and fees, another reason accurate SKU-level costs are worth maintaining.

Practical checklist: keep your identifiers clean

A few habits prevent most ASIN-related accounting messes. Treat your SKU scheme as permanent infrastructure: once a SKU has sales history, renaming it fragments your reporting. And export the SKU-ASIN-FNSKU mapping regularly, because Amazon merges and splits ASINs over time and your records should capture the state at each point.

If you sell through FBA, identifier hygiene also pays in recoveries. Amazon's claim window for fulfillment-center losses was cut to 60 days in October 2024, so SKU and FNSKU records need to be reconciled continuously, not at year-end. BeanHawk runs a free FBA reimbursement audit (no card required, and you keep 100% of recoveries) and posts summarized settlement journals to QuickBooks Online and Xero, with flat all-channel pricing from $19/mo, all keyed on SKU, with ASIN and FNSKU kept as mapped attributes.

• •Design SKUs you control: supplier, batch, or condition codes beat random strings
• •Never reuse a SKU for a different product or cost basis
• •Export your SKU-ASIN-FNSKU mapping from Seller Central on a regular schedule
• •Track costs and margin per SKU; treat ASIN as a channel attribute
• •Reconcile FBA inventory by FNSKU within the 60-day claim window