Getting your FBA labels right so you stop paying $0.50 per sticker for re-labeling
Most people treating this like it is a simple printing task is why their inventory gets stranded at fulfillment centers. The process involves generating FNSKU labels from Seller Central and getting them onto 1x3 inch thermal paper without creating edge-cutting errors, barcode defects, or misalignment that makes scanners reject the label. It sounds trivial. It is not, mostly because the tools Amazon expects you to use are adequate at best and actively hostile at worst if you have more than fifty ASINs to handle in a single shipment. The workflow most experienced sellers end up using goes like this. You generate the labels from Amazon's shipment creation page, download the PDF, and then run it through a script or template that maps the labels onto your actual sticker roll dimensions. Third-party tools like FBA Label Assistant or ShipStation can bridge the gap between Amazon's output format and whatever paper width you are actually feeding into your Zebra or Rollo printer. The reason this matters is that Amazon's native PDF generator assumes US Letter paper and a standard label layout, which rarely matches the reality of buying roll labels in bulk from suppliers who might be selling 1x3 inch but on a roll that sits differently on your printer tray. I spent about three weeks dealing with a specific problem where every single label in my batch was being rejected at receiving. The SKUs were fine, the barcodes scanned correctly when I tested them with a handheld gun, but the FC workers kept flagging them. Turns out the issue was that my printer was outputting at 98 percent of the intended label height due to a driver scaling setting in Windows, and the bottom quarter millimeter of each barcode was slightly compressed. Scanners read it fine in my warehouse but the conveyor belt scanners at the fulfillment center run at a different DPI threshold and they flagged it. The workaround was straightforward once I found it: I turned off "Fit to Page" in the Zebra driver and set the custom media size manually to exactly 1 inch by 3 inches, then exported the labels from Amazon and printed them at 100 percent scale with no margins. After that, rejection rate dropped to zero across five consecutive shipments totaling about four hundred units.
Here is something the beginner guides do not tell you, which I learned the hard way before figuring it out. The order in which you generate and print labels matters more than people realize. If you generate a fresh batch of labels and then use an older saved PDF from a previous day, you can end up with duplicate FNSKU codes on different items, or worse, items from the same SKU having two different FNSKU codes because Amazon rotated the identifier between batches. This happened to me with a batch of twelve hundred units across six ASINs. The fix was to generate and print labels in the same session, close the browser tab immediately after downloading, and never reuse a PDF older than twenty-four hours. Save the PDFs by shipment ID, not by date, and check the FNSKU string on the file itself before you start printing anything. Another thing nobody talks about is printer calibration. Thermal printers drift. The print head temperature changes throughout the day, especially in a warehouse that is not climate controlled, and this causes the barcode contrast to degrade in ways that look fine to your eyes but fail at scanning distance. I keep a test strip printed every morning and hold it up to my scanner gun at arm's length before running any full batch. If the beep is anything less than immediate, I run a head cleaning and adjust the darkness setting by two or three points. It takes about forty seconds and it has saved me from two separate shipment rejects already this year. The biggest bottleneck most people hit is dealing with mixed-quantity shipments where some items need barcodes and some need box labels, and doing it all from the Amazon interface in one sitting. My recommendation is to split this into two phases. Phase one, generate and print all the individual item FNSKU labels for the entire shipment before you even open the box labeling screen. Phase two, print the box labels and apply them after the items are packed. Trying to do it sequentially as Amazon's UI forces you to is where the errors creep in, mostly because you lose your place on which SKU you were just working on and start applying the wrong label set.
If you are only doing one or two shipments a month, the Amazon native workflow will work fine. You will waste about twenty minutes per shipment on setup and printer issues, which adds up if you are doing weekly volume. For anyone moving more than that, the time investment in getting a proper label template set up and a test-print routine going will pay for itself in the first two shipments alone. Not doing it just means you are betting your inventory flow on a system that was not designed for high-volume operations and shows it whenever you push past the basics. I keep a single Google Sheet open while I work that tracks the shipment ID, the number of labels generated, the printer darkness setting used, and whether the test strip passed. It is overkill if you are shipping fifty units a month. It is the difference between a smooth receiving day and spending your Tuesday on the phone with seller support when things go sideways on a thousand-unit shipment.
Get the Full Details
