For a limited edition, the certificate often needs to exist before the sale: pieces are numbered, photographed and certified in the studio, then sold one by one. Authentica can run that register for you, with each certificate tied to one physical piece for its whole life. Every tool here is off until you use it, so nothing changes for a store that issues on each order.
Issue every piece in advance
Set the edition size
In Settings → Serial numbering, set Default size for new editions (for example 999) and the format (for example 001/999). Each product is its own edition. It takes the default size when its first number is issued and keeps that size for good. Edition numbers are counted per product and never reused.Create the pieces
Issue them by hand from Certificates, or import a CSV (upload the file or paste the rows). With aproductIdcolumn the product's size limit and no-reuse rule apply to each row; without one, rows that give aneditionTotalare checked the same way. If the import creates a new edition, itseditionTotalsets that edition's size. An edition number above the size, one already taken, or aneditionTotalthat doesn't match an edition's size is refused, and the import page lists each refused row with the reason.Print
Print labels from Labels, or download print-ready QR files (below) for your printer.
Run editions of different sizes
Every edition keeps the size it started with, so you can sell a 150-piece edition and a 75-piece edition at the same time. To start a new edition at a different size, change Default size for new editions before its first piece is issued, or import its pieces with that editionTotal. Editions that have already started are never affected by the default. Edition progress, at the bottom of the same section, shows each edition against its own size and marks it Complete when every number is used. Once an edition is complete, no further certificate is issued for it.
Hold new pieces until they are checked
On Pro, activation checks start every new piece as Not activated until you tick your own checklist on its certificate page. Until then it shows no valid status, cannot be assigned to an order and its buyer email waits.
Give each order a pre-issued piece
- Automatically: turn on Give orders a pre-issued piece first in Settings → Serial numbering. Each new order receives the lowest unassigned piece of that product instead of a new certificate. If none is left, a new one is issued as usual.
- By hand: on a certificate's page, use Edition register → Assign to an order and enter the order number. The buyer from that order becomes the owner.
Replace a certificate
If a card is lost or a print is damaged, open the certificate and choose Replace certificate. The new certificate keeps the same piece, edition number, owner and ownership history. The old one shows as replaced on its public page with a pointer to the newer record, and in the API it stays revoked with superseded: true, so integrations do not break. Private photos move to the new certificate with the piece.
What the public page shows
- Edition number as the identity (Starter and Pro): show the edition number, such as 042/150, where the certificate number would be, or no identity line at all. See Public page wording and privacy.
- Lookup by edition and piece number (Starter and Pro): anyone holding a card printed with the edition name and piece number can reach the current certificate from
/apps/authentica/lookupon your store. See Look up a certificate by serial or edition number. - Certificates that are not valid: a replaced, revoked, expired or not-yet-activated certificate carries a large watermark across it, its seal shows no tick, and it never shows the PDF button or the signature line. Printing the page keeps the status at the top.
History of every change
Each certificate's page shows a history of what happened and who did it: issued, assigned, transferred, revoked, reactivated, replaced. Export it for every certificate from Certificates → Change log (CSV).
Revocation switches
- Refunds: in Settings → Refunds, revoke all of an order's certificates on any refund, only the refunded pieces, or never automatically.
- Cancellations: in the same section, untick Revoke certificates when an order is cancelled to keep them valid.
Exports and print files
| Export | Where | Plan |
|---|---|---|
| Certificates (CSV) | Certificates → Export | All plans |
| Ownership history (CSV) | Certificates → Ownership history | All plans |
| Change log (CSV) | Certificates → Change log | All plans |
| QR code as vector SVG or 1200 px PNG | A certificate's page | Starter and Pro |
| Every active QR code as SVG in one ZIP | Certificates or Labels | Starter and Pro |
| Full export (JSON) with history, change log and photo index | Certificates | Pro |
| All private photos (ZIP) | Certificates | Pro |
| Verification archive (ZIP): every certificate's public page as a standalone file | Certificates | Pro |
Private photos
On Pro, keep dispatch, return and complaint photos on each piece, visible only to you, protected from deletion and exportable as a ZIP. See Private piece photos.
Backups and recovery
- Authentica backs up its database every day, keeping daily copies for 30 days and one copy per month for 6 months, in encrypted storage in the United States.
- If something is deleted by mistake, we can restore a single store or record from those backups. Email [email protected] with the store and what to restore. There is no charge. A restore only brings back missing records and never overwrites newer ones.
- For your own independent copy, run the exports whenever you like, or on Pro schedule them with the export and photo endpoints.
Certificate pages on your own domain
On Pro, certificate pages can open on your own subdomain, such as verify.yourbrand.com, and printed QR codes keep working. See Verification links and your own domain.
Your certificates stay yours. Certificates → Verification archive (ZIP) downloads every certificate's public page as a self-contained file, saved at the exact path its QR code uses. Upload that folder to any static web host and point your verification domain at it, and every QR code issued on your own domain keeps resolving to its certificate, whether or not you still use Authentica. Download a fresh archive after issuing or transferring certificates to keep your copy current.
Plan required
Related articles