# Thailand Commerce Form Wireframe Pack

Date: 2026-05-08
Status: local-only static mockup complete
Site file: `side-ventures/thailand-commerce-site/waitlist-form.html`

## Purpose

Create a reviewable waitlist/product-vote form before connecting any external tool. The current implementation is static HTML only: no backend, no tracking, no external form embed, no checkout, no public deployment.

## Included fields

1. Email address
2. Product vote
   - Woven market bag hero
   - Scarf + scrunchie + pouch bundle
   - Small pouch / travel organiser add-on
   - Stationery or paper gift set
   - Not sure / show me first drop
3. Colour / style preference
   - Natural straw / neutral tones
   - Warm market colours
   - Black / everyday styling
   - Bright patterned textile
   - Giftable mixed colourway
4. Price comfort
   - Under £15 add-on
   - £15–£30 gift / pouch / accessory
   - £30–£45 small-batch accessory
   - £45–£65 hero woven bag
   - Launch-offer only
5. Source attribution
   - TikTok
   - Instagram
   - YouTube Shorts
   - Friend / family
   - Website preview
   - Other / not sure
6. Consent placeholder checkbox
   - Draft-only language: user understands this is interest, not an order; future email/contact consent wording must be reviewed before public use.

## Implementation notes

- The mock form uses `onsubmit="event.preventDefault()"` and a local alert to make the no-submission status obvious.
- Inputs are named in a backend-friendly way (`email`, `product_vote`, `colour_preference`, `price_comfort`, `source_attribution`, `consent_placeholder`) for later mapping.
- The site nav and home/product CTAs now link to `waitlist-form.html` for internal review.
- The existing small placeholder forms remain static and non-submitting.

## Approval gates before real integration

Do not connect anything until Alex explicitly approves:

### Tally / Google Forms gate

- Final public copy and brand name
- Exact fields to collect
- Consent wording and privacy/data-retention handling
- Response storage owner and export cadence
- Whether source attribution should use hidden UTM fields or a visible dropdown

### Shopify gate

- Shopify/account setup approval
- Customer list and marketing-consent settings
- Waitlist/app choice approval
- Checkout/payment settings review
- Product claims, shipping, returns and availability wording
- No checkout exposure until stock and compliance notes are ready

### Analytics/tracking gate

- No pixels, cookies, analytics tags or ad retargeting until separately approved.
- For MVP, prefer simple form-source fields and manual weekly review before adding platform tracking.

## Next recommended step

Review the static wireframe locally with dummy data, then choose either:

1. Tally/Google Forms for the fastest waitlist validation, or
2. Shopify waitlist only if the store build is approved and close to launch.

Recommendation: use Tally/Google Forms first for low-risk demand validation, then migrate confirmed product interest into Shopify when the first drop is ready.