What Is a SKU? SKU vs UPC, ASIN, and FNSKU

A SKU (stock keeping unit) is the internal code a seller creates to identify one specific product variant so it can be tracked through inventory, orders, and fulfillment. If you are asking what is a SKU, the short answer is that it is your own private label for a sellable item, controlled entirely by you, unlike a UPC, ASIN, or FNSKU, which are assigned by outside parties. A red medium t-shirt and a blue medium t-shirt are two separate SKUs, even though a shopper sees one product with color options.

Key takeaways

• A SKU is a seller-defined internal identifier for one exact product variant, including size, color, and pack quantity.
• A UPC is a standardized barcode issued through GS1, an ASIN is Amazon's catalog ID, and an FNSKU is Amazon's label for your specific FBA units. You assign the SKU; the others come from outside.
• Every sellable variant needs its own unique SKU, and no SKU should ever point to two different products.
• A consistent, human-readable SKU structure keeps inventory counts, picking, and 3PL handoffs accurate as your catalog grows.

What is a SKU and what is it for?

A SKU is a stock keeping unit: a code you assign to track one sellable item across every place it appears in your business. It ties together how much stock you have, where that stock sits, how fast it sells, and what it costs. Because the SKU is yours, you decide its format and meaning. A well-built SKU can encode the product line, size, color, and pack count so a person can read it without a lookup, while your software treats it as the primary key that links your storefront, your accounting, and your warehouse or warehouse management system.

The practical test is granularity. If two items differ in any way a customer chooses or a picker must distinguish, they are different SKUs. That includes case packs: a single unit and a 6-pack of the same product are separate SKUs because they occupy different shelf locations and sell at different prices.

How is a SKU different from a UPC, ASIN, and FNSKU?

The difference comes down to who controls the code and where it is used. A SKU is internal and seller-owned. A UPC is a universal barcode number shared across the whole retail supply chain. An ASIN and an FNSKU are both Amazon identifiers, but they do different jobs: the ASIN names the listing, while the FNSKU names your physical units inside Amazon's fulfillment centers.

One product can carry all four at once. Say you sell a stainless water bottle: you assign it a SKU, you buy a UPC through GS1 to list it, Amazon generates an ASIN for the listing, and if you send units into FBA you print an FNSKU label so those bottles are credited to your account rather than commingled with another seller's stock. The FNSKU is what physically goes on the unit during prep; our guide to FNSKU labeling covers when Amazon requires it and how the label is applied.

Who assigns each identifier?

You create SKUs yourself, for free, in whatever structure you like. UPCs come from GS1, the standards body that licenses each brand a company prefix so barcodes stay globally unique. ASINs and FNSKUs are both generated by Amazon, the first when a listing is created and the second when you set up a product for FBA. The distinction matters because you can change a SKU whenever you want, but you cannot rename a UPC or ASIN once it is in the wider system. Treat the outside identifiers as fixed references and let your SKU be the flexible internal key that maps to them.

What makes a good SKU structure?

A good SKU is short, consistent, and readable, built from segments that describe the product from general to specific. A common pattern is category, then product line, then variant attributes, separated by hyphens. The goal is that a warehouse associate or a founder can glance at a SKU and know roughly what it is without opening a database.

• Use uppercase letters, numbers, and hyphens only. Avoid spaces, slashes, and characters that look alike, such as the letter O and zero, or the letter I and one.
• Keep segments in a fixed order and a fixed length so SKUs sort cleanly and stay scannable, commonly 8 to 16 characters total.
• Do not start a SKU with meaning that changes, such as a supplier's name, and never embed a price. Prices change; SKUs should not.
• Reserve a segment for pack size so a single and a case never collide.

Can you walk through a worked example?

Suppose you sell bamboo cutting boards in two sizes and two finishes. Start with a line code, add size, then finish: BAM-CB-LG-NAT is a large natural board, BAM-CB-LG-DRK is the large dark board, and BAM-CB-SM-NAT is the small natural one. Add a 2-pack of the large natural board and it becomes BAM-CB-LG-NAT-2PK, a distinct SKU with its own count and location. Four variants plus one bundle gives five SKUs, each mapping to its own UPC and, if you use FBA, its own FNSKU. The structure reads the same for every future product, so onboarding a new line means filling in the same slots rather than inventing a scheme from scratch.

Why do clean SKUs matter for inventory and fulfillment accuracy?

Clean SKUs are what keep your on-hand counts honest and your orders shipping the right item. Every downstream process keys off the SKU: reorder points, cycle counts, and the scan a picker makes when they pull a unit. If two products share a SKU, or one product carries two, the math never reconciles and you get oversells, backorders, and returns. When a pick and pack operation or a third-party warehouse handles your goods, the SKU is the only language you share, so an ambiguous or duplicated code turns into a miship on their floor. This is also why 3PLs ask for a clean SKU list before onboarding: they map your codes to their storage locations, and messy inputs slow the whole handoff. The SBA's guidance on managing a business treats accurate inventory tracking as a core control, and the SKU is the unit that tracking is built on.

One more distinction worth keeping straight: SKUs are internal and are not the codes customs uses. If you import, your products are also classified under HTS numbers, and CBP works from those, not your SKU. Keep the two mapped but separate.

How do SKUs fit into choosing a fulfillment partner?

When you compare 3PLs or prep centers, ask how they ingest your SKUs, whether they support your case-pack and bundle codes, and how they reconcile counts back to you. A provider that maps cleanly to your SKU structure will have fewer miships and faster onboarding. You can browse neutral options in the ecommerce fulfillment directory or run the numbers first with the FBA prep cost estimator. Whatever partner you pick, keep the SKU as your single source of truth: it is the one identifier you own, and it is the thread that ties the UPC, ASIN, and FNSKU together into a product you can actually count and ship.