Issuing certificates

Running an edition register

Issue every piece of a limited edition in advance, assign pieces to orders, replace lost certificates without losing the history, and export everything.

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

  1. Set the edition size

    In Settings → Serial numbering, set the edition size (pieces per product, for example 999) and the format (for example 001/999). Edition numbers are counted per product and never reused.
  2. Create the pieces

    Issue them by hand from Certificates, or import a CSV with a productId column so the size limit and no-reuse rule apply to each row. An edition number above the size, or one already taken, is refused.
  3. Print

    Print labels from Labels, or download print-ready QR files (below) for your printer.

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.

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

ExportWherePlan
Certificates (CSV)Certificates → ExportAll plans
Ownership history (CSV)Certificates → Ownership historyAll plans
Change log (CSV)Certificates → Change logAll plans
QR code as vector SVG or 1200 px PNGA certificate's pageStarter and Pro
Every active QR code as SVG in one ZIPCertificates or LabelsStarter and Pro
Full export (JSON) with history, change log and photo indexCertificatesPro
All private photos (ZIP)CertificatesPro

Private photos

On Pro, attach photos to a piece from its certificate page, for example at dispatch, on a return or for a complaint, with a short note. They are visible only to you in the app, never on public pages, and you can download the originals at any time. Up to 50 photos per piece, 10 MB each.

Certificate pages on your own domain

On Pro, certificate pages can open on your own subdomain, such as verify.yourbrand.com. Enter it in Settings → Custom verification domain and the two DNS records to add appear straight away. Authentica checks automatically and emails you as soon as the domain is live, usually within an hour of adding the records. New links, QR codes, emails, the API and webhooks then use your domain, and QR codes printed earlier keep working.

Plan required


Related articles

Not on Shopify yet?

Start a free Shopify trial, then add Miko apps when you are ready.

Set up your store in minutes and try it with your own products. Loyalty, wholesale pricing, AI descriptions and the rest of the Miko apps install in one click once your store is live.