2026 台東博覽會 (Taitung Expo) × 食品商會 (Food Chamber of Commerce) — Expo-Exclusive Bento Points and Lottery Platform
A complete event-tech platform for a two-month event (2026/06/05–08/05): consumer LIFF + PWA points and scratch cards, merchant back office, a 15-module organizer CMS, and a livestreamed grand draw. Built on 206 partner bento shops.
- Client
- 2026 台東博覽會 (Taitung Expo)
- Industry
- Events / associations
- Service
- Custom web & apps
- Led by
- Johnny Yang

What we delivered.
- New members during the event
- 6,090 people
- Partner shops
- 206 bento shops
- Event period
- 2026/06/05–08/05
- Organizer back office
- 15 modules
01Why this case is worth writing up
Large limited-time events (county and city expos, festivals, joint chamber-of-commerce promotions) have a structural problem: the event only runs for two months, but the regulatory / reporting / fairness responsibility is as heavy as a year-round system, and there is no time for a traditional ERP development cycle.
The organizer, 2026 台東博覽會 (Taitung Expo) × 食品商會 (Food Chamber of Commerce), came to us wanting this: consumers can get in, shops can redeem, the organizer can pull reports, and the draws are fair and auditable. And it had to go live on 6/5, no exceptions.

02What we delivered: a complete three-sided architecture
1. Consumer side (LIFF + PWA)
The consumer opens LINE, adds the official account → enters LIFF (LINE's in-app web framework) → automatic LINE Login → lands in their personal account. People who don't use LINE can use PWA mode (browser + manifest) and add it to the home screen on iOS / Android.
- Home: event hero (the Expo-exclusive "Mountain and Sea Feast" bento) + latest news + points progress
- Scan for points: scan the shop's QR code with LINE to collect points; the backend writes the points record
- Bento serial code redemption: specific bento boxes carry a printed serial code; enter it in the app for points
- Scratch cards: trade accumulated points for scratch chances, with canvas-confetti win effects
- Livestream draw: during the grand prize livestream, consumers open the "Livestream Draw" page and follow along as the organizer draws the big prizes
- Prize center: winners list, claim process, redemption status
- My account: points / redemption history / win history
2. Merchant side (206 bento shops)
Every bento shop has its own back office:
- After login, it goes straight to that shop's dashboard (today's redemptions, this month's points contribution, remaining serial codes)
- Redeem the QR codes of consumers coming in to claim prizes
- Check the status of the shop's serial code pool
206 shops running at the same time, each with its own LINE notifications, its own serial code pool, its own reports. A SaaS template can't carry this kind of multi-merchant setup.
3. Organizer side (15-module CMS)
This is the real core of the case. To run the whole event in two months, the organizer needed these back-office modules:
- Back-office login
- Dashboard: overall event data (today's participation, cumulative points, number of winners, shop distribution)
- Event settings: start and end dates, rules copy, terms versions
- Member management: the full pool of LINE consumers, manual points adjustment, flagging of suspicious accounts
- Shop management: activation / suspension / serial code allocation for 206 shops
- Prize management: prize types (e-vouchers / physical prizes / on-site redemption) + quotas + odds
- Serial code management: the bento serial code pool issued to each shop (anti-counterfeit + anti-duplicate redemption)
- Draw management: session setup / scheduling / winners list export
- Livestream big screen: the live on-site display during draws (for the main event venue)
- Prize redemption: closed-loop tracking from winner → prize claim → shop redemption
- Latest news: event announcements, press releases
- FAQ: editable from the back office
- Map pins: location pins for all 206 shops on the map (for consumers)
- Notification log: an audit record of every LINE push message
- Report center: every report needed to close out the event (for the county government / the chamber / accounting)

03Why this case is not simple technically
Most people see "points + lottery event" and think "throw up an app and a promo page." In reality, this stack had to solve:
- Auditable fairness: every draw has to be reproducible and auditable (a hash chain guarantees winning numbers can't be changed afterward)
- Serial codes that resist forgery and duplication: 206 bento shops each get their own serial codes, and the design has to stop one code being redeemed twice, stop counterfeits, and stop leaks by staff
- Sudden traffic spikes: the moment the livestream draw starts, everyone opens the page at once, and the backend has to absorb the spike (the backend scales automatically, and we load-tested before launch)
- LIFF + PWA dual mode: it has to support people who use LINE and people who don't (PWA mode relies on manifest + service worker)
- Third-party organizer relationships: the county government, the chamber, and the food industry association each have their own review process, and the back office has to export the report format each of them wants

04How we work
A two-month event = no chance for a second round of development. Before launch we did this:
- Three-sided demo environment handed to the organizer early for review: admins check the dashboard, shops try redemptions, consumers walk through points → draw → prize claim end to end
- All 15 modules accepted one by one before going to prod
- Complete operating manuals written separately for each role (admins 15 chapters, merchants 2 chapters, users 8 chapters) — PDF export included, so new organizer staff can pick it up and start working
- Livestream grand draw rehearsed twice in the 7 days before it ran (a load test with 10,000 people hitting it at once + integration with the main venue's big screen)
This "demo environment → module-by-module acceptance → complete manuals → pre-launch rehearsal" cycle is our standard practice for event-tech clients. The client moves on, the event ends, but the name attached to a failure stays in the news. We can't let the client carry that risk.
05The numbers it actually produced
Event period 6/5–8/5 (actual counts from the system database):
- 6,090 new members joined during the event
- 7,396 bento serial codes redeemed
- 56,790 points issued to consumers
- 12,670 scans
- 196,853 event website views
- Livestream draws ran on time on 6/7, 7/7, and 8/11
06Why this case proves Brightstream can take on county-level events
The system went live on time on June 5, 2026, ran the full two-month event, and closed on August 5: organized by the county government, co-run with the food chamber of commerce, with 206 bento shops taking part.
After running this one, Brightstream has proven it — we can take on event-tech platforms for county-level / chamber-level / cross-organization events. This is the case that moved our project scale from "single corporate client" to "public-private partnership project."
Food festivals, agricultural expos, and limited-time festival events in other counties and cities can reuse this approach directly.
The event only ran for two months. But accounting reports, shop redemptions, consumer disputes, draw fairness: if any one of those blew up, it would make the news. We didn't want a pretty app. We wanted a system that could carry a county-level event in two months. Brightstream is one of the few partners that could build all three sides, organizer, merchant and consumer, completely, and still go live on time within two months.

