Printing less than Amazon desires means increasing the chances of errors.
Among the best practices is to never increase the chances that Billy in the FC will screw up. You will discover Billy does not need any extra help to do that.
This is an interesting thread - my labels just have the barcode, FNSKU and partial title - and the titles are old.
I have the FNSKU labels stored in folders and print them from there, and most of my titles have changed over time so they aren’t current. So far, no issues.
We do this. It has to be precisely what you see when you print them manually. All the text must be there, including the condition.
!!!HERE’S THE IMPORTANT PART!!!
It must be the same exact size as the 30 up label (min).
Even more important
That part of the label must have no finish on it at all. No UV coating, No gloss coating, NOTHING.
We have run into so many “Shipment Problem” fines because we didn’t do it the right way first. Well we did, but Amazon changed their belt scanners to visual from laser and it can’t handle a standard CPG label finish.
You do it the way I mentioned above and you will have no issues at all and save a lot of time and labor.
We’ve been OK since we changed it all up and had custom printer plates made that exclude that area from having the standard label finish / UV coating. Also had out printer move from semi-gloss to flat stock.
Amazon makes everything as difficult as possible and changes the rules / equipment on the fly.
We used to hand apply our FNSKU’s and lots of time they were smudged. Never had a single issue. When we had them professionally printed and then Amazon changed their scanners, we had lots of problem / cost / heartache / aggravation.
The UK version of that MWS dev page hasn’t greatly deviated from the US version (@ least not to my knowledge) since I first archived both back in 2015 - but I would submit that it could at any time (mayhaps especially-so as the ever-looming* deprecation of the MWS API in favor of the SP-API once again reaches the cut-off date displayed on that and many another documentation webpage); as such, I would recommend bookmarking the .com-specific v. @ (‘broken’ URL: https: //docs.developer.amazonservices.com/en_US/fba_guide/FBAGuide_ItemLabelSpec.html) :
This deprecation has continuously been put off @ least a dozen times since 2020, largely on the score of legacy-application compatibility -so it will not surprise me to learn that 31Mar24 isn’t the final revision in that regard…