From the sourcing desk
FBA Labeling: Approve the Barcode-to-SKU Crosswalk
A six-column crosswalk (STS SKU, seller SKU, ASIN, FNSKU, pack count, artwork version) with scan and sign-off gates before you approve FBA labeling.
Approve a six-column crosswalk — STS SKU, seller SKU, ASIN, buyer-supplied FNSKU, pack count and artwork version — and freeze it with two gates: a scan gate (every printed label scans back to the exact row) and a sign-off gate (one named approver initials the version). This is the toy FNSKU labeling checklist that prevents the wrong label landing on the wrong unit.
The reason it matters: an FNSKU is the FBA product label code, only FBA products have one, and one FBA product SKU maps to one FNSKU. Get the crosswalk right and labeling is mechanical. Get it wrong and you rework cartons at your own cost.
What each of the six columns actually controls
Each column exists to stop a specific failure. STS SKU is your internal sourcing reference — the number you quote to a supplier. Seller SKU is what your Amazon seller account recognizes. ASIN is the catalog identity. FNSKU is the buyer-supplied label code. Pack count is how many sellable units sit in one carton. Artwork version is which print file the factory is running.
Keep them in one row per sellable unit. A row that mixes a pack count from one revision with an artwork version from another is the classic source of mislabeled cartons.
| STS SKU | Your internal sourcing reference; ties the row to a quoted supplier item |
|---|---|
| Seller SKU | The identifier your seller account uses for the listing |
| ASIN | Catalog identity; buyer-supplied, never invented |
| FNSKU | FBA product label code; buyer-supplied, one per FBA product SKU |
| Pack count | Sellable units per carton; drives label quantity and carton math |
| Artwork version | The print file revision the factory is running |
Manufacturer Barcode vs Amazon Barcode: which one your crosswalk assumes
| FNSKU equals ASIN | Manufacturer Barcode selected; no FNSKU label needed; goods commingled with other sellers' same-ASIN stock |
|---|---|
| FNSKU differs from ASIN | Amazon Barcode selected; all FNSKUs unique; Amazon will not commingle the seller's goods |
| What this means for your crosswalk | If the FNSKU column is blank or mirrors the ASIN, confirm the barcode preference before you print anything |
Why an approved crosswalk can still go stale
The same SKU's FNSKU may be adjusted because of product performance or platform policy — for example, when mixed inventory support ends and an X-prefixed label becomes required. That is one reason two FBA SKUs from the same seller can end up on one product page.
Treat the crosswalk as a versioned document, not a one-time file. Date it, and re-verify the FNSKU column each time you create a new shipment rather than trusting last quarter's sheet.
The two gates: scan, then sign off
Scan gate. Before cartons leave, scan a printed label from each artwork version and confirm it resolves to the correct row. If a label scans to the wrong row, stop the run — do not 'fix it later' at the fulfillment center.
Sign-off gate. One named approver initials the crosswalk version and the date. That single signature is what lets you trace a mislabel back to a revision instead of a person's memory.
A worked example (illustrative numbers only)
The figures below are illustrative and exist only to show the arithmetic — they are not quotes, fees or lead times.
Say a crosswalk row carries a pack count of 24 units per carton and the shipment is 5 cartons. That is 120 sellable units, so you need 120 FNSKU labels for that row, plus spares for damaged or re-applied labels. If the artwork version on that row is superseded mid-run, the row is void and must be re-approved before more labels are printed.
| Pack count (illustrative) | 24 units per carton |
|---|---|
| Cartons (illustrative) | 5 |
| Labels required (illustrative) | 120, plus spares for re-application |
| Trigger to re-approve | Artwork version changes or the FNSKU column no longer matches the shipment |
Buyer questions on the FNSKU crosswalk
Do I need an FNSKU on every unit?
Only if the listing uses Amazon Barcode. When FNSKU equals the ASIN, the seller selected Manufacturer Barcode and no FNSKU label is required — but the goods are commingled with other sellers' same-ASIN inventory.
Can one seller SKU have more than one FNSKU?
One FBA product SKU maps to one FNSKU, but the same SKU's FNSKU may be adjusted due to product performance or platform policy — for example when mixed inventory support ends and an X-prefixed label becomes required.
How do I switch to labels I apply myself?
Disable the manufacturer barcode preference in your Amazon Logistics barcode settings. Previously uploaded B00 products can be re-followed, and when an X00-prefixed FNSKU appears you can proceed with the FBA shipment and print labels.
Is there a required label size?
Match the label to the product; there is no single size that fits every unit. Test a printed label on the actual packaging before committing a full run.
Sources
- FNSKU-跨境百科-跨境电商雨果网
- FNSKU-跨境百科-跨境电商雨果网
Next step
If you want the crosswalk built and checked alongside your packaging and shipment handover, our sourcing desk coordinates private-label packaging, sample and QC checks, and multi-supplier consolidation for Amazon and Shopify brands. Start by sending your current SKU list and artwork versions for a crosswalk review.