Notification System

​

Overview

​

Architecture

                    ┌──────────────────┐
                    │  Reminder Engine  │
                    │  (Edge Function)  │
                    └────────┬─────────┘
                             │ evaluates schedules
                             ▼
          ┌──────────────────────────────────┐
          │       reminder_schedules         │
          │  + reminder_schedule_day_overrides│
          └──────────────┬───────────────────┘
                         │ creates
                         ▼
              ┌─────────────────────┐
              │    notifications    │◄── read/manage by users
              └──────┬──────────────┘
                     │ dispatches
          ┌──────────┴──────────┐
          ▼                     ▼
  ┌───────────────┐   ┌─────────────────────┐
  │  Web Push     │   │  Mobile Push / Email │
  │  (browser SW) │   │  (Expo + Resend)     │
  └───────────────┘   └─────────────────────┘

​

Flow

1. The dispatch-reminders Edge Function runs on a cron schedule
2. It evaluates reminder_schedules + reminder_schedule_day_overrides for the current time and day
3. For each schedule due, it checks if a recent submission exists (smart skip)
4. If a reminder is needed, it inserts a row into notifications
5. It also dispatches to external channels: Web Push via web_push_subscriptions, mobile push via Expo, and email via Resend (if reminder_emails_enabled is true on the user)

​

Database Schema

​

notifications

​

web_push_subscriptions

​

reminder_schedules

• One global default (where auction_id IS NULL AND location_id IS NULL)
• One per auction (where location_id IS NULL)
• One per location

​

reminder_schedule_day_overrides

​

reminder_logs

​

Edge Function: dispatch-reminders

​

Invocation

​

Logic

1. Fetch all enabled reminder_schedules
2. For each schedule:
   a. Resolve the effective config (with day overrides for today)
   b. Determine if a reminder is due now based on mode:
      - Interval: check if current time is within window and interval elapsed
      - Deadline: check if any deadline advance time matches
   c. If due, check smart_skip:
      - Query recent submissions for the schedule's location(s)
      - If submission exists in current period, skip
   d. If not skipped:
      - Insert notification rows for each assigned user
      - Dispatch Web Push to web_push_subscriptions
      - Send email via Resend (if user.reminder_emails_enabled)
      - Send mobile push via Expo push API
   e. Log to reminder_logs

​

Environment Variables

​

VAPID Key Configuration

​

Generating VAPID Keys

npx web-push generate-vapid-keys

• NEXT_PUBLIC_VAPID_PUBLIC_KEY — Used by the admin dashboard client
• VAPID_PRIVATE_KEY — Used by the Edge Function (server-side only)

​

Adding New Notification Types

await serviceClient.from('notifications').insert({
  user_id: userId,
  auction_id: auctionId,
  type: 'inspection_complete',
  title: 'Inspection Completed',
  body: `Vehicle ${vin} passed inspection`,
  data: { inspectionId, vin },
});

​

RLS Policies Summary

​

Testing Locally

​

Testing Notifications

1. Insert a notification directly via SQL or the Supabase dashboard:
   Copy

   INSERT INTO notifications (user_id, type, title, body)
   VALUES ('your-user-id', 'system', 'Test Notification', 'This is a test');
   
2. Open the admin dashboard — the notification bell should show a badge
3. Click the bell to see the notification in the panel

​

Testing Web Push

1. Set NEXT_PUBLIC_VAPID_PUBLIC_KEY in your admin .env.local
2. Enable browser notifications in the notification panel
3. Accept the browser permission prompt
4. Send a test push via the Edge Function or directly via the web-push library

​

Testing Reminders

1. Create a reminder schedule via the admin UI or SQL
2. Invoke the dispatch-reminders Edge Function manually:
   Copy

   supabase functions invoke dispatch-reminders --no-verify-jwt
   
3. Check the notifications table and reminder_logs for results

​

Related Guides