King of Flavors docs

Client handoff

What the client should review and provide before the next build phase.

Client handoff

Use this checklist before moving from prototype to production planning.

Content decisions

Confirm:

  • store name and address display
  • primary product categories
  • featured products
  • product naming style
  • whether prices are public
  • whether stock counts are public
  • whether member pricing exists

Product assets

Provide or approve:

  • product photos
  • category photos
  • store interior photos
  • logo and mark files
  • product descriptions
  • final category labels

Customer flow

Choose the first production checkout path:

  • pickup hold request with counter payment
  • NMI-backed online payment after merchant approval
  • contact form
  • member-only request flow

For this store, pickup hold request is likely the most practical first version.

Review Payment strategy before committing to online payment.

Member flow

Decide:

  • open signup or approved accounts
  • what members can access
  • whether members can save reorder lists
  • whether member drops are public or hidden

The current account direction uses self-hosted Supabase Auth with a protected member locker. Email/password is the stable first path; social login can be enabled later when provider setup is confirmed.

Launch readiness

Before launch, confirm:

  • mobile layout has been reviewed
  • cart behavior is approved
  • product data is approved
  • legal/compliance copy is reviewed
  • staff understands how requests or orders arrive

On this page