What is ASIN?

What does ASIN stand for, and what is an ASIN code?

ASIN stands for Amazon Standard Identification Number. The ASIN code is a 10-character alphanumeric string. For most products other than books it begins with the letters "B" followed by nine characters. Books are the exception: their ASIN is simply the 10-digit ISBN. Amazon generates the ASIN automatically when a product is first added to the catalog, and it stays attached to that listing for the life of the product.

Ask what an ASIN number is supposed to mean, character by character, and the honest answer is: nothing. Unlike a SKU you design yourself, the string carries no encoded brand, size, or batch information. It's an opaque pointer to a catalog record, which is precisely why you can't read a cost or a variation out of it and shouldn't try.

The ASIN meaning that trips people up is this: one ASIN equals one product page, shared across all sellers of that product. When ten merchants sell the same branded item, they are all attached to the same ASIN and compete on that single listing. Your own seller-defined SKU, by contrast, is private to your account. That distinction matters the moment you start reconciling sales, because Amazon reports activity at the SKU and order level, while shoppers and competitors see the ASIN.

One more nuance: an ASIN outlives its sellers. If every merchant stops offering a product, the ASIN doesn't disappear. The detail page goes dormant, keeps its reviews and sales history, and reactivates the moment someone lists against it again. That's why buying into an established ASIN with reviews is a completely different commercial decision than creating a fresh one, even for an identical physical product.

How to do an Amazon ASIN lookup

The fastest Amazon ASIN search is the product URL itself. On any listing, the ASIN appears in the address right after /dp/ or /gp/product/. You'll also find it in the "Product information" or "Additional Information" section near the bottom of the detail page. Inside Seller Central, your ASINs are listed in Manage Inventory next to each offer, and they flow through to your reports and the Amazon API.

Sellers commonly need to map identifiers in both directions: ASIN to UPC when listing against an existing catalog entry, or FNSKU to ASIN when investigating a warehouse discrepancy. Tools and the Amazon catalog API let you resolve an ASIN from a UPC, EAN, or your own SKU. Keep in mind that ASINs are also marketplace-specific in practice. The same physical product can carry a different ASIN on Amazon's US, UK, or India storefronts, so an ASIN that resolves cleanly on amazon.com may not exist on another marketplace.

• •Product URL: the value after /dp/ or /gp/product/
• •The Product Information block on the detail page
• •Seller Central > Manage Inventory, shown per offer
• •Business Reports and the Amazon SP-API, keyed by ASIN
• •Catalog lookup tools that resolve ASIN from a UPC, EAN, or SKU

How ASINs get created, and how parent and child ASINs work

There are only two ways to attach yourself to an ASIN. You either match an existing one or you create a new one. Matching happens when you list a product and supply its UPC, EAN, or ISBN: Amazon checks the catalog, finds the existing entry, and adds your offer to that ASIN. Creating happens when the product genuinely doesn't exist in the catalog yet, typically for private label goods. You submit the product data (with a GTIN, or a GTIN exemption for brands that don't use barcodes), and Amazon mints a brand new ASIN for the listing.

Products with variations add one more layer: the parent-child structure. A t-shirt that comes in four sizes and three colors doesn't get one ASIN, it gets thirteen. Twelve child ASINs, one for each buyable size-and-color combination, plus one parent ASIN that acts as a non-buyable container tying the family together on a single detail page. Shoppers see one page with dropdown selectors. Your reports see twelve distinct children.

This structure has real reporting consequences. Sales, inventory, and fee data land at the child ASIN level, because that's what customers actually buy. Some advertising and traffic reports roll up to the parent. If you compare an ad report keyed to parents against a sales report keyed to children without translating between them, the numbers won't reconcile and it will look like data is missing. It isn't. It's just sitting at a different level of the hierarchy.

ASIN vs SKU vs FNSKU

These three identifiers describe three different things, and conflating them is the single most common source of inventory and bookkeeping errors for new sellers. The ASIN identifies the public catalog listing. The SKU is your private, seller-chosen label for the offer you list against that ASIN. The FNSKU is the barcode Amazon puts on each physical unit so it can track your specific goods inside its fulfillment network.

