You send in 500 units. Amazon receives them, scans the barcode, and can’t match them to your listing. Now those units are in a black hole \u2014 stranded inventory, a support ticket you’ll spend three weeks on, and possibly a removal order you paid for. This happens because a seller used a UPC where Amazon required an FNSKU. We see it at our receiving dock more than you’d think, and it’s almost always preventable.<\/p>\n
The question of FNSKU vs. UPC labels on Amazon isn’t just a technicality. It determines whether your inventory gets received correctly, whether Amazon can track it back to your seller account, and whether you get hit with unplanned prep fees. Let’s break down exactly what each label does, when you need which, and where sellers get it wrong.<\/p>\n
A UPC (Universal Product Code) is a manufacturer barcode. It identifies the product \u2014 not who’s selling it. If you, your competitor, and a wholesale distributor all sell the same widget, you all share that UPC. It’s a product identifier, not a seller identifier.<\/p>\n
An FNSKU (Fulfillment Network Stock Keeping Unit) is Amazon-generated and specific to your seller account and your listing. Amazon assigns it when you create an FBA listing. It ties that unit to you \u2014 your ASIN, your account, your inventory pool.<\/p>\n
That distinction matters a lot inside a fulfillment center. When Amazon’s scanner reads a UPC, it sees a product. When it reads an FNSKU, it sees your product. In a commingled inventory situation, those are two very different things.<\/p>\n
Amazon built FNSKU labeling specifically for FBA accountability. With millions of sellers sending in millions of units, they needed a way to credit inventory to the right account at receiving. The FNSKU is how they do it. Without it, the warehouse can’t reliably attribute your units to your account when multiple sellers stock the same item.<\/p>\n
Here’s the rule that trips people up: Amazon requires FNSKU labels on every unit going into FBA unless the product is enrolled in the Commingled Inventory program (also called Stickerless, Commingled Inventory). That program lets Amazon pool your units with identical units from other sellers \u2014 and use the UPC alone for tracking.<\/p>\n
Most experienced sellers opt out of commingling. Here’s why.<\/p>\n
So in practice, the answer for most FBA sellers is: FNSKU labels on every unit, every time. The UPC is still on the product packaging underneath. Amazon just wants your FNSKU covering it or placed where the scanner reads it first.<\/p>\n
Amazon mandates FNSKU labeling (no commingling option) for certain categories: media products, consumables with expiration dates in some cases, and items flagged as high-risk for authenticity. Check your category-specific requirements in Seller Central \u2014 they change, and the consequences of getting it wrong are expensive.<\/p>\n
Amazon will either reject the shipment at receiving or \u2014 and this is the costly one \u2014 apply the label themselves and charge you an unplanned prep fee. As of the current Amazon fee schedule, that unplanned labeling fee is $0.30 per unit<\/strong> on top of whatever standard prep fees apply. Send in 1,000 units with the wrong label, and you’re looking at a $300 surprise charge before your inventory even hits a shelf.<\/p>\n According to Amazon’s own FBA policies, sellers are responsible for ensuring units are properly labeled before shipping to a fulfillment center. If Amazon has to do it, you pay \u2014 and you don’t get to negotiate the rate.<\/p>\n We’ve had clients come to us after exactly this situation. One seller sent 800 units of a private label product without FNSKU labels because they copied a shipment workflow from an older account. Amazon labeled them all. The bill was $240 plus delayed availability during peak Q4 inventory windows. That delay alone cost more in lost sales than the labeling fee.<\/p>\n Finding your FNSKU is straightforward. In Seller Central, go to Manage Inventory, pull up the SKU, and look under the product details. Or go directly to your FBA shipment workflow \u2014 Amazon displays the FNSKU during the label generation step and lets you print label sheets in standard formats (30-up Avery sheets are common).<\/p>\n The label has to be scannable. That sounds obvious, but here’s where sellers get sloppy:<\/p>\n At our prep facility, we use thermal label printers with 4×6 or 2×1 stock depending on the product type. The print quality matters \u2014 a partially printed FNSKU will fail scanner reads at the fulfillment center, and you’re back to unplanned prep territory.<\/p>\n If your supplier prints a UPC directly on the packaging (common with private label manufacturers in China), you have two options: have your supplier switch the barcode on the packaging to the FNSKU (more expensive, requires a packaging revision), or cover the UPC with your FNSKU label at the prep stage. Most sellers do the latter. It’s cheaper and faster, and it’s exactly the kind of work our FBA prep service<\/a> handles at volume every week.<\/p>\n Let’s say you sell a non-private label product \u2014 something you source from a distributor that’s also sold by 12 other sellers on the same ASIN. You’re tempted to skip the labeling step and let your units commingle. Here’s the math to run first.<\/p>\n Commingling saves you the cost of FNSKU labeling \u2014 roughly $0.10\u2013$0.20 per unit at a prep center depending on volume and product type. But if one bad unit from another seller’s pool gets attributed to your account through a customer complaint or return, you’re looking at a potential A-to-Z claim, negative review removal costs, and in worst cases, account health metrics that affect your selling privileges.<\/p>\n Honestly, most sellers shouldn’t commingle unless they have complete confidence in every other seller on that ASIN \u2014 which is almost never knowable. The labeling cost is cheap insurance.<\/p>\n Amazon’s FBA Label Service \u2014 where they apply FNSKU labels on your behalf as a planned service \u2014 costs $0.55 per unit<\/strong> as of recent fee schedules. That’s a planned, requested service through your shipment workflow. If you use it intentionally, fine. But if you’re paying $0.55\/unit because you forgot to label and it became unplanned, that’s a problem at any volume above a few hundred units. At 365PrepCenter, we label FBA units for a fraction of that cost, which is why sellers who ship through us don’t usually see those fees.<\/p>\n Private label sellers generally have clean FNSKU workflows because they’re creating the product and the listing. Wholesale and RA sellers hit more friction. Here’s why.<\/p>\n When you’re sourcing retail arbitrage product, the item has a manufacturer UPC on it. You list it on an existing ASIN. Now you need to apply an FNSKU label for FBA \u2014 but you didn’t make the product, you’re not changing the packaging, and you might be processing 50 different SKUs from a single Target run. That’s a labeling operation, not just a prep step.<\/p>\n Each ASIN gets its own FNSKU. You can’t batch one label across multiple SKUs. And if you’re commingling multiple ASINs into one shipment without organized FNSKU labeling, the receiving errors compound fast.<\/p>\n RA and wholesale sellers are the ones who most benefit from outsourcing labeling to a prep center \u2014 specifically because of the SKU variability. Our FBA prep process<\/a> is built around exactly this kind of mixed-SKU inbound workflow, and we handle the FNSKU matching so you don’t have to track it unit by unit yourself.<\/p>\n If you’re selling on multiple marketplaces \u2014 Amazon.com and Amazon.ca, for example \u2014 the FNSKU is different per marketplace. The same product listing on Amazon Canada gets a different FNSKU than on Amazon US. Sellers who prep for multi-marketplace fulfillment need to keep those label runs separate. Mixing them creates receiving errors in whichever country gets the wrong labels.<\/p>\n Here’s how the two labels stack up in practical terms:<\/p>\n The decision tree is actually simple: if you’re shipping FBA and you’re not enrolled in commingled inventory, every unit needs an FNSKU label before it hits the fulfillment center. Everything else is just execution.<\/p>\n If you’re spending time at a packing table printing and applying FNSKU labels yourself instead of prepping your next product or working on your catalog, that’s probably not the best use of your hours. 365PrepCenter in Lebanon, Ohio handles inbound FBA prep \u2014 including FNSKU labeling at scale \u2014 so you can send product directly from your supplier without touching it. Get a free quote<\/a> and see what it costs to hand off the label work entirely.<\/p>\n","protected":false},"excerpt":{"rendered":" FNSKU vs. UPC Labels: The Complete Amazon Seller Guide You send in 500 units. Amazon receives them, scans the barcode, and can’t match them to your listing. Now those units are in a black hole \u2014 stranded inventory, a support ticket you’ll spend three weeks on, and possibly a removal order you paid for. This … Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":280,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-281","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized-en"],"_links":{"self":[{"href":"https:\/\/365prepcenter.com\/blog\/wp-json\/wp\/v2\/posts\/281","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/365prepcenter.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/365prepcenter.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/365prepcenter.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/365prepcenter.com\/blog\/wp-json\/wp\/v2\/comments?post=281"}],"version-history":[{"count":0,"href":"https:\/\/365prepcenter.com\/blog\/wp-json\/wp\/v2\/posts\/281\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/365prepcenter.com\/blog\/wp-json\/wp\/v2\/media\/280"}],"wp:attachment":[{"href":"https:\/\/365prepcenter.com\/blog\/wp-json\/wp\/v2\/media?parent=281"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/365prepcenter.com\/blog\/wp-json\/wp\/v2\/categories?post=281"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/365prepcenter.com\/blog\/wp-json\/wp\/v2\/tags?post=281"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nHow to get your FNSKU labels and apply them correctly<\/h2>\n
Label placement rules that matter<\/h3>\n
\n
What about manufacturer barcodes on the product itself?<\/h3>\n
\nFNSKU vs. UPC labels on Amazon: the commingling calculation sellers skip<\/h2>\n
One more number to keep in mind<\/h3>\n
\nWholesale and retail arbitrage sellers: you have a different problem<\/h2>\n
One situation that confuses even experienced sellers<\/h3>\n
\nQuick reference: FNSKU vs. UPC labels on Amazon<\/h2>\n
\n