Issuing codes

Minting the codes that will be printed on your goods.

Issuing codes for a product or asset

Prerequisites. A brand, a subject and an item must already exist.

1. Open the batch (or asset item) and select Issue Codes.
2. Choose the Code type — Public for anything a customer will scan.
3. Enter the Quantity: between 1 and 1000 codes.
4. Select Issue.

Expected result. The issuance is created instantly with that many unique codes, listed and ready to view, download or print.

The minted codes.

Tip · Issue per production run, not per year

Because archiving an issuance withdraws exactly the codes it contains, an issuance that matches one physical production run gives you the most precise recall control. For runs above 1000 units, create several issuances.

Common errors

Message	Resolution
Quantity must be between 1 and 1000	Split larger runs into several issuances.
Item and authcode type are required	Select both before submitting.
File subjects require uploaded files; products and assets require a quantity	You are issuing for a content item — upload files instead of entering a quantity (Issuing codes for content).
Object storage is not configured	A server-side setup problem. Contact your administrator — see Troubleshooting.

Issuing codes for content

1. Open the content item and select Issue Codes.
2. Choose the code type.
3. Select the files to certify — up to 1000 files at a time, each up to 8 MB.
4. Select Issue. The count of files is shown before you confirm.

Expected result. One certified code per file, each bound to that file’s fingerprint.

Working with individual codes

Open an issuance to see its codes. Each row offers:

Action	What it does
Copy code	Copies the code text to the clipboard.
QR code	Shows the QR image, with a download button for a single label.
Holdings	Shows which verifier currently holds the item, and since when.
Operations	Every scan and transfer recorded for this one code.
Settings	Code configuration, including ownership transfer for assets and contents.
Archive	Stops this single code verifying, without affecting the rest of the batch.

Every code has a downloadable QR image.

Tip · Investigating a customer complaint

Paste the disputed code into the global search, open it, and read its Operations. If it has been scanned in several distant places within days, the code has almost certainly been copied — archive that single code and issue a replacement for the genuine unit.

Transferring ownership of a code

Purpose. Hand an asset or a certified document to another AuthPlus account — for example when a valuable is sold to a collector who has their own account.

1. Open the code’s settings from the issuance list.
2. Enter the recipient’s AuthPlus account email under Transfer ownership.
3. Confirm.

Expected result. The code moves to the other account, which can then manage it. The movement is recorded and contributes to the provenance count shown on the certificate.

Warning · Ownership transfer cannot be undone by you

After the transfer the code no longer belongs to your account, so you cannot transfer it back — only the new owner can. Confirm the recipient’s address before proceeding. If the address does not correspond to an account you will see No user with that email.

Note · Two different transfers

This is ownership between accounts, performed in the dashboard, for assets and contents. Custody between verifier profiles in the field is a separate mechanism, described in Transfers & custody. They do not affect each other.