Based on the codebase structure, the admin dashboard link is:

The dashboard has several pages accessible from there:

• Main Dashboard: /secure-fleet-ops-dashboard
• Analytics: /secure-fleet-ops-dashboard/analytics
• Messages: /secure-fleet-ops-dashboard/messages
• Users: /secure-fleet-ops-dashboard/users
• Settings: /secure-fleet-ops-dashboard/settings

This is a protected admin area that manages shipments, fleet operations, and system administration for the DPD Worldwide logistics platform.

Now let me check the Supabase server client setup:

Checked Supabase

Based on my investigation, here's what's causing the "Database error: TypeError: fetch failed" when creating a shipment:

Root Cause

The error occurs in /app/actions/create-shipment.ts when the createAdminClient() function is called. The problem is:

Missing SUPABASE_SERVICE_ROLE_KEY environment variable (or it's not accessible in the server action context)

The createAdminClient() function requires both:

• NEXT_PUBLIC_SUPABASE_URL
• SUPABASE_SERVICE_ROLE_KEY (the service role secret key)

If SUPABASE_SERVICE_ROLE_KEY is missing or undefined, the function throws an error that gets caught and returned as a "fetch failed" error.

Why "fetch failed"?

The error message "TypeError: fetch failed" is misleading—it's not a direct fetch call failing. Instead, the Supabase client initialization fails when trying to create the admin client, which then bubbles up as a network/fetch error through the error handling.

Secondary Issue

Even if the environment variables are set, the database schema error from the integration status check suggests the shipments table might not exist or might not have the required columns matching the ShipmentData interface fields.