> Source: https://vitna.ai/docs/cli/skus/link > Raw Markdown: https://vitna.ai/docs/cli/skus/link.md > Corpus index: https://vitna.ai/llms.txt # npm run sku:link Close a candidate against a [sku](../../concepts/sku.md) the registry already holds. ```bash npm run sku:link -- <id> --sku <sku id> [--note "..."] ``` For a product registered by hand in `platform/witness/seed-data.mjs`, which is how a batch of joins lands with its adapter rows and fixtures. The registry already holds the slug, so [promotion](promote.md) refuses the candidate, and [rejection](reject.md) would record a product Vitna tracks as one it decided not to. Without a link the row stays pending and counts on /witness as work nobody has done. ## What it refuses - A candidate that is not pending. A ruling is not made twice. - A sku sold by a different provider from the page the row was read on, however alike the names are. - A candidate whose page has not been read successfully since the row was last counted. Every good read counts every row the adapter does not claim, so a later read that did not count it is the evidence that the registered sku now covers the row. Before that read, the next one could count it again. No event is written. The sku was registered by the change that added it, and a link records only that a queue row and a registry row are the same product. The note defaults to naming the sku, and `--note` replaces it.