Skip to content

Glossary

FNSKU

The barcode a marketplace assigns to a product for its own fulfillment network. It is printed on the unit, it is not your SKU, and it comes back to your dock on every return.

What it is

When you send inventory into a marketplace’s fulfillment network, the marketplace often requires each unit to carry its own barcode instead of the manufacturer’s UPC. That barcode is the FNSKU. It ties the unit to your seller account and your listing, so the network can tell your units from another seller’s units of the same product.

The sticker goes on the unit. From then on, that unit answers to two names: your SKU, and the marketplace’s FNSKU.

Why it matters

The network does not keep your units forever. Removal orders send them back. Customers return them. Both arrive at your dock with the FNSKU sticker on top of, or instead of, the original barcode. If your warehouse system only recognizes your SKU barcode, the receiver scans the sticker, gets “unknown product”, and either types the SKU by hand or puts the unit aside. Either way the ledger is now wrong or late.

The fix is not to rename anything. It is to teach the system that this sticker means that SKU.

A worked example

ITEM-01 carries the UPC on its retail packaging. Two hundred units are labeled with FNSKU X0000AB1CD and shipped into the network. Months later, thirty come back on a removal order. The receiver scans X0000AB1CD. The system resolves it to ITEM-01, matches the expected line on the removal document, and the receive row is written against ITEM-01. The document, the ledger and every report say ITEM-01. The alias did its one job and disappeared.

How DockingWare does it

A product can hold any number of alternate barcodes, each unique across the whole catalog, with a named refusal if a code is already taken by another product. The alias resolves on every scan surface: receiving, putaway, picking, packing, returns and removals. It never renames; the ledger always carries the real SKU. Unit labels can be printed for the SKU itself or for each registered FNSKU, encoded byte for byte as stored, so a printed label always scans back to its product.

Questions

Is the FNSKU the same as the UPC?
No. The UPC identifies the product to the whole retail world. The FNSKU identifies your listing of that product inside one marketplace's network, and it can differ per seller for the same UPC.
Why does the FNSKU matter to my own warehouse?
Because relabeled units come back. Removals and customer returns arrive wearing the marketplace sticker, and a scanner that only knows your SKU barcode will not recognize your own product.
Should I rename my SKU to the FNSKU?
Never. Keep your SKU as the identity and register the FNSKU as an alias. Documents and the ledger should always name the real SKU; the alias is a door in, not a new name.

Related terms

See how DockingWare handles this →