Brand Systems
•
•
6 min
Designing a Submission Pipeline That Respects Creators
By Studio Kanso
Creators judge a marketplace by how it treats their submission. A confusing upload, silent queues, and opaque rejections push the best makers elsewhere. A transparent pipeline keeps them.
The First Impression Is the Workflow
In CurateOS, a submission becomes a draft, a draft enters review with clear status, and feedback is specific. Creators always know where their work stands.
Feedback Is Product
Rejections that explain themselves turn into improvements. Treating review notes as a feature, not a formality, is how a catalog gets better over time.
Stay in the loop
New drops, curator picks and product updates — straight to your inbox.
SUPABASE READY BOUNDARY
Connect real auth, upload storage, and approvals when you are ready.
The Framer build defines the public marketplace, CMS model, submission experience, and admin UI. Supabase would power Google/email auth, storage, row-level security, and review actions.
Google and email authentication via Supabase Auth
File upload storage and private review buckets
Admin-only review actions with row-level security
Published assets synced into public marketplace views