Production-grade patterns for event registration → badge-printing automation.
Architect pipelines that survive event-day load: ingestion, payment reconciliation, template sync, and on-site print routing.
Badge Printing Pipelines is an open reference site for the engineers and operations teams who turn event registrations into printed badges. It is written as a working runbook, not marketing copy: every guide frames a real operational failure, shows the data contract, gives runnable Python, and ends with a triage-and-rollback procedure you can follow while an incident is live.
The examples lean on the tools these pipelines actually run on — Pydantic v2, Celery, Stripe, ReportLab, Redis, FastAPI — but the architectural patterns (idempotent stages, durable queues, dead-letter routing, observable boundaries) translate to any stack.
- Event operations & registration managers running medium-to-high-volume registrations.
- Event-tech developers integrating ticketing, payments, and CRMs.
- Python automation engineers keeping the registration-to-print pipeline healthy in the days before and the hours during an event.
The site covers the four operational domains of the registration-to-badge pipeline, each with in-depth topic and troubleshooting guides:
| Section | What it covers |
|---|---|
| Core Architecture & Event Taxonomy | Event taxonomy schemas, attendee field mapping, identity resolution, badge layout, and the ingress security boundary. |
| Registration Ingestion & Payment Reconciliation | Webhook handling, form-API polling, schema validation, async batching, and refund / chargeback reconciliation. |
| Badge Generation & Template Sync | Dynamic field mapping, QR & barcode generation, font & glyph embedding, and PDF routing. |
| On-Site Check-In & Print Routing | Print-queue orchestration, kiosk sync, badge reprints, and printer failover under live event load. |
Every page pairs a hand-drawn architecture diagram, a strict data contract, annotated code, a failure-mode table, and an incident checklist — so you can read it as a tutorial before the event and as a runbook during it.
Registration-to-badge workflows fail in the same handful of ways every event: schema drift, payment sync gaps, template misalignment, queue saturation, and last-mile print failures. Most write-ups stop at the happy path. This site documents what actually breaks at scale and the deterministic fixes that keep the print floor moving.
- Eleventy static site generator
- Hand-authored, theme-aware inline SVG diagrams (no runtime chart libraries)
- Structured data (JSON-LD:
Article,BreadcrumbList,HowTo,FAQPage) on every page - Deployed on Cloudflare Pages
npm install
npm run build # build the static site into _site/
npm run deploy # build + deploy to Cloudflare PagesIssues and suggestions are welcome — open an issue describing the failure mode or the guide you'd like to see.
- Live site: https://www.badgeprinting.org
- Organization: https://github.com/badge-printing-pipelines