SLRP

Background

Coffee-industry data is fragmented at every stage: production, import and export, roasting, cafés, and consumers. Producers have a hard time knowing where and how their coffee is consumed, and consumers have nowhere to keep what they drink in a standardized form.

SLRP (Specialty Lot Registry Platform) aims to bridge that gap. It starts with cupping: hosting, gathering, running, and recording sessions in one place, then returning the accumulated sensory records as personal analysis and tools for running an organization.

My role

• Product planning, development, and operations (lead developer and operator)

What I built

• Sessions: Setting up and signing up for business cuppings, public cuppings, and bean-sharing and tasting sessions. A monthly calendar, a session list, and a live scoreboard
• Cupping input: SCA/CVA cupping forms (designed separately for desktop and mobile), a quick-entry mode, and a path for recording without checking in
• Reports: A four-tab analysis report for hosts (Overview · By Sample · By Participant · Raw Data) with PDF export and shareable result images, personal reports for participants, and AI session reports
• Organization tools: Company Workspace — calibration and QC, and additional member seats
• Coffee experience records: Phase one of the Coffee Experience Registry — issuing and looking up QR coffee cards, and recording the experience of the coffee you drank
• Korean and English support: A bilingual ko/en site with the same screen structure

Approach

Built with Next.js, React, TypeScript, and Tailwind CSS, with Supabase for data and authentication. User distinctions (plan, sign-up role, internal-feature eligibility, partner approval, business verification) are kept on separate axes. Permissions are decided from the user as verified on the server, and the database adds a second guard with RLS.