For accounting, the practical takeaway is that you reconcile and value inventory at the SKU level, because that's the grain at which you actually know your unit cost. The ASIN is the bridge to marketplace context: sales velocity, competing offers, and the Featured Offer (Buy Box). Tying your COGS and landed cost to SKUs, then rolling those up to ASINs, gives you both clean books and product-level profitability.

The relationship is many-to-one in both directions, which is where it gets slippery. One ASIN can have many SKUs attached to it (yours and every competitor's, and even several of your own if you list the same product twice at different costs). And one of your SKUs maps to exactly one ASIN at a time, but Amazon can merge or reassign ASINs during catalog cleanups, so the mapping isn't guaranteed to be stable forever. Keep a dated SKU-to-ASIN map somewhere outside Seller Central. When a merge happens, that map is how you stitch your historical sales back together.

A worked example: one ASIN, three SKUs, two different costs

Say you sell a stainless steel water bottle under your own brand. The listing carries one ASIN, call it B0EXAMPLE1. In January you imported 500 units at a landed cost of $6.10 each and listed them under the SKU BOTTLE-500-JAN. In April your supplier raised prices and your second batch of 500 units landed at $6.85, which you received under a fresh SKU, BOTTLE-500-APR. You also sell a two-pack as its own child ASIN under the SKU BOTTLE-2PK. All hypothetical numbers, but the structure is exactly what a real catalog looks like.

Now a customer buys one bottle for $24.99. Amazon's order report shows the sale against whichever SKU fulfilled it. If it shipped from the January batch, your cost of goods sold for that order is $6.10. If it came from the April batch, it's $6.85. Same ASIN, same detail page, same sale price, different margin. A seller who tracks cost "per ASIN" with a single blended number would book the wrong COGS on every single order from one of those batches, and the error compounds silently as prices drift over time.

Roll it up the other way and the ASIN earns its keep. When you want to know whether the water bottle line is worth reordering, you sum both SKUs' revenue, fees, and COGS under B0EXAMPLE1 and look at the blended margin and velocity. Cost lives at the SKU. Profitability questions get answered at the ASIN. Keeping those two levels straight is 90% of what separates clean seller books from guesswork.

Where the ASIN fits in your bookkeeping

Here's the uncomfortable truth: your general ledger should barely know ASINs exist. Amazon pays you in settlements, each one a bundle of thousands of order, fee, refund, and adjustment lines. The clean pattern for amazon bookkeeping is to post each settlement to QuickBooks or Xero as a summarized journal entry (revenue, fees, refunds, and the net deposit) and keep the SKU-level and ASIN-level detail in a subledger built for it. Post every order line individually into your ledger and it becomes an unusable wall of transactions within a quarter.

The ASIN's real accounting job is dimensional. It's the grouping key that turns raw SKU data into product-line answers: which products are actually profitable after fees, which parent families deserve more inventory, which listings are quietly losing money on returns. That analysis lives in your amazon accounting software or a profitability tool, not in the chart of accounts. Purpose-built tools like A2X, Link My Books, and BeanHawk all follow this same summarized-journal pattern, and they differ mainly in how much SKU and ASIN detail they preserve underneath the journal.

If you're evaluating quickbooks for amazon sellers, know that QuickBooks on its own has no concept of an ASIN. It sees whatever you post to it. An amazon quickbooks integration is what maps settlement lines to your accounts and keeps the identifier detail out of the ledger while still making it queryable. The same logic applies to inventory: amazon inventory management software should carry per-SKU unit costs and quantities, then let you view them grouped by ASIN, not force you to blend costs at the listing level. Ask any tool you're comparing one question: when Amazon merges two ASINs, what happens to my history? The answer tells you a lot.

Common ASIN mistakes that cost sellers money

Most ASIN problems aren't exotic. They're the same handful of mix-ups, made at scale, discovered months later when the books won't reconcile or a profit report looks impossible. These are the ones worth actively checking for.

• •Booking COGS at the ASIN level when multiple SKUs with different unit costs feed the same listing, which silently misstates margin on every order
• •Creating a duplicate ASIN for a product that already exists in the catalog, splitting your sales history and reviews across two pages (and risking policy trouble)
• •Assuming the same ASIN exists on every Amazon marketplace, then failing to reconcile UK or EU sales because the identifier doesn't match your US map
• •Confusing parent and child ASINs in reporting, so ad spend (often at the parent) never lines up with sales (always at the child)
• •Ignoring Amazon-initiated ASIN merges, which orphan your historical data unless you keep your own dated SKU-to-ASIN mapping
• •Treating the ASIN as a unit identifier when disputing FBA lost or damaged inventory, when Amazon's warehouse actually tracks your goods by FNSKU

Frequently asked questions

What is an ASIN number on Amazon?

An ASIN number is Amazon's 10-character Standard Identification Number for a product listing. It identifies a single catalog page that all sellers of that product share. It is not your personal SKU and not the FNSKU barcode on your physical units.

What does ASIN stand for?

ASIN stands for Amazon Standard Identification Number. Amazon assigns it automatically when a product is first added to the catalog, and it stays with that listing permanently.

How do I find an ASIN?

The quickest way is to read it from the product URL, where it appears right after /dp/ or /gp/product/. You can also find it in the Product Information section of the listing, or in Seller Central under Manage Inventory next to each offer.

Is the ASIN the same as a UPC?

No. A UPC is a universal barcode standard used across all of retail, while the ASIN is internal to Amazon. When you list a product, Amazon often matches your UPC to an existing ASIN, but the two codes are not interchangeable.

What's the difference between an ASIN and a SKU?

The difference between ASIN and SKU is ownership and scope. Amazon owns the ASIN and it describes a catalog page every seller of that product shares. You own the SKU and it describes your offer, your units, and your cost. For your books that split is the whole ballgame: cost of goods sold belongs on the SKU, because that's where you know what you paid, while the ASIN is the grouping key you report by.

What is the difference between an ASIN and an FNSKU?

An ASIN identifies the listing; an FNSKU identifies your physical units. The difference between ASIN and FNSKU shows up the moment something goes wrong in a fulfillment center, because Amazon's warehouse doesn't reconcile by ASIN. It scans the FNSKU barcode on the box. File a lost-inventory claim quoting an ASIN and you're describing a product page, not the specific units Amazon received from you, which is why those cases stall.

Can the same product have different ASINs?

Yes, in two situations: the same product can carry different ASINs across Amazon marketplaces (US vs UK vs India), and duplicate listings can occur when a product gets created more than once in the catalog. Merging duplicate ASINs keeps your sales and reviews consolidated.

What is a parent ASIN vs a child ASIN?

A parent ASIN is a non-buyable container that groups product variations (sizes, colors) onto one detail page. Each buyable variation is a child ASIN with its own inventory, sales, and fee data. Sales always land at the child level, while some ad and traffic reports roll up to the parent, so translate between levels before comparing reports.

Does QuickBooks track ASINs?

Not natively. QuickBooks has no built-in concept of Amazon identifiers, which is why sellers pair it with an amazon quickbooks integration that posts summarized settlement journals to the ledger and keeps SKU and ASIN detail in a separate layer. Trying to recreate ASIN-level tracking inside QuickBooks items gets unmanageable fast.

What should accounting software for amazon sellers do with ASINs?

Three things: keep unit costs at the SKU level where they're actually known, let you group and report by ASIN for product profitability, and survive Amazon's ASIN merges without losing history. Compare tools like A2X, Link My Books, and BeanHawk on exactly those points, plus how they summarize settlements into QuickBooks or Xero. A spreadsheet honestly works fine under about 20 SKUs; past that, manual mapping starts breaking.

Related terms

Go deeper

• FNSKU vs ASIN vs SKU: Amazon Barcode Labels Explained
• What Is an ASIN Number? Amazon's Product ID, Explained