Supabase and Vercel production launch checklist
Sellizi runs on Next.js, Drizzle and standard PostgreSQL. Supabase provides the database and Vercel runs the application, webhooks and scheduled infrastructure.
Use the pooled Supabase connection
Create a Supabase Postgres project and place its pooled connection string in DATABASE_URL. Keep the direct database credential server-only; never expose it with a NEXT_PUBLIC_ prefix.
Apply src/db/schema.ts with drizzle-kit push during initial setup, then use reviewed migrations for later production changes. Run the health check after deployment.
Align public URLs and OAuth
Set NEXT_PUBLIC_APP_URL to the exact HTTPS production origin. Google OAuth requires that same origin plus /api/auth/google/callback in the authorized redirect list.
Email sessions work without Google. If OAuth keys are absent, Sellizi says so instead of pretending that an external sign-in happened.
Verify payments and fulfilment
Cash on delivery needs no payment gateway. For cards and mobile money, add SASPAY_SECRET_KEY (sk_test_... or sk_live_...) and SASPAY_WEBHOOK_SECRET, then in the SasPay dashboard create a webhook to YOUR_DOMAIN/api/webhooks/saspay subscribed to transaction.created, transaction.success, transaction.failed and transaction.cancelled.
Place a small test order with SasPay Checkout, confirm the stock change, update its fulfilment status and verify delivered revenue. Test an expired/cancelled SasPay session too: stock must return and payment must not appear paid.
Put the guide into practice
Create your catalogue, publish your store and manage every delivery in Sellizi.
Start for free