Can I vibe code Outvio?

Build a post-purchase shipping tracking and notification microservice using Next.js App Router, Supabase, and Tailwind CSS.

1. DATA MODEL:
Create database tables for orders (id, platform_order_id, customer_email, status), shipments (id, order_id, carrier_code, tracking_number, current_status, estimated_delivery, raw_carrier_payload), and tracking_events (id, shipment_id, status, description, location, timestamp).

2. INTEGRATIONS:
- Set up a webhook endpoint to receive new order and fulfillment payloads from Shopify or WooCommerce.
- Integrate with a multi-carrier API aggregator (e.g., EasyPost or ShipEngine) to generate shipping labels and register tracking numbers for webhook updates.
- Implement a webhook handler to process carrier status updates (e.g., 'in_transit', 'out_for_delivery', 'delivered', 'exception') and insert records into tracking_events.

3. CORE FEATURES:
- Branded Tracking Page: Create a public route `/tracking/[tracking_number]` that fetches the latest tracking events and displays a visual step-by-step timeline of the shipment.
- Automated Email Notifications: Trigger transaction emails via Resend when a shipment transitions to 'out_for_delivery' or 'exception'.
- Basic Return Request: Build a `/returns` page allowing users to input order number and zip code, selecting items to initiate a return request.

4. FAILURE HANDLING:
- Handle missing carrier status events by polling the carrier API every 12 hours for active shipments.
- Log webhook validation failures and implement an exponential backoff retry queue using Supabase Edge Functions or Upstash Queue.

5. OUT OF SCOPE:
Do not write custom direct SOAP or raw FTP integrations for individual regional European couriers; rely strictly on a unified carrier API provider for tracking normalization.

$ each button prefixes agent-specific run instructions · build your own product, never copy proprietary code, trademarks or designs