Solutions e-commerce
Cette page pilier centralise les workflows codes-barres marketplace, y compris les étiquettes de préparation Amazon FBA, les exigences Noon FBN et les opérations SKU multi-boutiques.
Multi-channel sellers rarely need one barcode format twice: Amazon expects FNSKU or UPC/EAN depending on brand registry status, Noon and other GCC marketplaces have their own compliance rules, and your own warehouse may run Code128 SKUs internally. Instead of relearning a different generator for each channel, upload one product CSV or Excel sheet and export every format your listings need — EAN-13, UPC-A, Code128 or QR — as print-ready PDF sheets or a ZIP of images.
- Bulk-generate from the same product spreadsheet you already export from Shopify, Amazon Seller Central or your ERP
- Match each marketplace's label spec (FNSKU, UPC-A, EAN-13) without switching tools
- Export thermal-printer-ready PDFs or a ZIP of individual images for warehouse packing stations
UPC vs ASIN vs FNSKU: what do you actually need to print?
If you're new to the Amazon ecosystem, the acronyms alone can cause mislabeled inventory and costly inbound errors. Here's what each one is for:
UPC / EAN
The manufacturer's global barcode, used to initially list the product on Amazon. Don't use this for FBA carton labeling unless you're specifically enrolled in Amazon's manufacturer-barcode tracking, which carries its own co-mingled-inventory tradeoffs.
ASIN
Amazon's 10-character catalog identifier for the digital listing itself (starts with B0). This is not something you print on a physical label.
FNSKU
Fulfillment Network SKU — unique to your seller account. This is the barcode you actually generate and apply to inbound FBA units, encoded as Code 128.
Workflow inside this tool
- Export from Seller Central. From your Amazon inventory or shipment plan, download a CSV or XLSX with your FNSKU and quantity columns included.
- Upload and map columns in the workspace. Set the symbology to Code 128 (Amazon's requirement for FNSKU), map the barcode-value column to your FNSKU field, and point the quantity column at how many copies of each label to print.
- Export a print-ready PDF roll sized for your thermal printer, or a ZIP of individual label images if you're handing labels to a packer or print shop.
Formatting details that matter for inbound acceptance
- Amazon expects the product title and condition printed above the barcode, not just the code itself — the generator places this automatically so it doesn't overlap the barcode's quiet zone.
- Code 128 needs blank space ("quiet zone") on either side of the bars to scan reliably; this is calculated automatically rather than left to manual margins.
- If you also sell wholesale or in physical retail alongside Amazon, the same workspace switches to EAN-13 or UPC-A for those channels without a separate tool.
FAQ
What barcode format does an Amazon FNSKU use?
Code 128 — FNSKUs are alphanumeric, and Code 128 is the symbology that encodes letters and numbers together reliably at warehouse scan volume.
Can I generate FNSKU labels without Amazon's own label service?
Yes. Export your FNSKU list from Seller Central, upload it here, and generate a batch of thermal-ready labels directly, rather than using Amazon's per-label prep flow.
Does printing my own FNSKU labels cost less than Amazon's prep service?
Amazon charges a per-unit prep fee for applying barcodes on your behalf; printing them yourself in bulk avoids that fee entirely, though you take on the printer hardware and label stock cost.
Noon (Fulfilled by Noon / FBN): printing Partner SKU labels in bulk
Noon sellers using FBN (Fulfilled by Noon) hit a different labeling problem than Amazon FBA sellers: your product identifier is a Partner SKU you assign yourself in Noon Seller Lab, not a barcode Noon issues for you. The workflow below matches what Noon's own barcode-requirements guidance describes.
Workflow inside this tool
- List and export from Seller Lab. List your products in Noon Seller Lab and generate your Partner SKUs there, then export an Excel (.xlsx) file that includes the Partner SKU, product title, and the quantity you're shipping.
- Upload and map columns in the workspace. Code 128 is generally the right symbology for alphanumeric Partner SKU values; use EAN or UPC instead if your listing already carries one of those identifiers.
- Export a print-ready PDF roll sized for your thermal printer, then book your Advance Shipping Notice (ASN) appointment and deliver to Noon's warehouse for scanning.
FAQ
What barcode format should I use for Noon Partner SKU labels?
Code 128 is usually preferred for alphanumeric Partner SKU values, while EAN or UPC can be used when your product identifiers already require them.
How do I print Noon Partner SKUs in bulk?
Export your Partner SKUs from Noon Seller Lab into an Excel sheet alongside the quantity to ship, upload the file here, select Code-128, and export a continuous PDF roll sized for your thermal printer.