Bulk issuance

A thousand certificates is one upload.

Bring recipients from a spreadsheet, a saved contact list or a form, map the columns once, and let the queue do the rest: render, email, retry, report — while you watch it happen live.

1 upload

Excel, CSV or a saved list

90 days

ahead, the furthest a batch schedules

3 states

per recipient: rendered, emailed, delivered

0 blocked

a bad address never stops the batch

Excel, CSV or saved lists

Upload a file or reuse a contact list. Columns map to your template's dynamic fields — any column, not just name and email.

A real queue, not a loop

Rendering and sending run in a background worker with automatic retries. A failed address never blocks the rest of the batch.

Live per-recipient status

Watch each certificate move through rendered → emailed → delivered, and see exactly who bounced and why.

Schedule it

Queue a batch up to 90 days ahead — results day, the end of the cohort, the morning after the event.

Test before you send

Send yourself a test certificate from the real template and the real email, then launch the batch with confidence.

ZIP export included

Need the files themselves? Download the whole batch as a ZIP of PDFs, named per recipient.

In practice

How it runs

  1. 1

    Upload recipients

    Excel/CSV, a saved list, or a connected form.

  2. 2

    Map and preview

    Match columns to fields; preview a real certificate.

  3. 3

    Launch or schedule

    The queue renders, emails, retries and reports.

Made for

Who runs this every week

Questions

What teams ask before they start

What happens to the batch if some emails bounce?

Nothing stops. Each recipient runs independently in the queue: transient failures retry on their own, hard bounces are marked with the reason, and every other certificate keeps rendering and sending. The report tells you exactly who did not receive theirs.

Can I re-send to only the people who failed?

Yes. The batch view lists each recipient with their outcome, so you can fix an address and re-send to that one person, or pick everyone who bounced and send again, without re-running the whole batch.

How large can a batch be?

The queue is built for thousands of recipients in one run; sending is paced to your mailbox provider's limits so a large batch is spread rather than flagged. What caps a batch is your plan's monthly certificate allowance, from 100 on Free to 25,000 on Business.

Do I need email addresses for everyone?

No. A recipient without an email still gets a rendered certificate you can download from the batch as a PDF, and the whole batch exports as a ZIP named per recipient. For attendees you have not collected, a claim form lets them fetch their own.

Works with

The rest of the platform

Your first certificates are minutes away.

Free to start — design a template, send yourself a test, and see the verification page live.