Member experience

The current member area is a prototype surface for future customer features.

It is not meant to distract from product browsing. The storefront should work for casual shoppers first, then reward repeat shoppers with faster access.

Current auth status

The prototype now supports a basic member account flow.

Customers can:

• create an account
• sign in
• access a protected member locker
• sign out

The member locker currently shows placeholder reward and activity data. It proves the account boundary before real saved products, pickup requests, and reward history are connected.

Self-hosted account system

The account system is designed around Supabase Auth on the client's self-hosted infrastructure.

This has practical benefits:

• the shop keeps control of the account database
• the storefront is not locked into one payment processor
• the API can verify member sessions before exposing private data
• the same account system can later support saved products, pickup history, and rewards

Self-hosting also comes with responsibilities. Backups, email delivery, provider settings, monitoring, and updates should be treated as part of launch readiness.

Possible member features

Good member features for this store:

• saved reorder list
• pickup history
• member-only drops
• hold requests
• product alerts
• staff-picked bundles
• member pricing prompts

Login and sign up

The prototype includes sign-in and sign-up routes. Email and password login is the current stable path.

Social login can be a good customer experience upgrade, especially Google login. It is currently gated off in the app configuration until the production OAuth provider setup is confirmed.

In production, the member flow should be short:

1. Customer creates an account.
2. Customer confirms email.
3. Customer can access member locker.
4. Customer can save or request products.

Client decisions

Before launching member features, decide:

• What benefit does a member get?
• Should membership be open to everyone?
• Should staff approve accounts manually?
• Should members see different pricing?
• Should member drops be visible publicly but locked?

The cleanest first version is a simple member locker for saved products and pickup requests.