No ticketing channel of its own
Everything ran through third-party forms and chat messages. No live count of tickets left, no digital ticket to scan at the gate.
Live at akimitsu-small.com
Akimitsu web project
A website, an e-ticketing system and gate check-in for a Vietnamese–Japanese cultural festival series held across Vincom shopping malls.
- 50–100Kvisitors per edition
- 12editions held since 10/2024
- 30+booths & workshops each edition
- 2017the year Small Studio was founded
Context
A festival at scale,
01
02
03
A festival at scale,
run on forms and notebooks.
Akimitsu is a Vietnamese–Japanese cultural festival series produced by Small Studio, held regularly at Vincom shopping malls with booths, a stage, workshops and guests. Each edition draws tens of thousands of visitors, yet ticketing and guest lists were still handled by hand and scattered across tools.
Every edition has its own identity
Each one comes with a different theme, palette and story — a single shared template was never going to be enough.
Many people, many roles
Organisers, managers and gate volunteers — each group needs to see exactly their own part of the work.
Solution
One place for the whole season
The public site, the ticket purchase flow and the admin area live in one system — one account for the visitor, one place to manage for the organisers.
Digital tickets
Buy online, pay by QR bank transfer, receive the ticket straight into your account. Tickets and order history stay available at any time.
Check-in from a phone
Volunteers scan the QR right at the gate and get a clear colour-coded result. No dedicated hardware, no printed lists.
A page per edition
Organisers build each edition’s landing page from ready-made blocks — cover, palette, story, guests, photo gallery.
Discount codes for KOLs
Every KOL gets their own code with its own usage cap, plus the numbers needed to work out commission and measure each one’s reach.
Role-based access
Three levels from administrator down to volunteer, each seeing only their own part. Every significant action is logged.
Content they edit themselves
About pages, FAQ, policies, events, ticket types — organisers update all of it from the admin area without waiting on anyone.
The ticket experience
From picking a ticket to walking through the gate
- 01Sign inCreate an account once; nothing to re-enter in later editions.
- 02Pick a ticketChoose the ticket type, apply a discount code, and the system holds the spot while you pay.
- 03PayScan a QR bank transfer carrying a reference unique to each order.
- 04Get the ticketOnce the order clears, the ticket appears in the customer’s account.
- 05Walk inShow the QR to a volunteer at the gate; each ticket admits once.
Stack
Next.js
TypeScript
Tailwind CSS
Supabase
PostgreSQL
Vercel
VietQR
Takeaways
The decisions that paid off most
-
01
Hand the organisers the controls
Content, events, ticket types and the per-edition pages are all editable from the admin area. Everything they can do themselves is one less thing to wait for — and the reason the system is still alive after handover.
-
02
Design for the next edition, not just this one
Each edition looks its own way but shares accounts, tickets and data. Adding one means adding content, not rebuilding the system.
-
03
Start from how they already work
With no automated payment gateway yet, QR transfer plus manual reconciliation came first — but the seams were built in so automation can be added later without rewriting the core.
See the system running
The website, the event pages and the ticket flow are all live.
Case study · Updated 10/2026