U-Max Coffee Day

From a reservation to a ticket, then through the door.

Software developer · event reservations and commerce

2026 · past event

U-Max Coffee Day storefront showing the past event and closed table reservations — The Coffee Day storefront. Table reservations for the past event are closed.

The problem

Coffee Day needed the customer and organizer sides to work together: reservations and purchases, Mobile Money checkout, ticket recovery, entry, and collection of purchased items. A successful payment had to lead to a usable record at the event.

What I built

Built the bilingual storefront, cart, Mobile Money checkout, and persistent bookings.

Implemented recovery codes, payment reconciliation, and duplicate-payment prevention.

Connected QR tickets to signed organizer sessions, single-use check-in, and durable collection tracking.

Inside the product

Open an image to inspect the interface at full size.

U-Max Coffee Day shop interface — The shop connects product selection to checkout and event collection.

Coffee Day demonstration ticket marked not valid for entry — Actual ticket interface with fictional demo data. This ticket is not redeemable and contains no usable QR credential.

Payment is not the finish line

The booking remains useful after checkout. Recovery codes let a customer find their ticket again, while organizer tools record entry and item collection separately. Conditional redemption prevents the same entitlement being used twice.

The result

A connected purchase, ticket, and fulfillment workflow
Recoverable bookings backed by persistent storage
Separate organizer tracking for entry and purchased items

Built with

Next.js, TypeScript, Turso / SQLite, CamPay, QR tickets

Something similar?

Tell me about the workflow you want to build.

Discuss a project

Next case studyInVisCon