Products sync in as drafts. Review each one, set your own name, price, description and image, then hit Publish to make it visible on your site. Unpublished products are NEVER shown to customers.

1. 1. Printful token — In Printful → Developers, create a token and paste it into the Supabase Edge Function secret PRINTFUL_TOKEN. Optionally set PRINTFUL_STORE_ID if your token accesses multiple stores.
2. 2. Stripe keys — Set STRIPE_SECRET_KEY (sk_live / sk_test) as a Supabase Edge Function secret.
3. 3. Stripe webhook — In Stripe, create a webhook pointing to /functions/v1/stripe-webhook listening on checkout.session.completed. Set STRIPE_WEBHOOK_SECRET to the signing secret.
4. 4. Deploy the functions — supabase functions deploy printful-sync create-checkout stripe-webhook.
5. 5. Click Sync — Hit the button above. Products appear on the public homepage instantly.

Never put Stripe secret keys or Printful tokens into HTML or JS files — always use the Supabase Edge Function secrets.

Messages submitted through the website contact form.

• Supabase — Auth (fan magic-link + admin), database for products/variants/orders, Edge Functions for Printful sync + Stripe checkout.
• Printful — Full catalog mirrored via the printful-sync Edge Function. One click in the Shop tab pulls every product, variant, size, color, and mockup.
• Stripe — Checkout sessions are created server-side by the create-checkout function with anti-fraud re-pricing. The stripe-webhook function confirms payment and auto-creates the Printful order.

Set these via the Supabase CLI: supabase secrets set KEY=value.

• PRINTFUL_TOKEN — from Printful → Developers
• PRINTFUL_STORE_ID — optional, if your token covers multiple stores
• STRIPE_SECRET_KEY — sk_live_... or sk_test_... from Stripe
• STRIPE_WEBHOOK_SECRET — whsec_... from the Stripe webhook you pointed at /functions/v1/stripe-webhook

Never put these keys in HTML or JS files — always use Supabase secrets.

Edit the full content.json directly. Use "Apply JSON" to load it back into the dashboard.