Can I vibe code ShippyPro?

Build a multi-carrier shipping label and tracking microservice for an e-commerce platform using Node.js, Fastify, TypeScript, and Prisma with PostgreSQL.

The system must handle three primary workflows: Carrier Rate Shopping, Label Generation, and Post-Purchase Tracking Sync.

1. DATA MODEL & SCHEMA
Define the following Prisma models:
- Order: id, externalOrderId, source ('shopify'|'woocommerce'|'custom'), recipientName, addressLine1, addressLine2, city, state, postalCode, countryCode, email, phone, items (JSON), status ('pending'|'fulfilled'|'cancelled').
- CarrierAccount: id, carrierName ('dhl_express'|'dpd'|'fedex'|'post_italiane'), credentials (encrypted JSON containing api_key, account_number, secret), isActive (boolean).
- Shipment: id, orderId, carrierAccountId, trackingNumber, labelUrl (PDF stored in S3/MinIO), shippingCost (decimal), currency, status ('label_created'|'in_transit'|'out_for_delivery'|'delivered'|'exception'), metadata (JSON).
- ReturnRequest: id, shipmentId, RMA, reason, status ('requested'|'approved'|'label_generated'|'completed'), returnLabelUrl.

2. CARRIER INTEGRATION ENGINE
Implement an extensible Carrier Adapter pattern with an abstract base class `BaseCarrierAdapter`.
Implement adapters for:
- DHL Express REST API (Shipment creation & Label generation)
- DPD REST API (Parcel creation & Label generation)

Each adapter must implement:
- `getRates(parcelDetails, destinationAddress)`: Normalizes rate responses.
- `createShipment(order, parcelConfig)`: Calls the respective carrier API, requests a standard 4x6 PDF/ZPL label, saves the binary file to an object store, and returns the tracking number and label URL.
- `getTracking(trackingNumber)`: Maps raw carrier statuses to unified statuses: 'label_created', 'in_transit', 'out_for_delivery', 'delivered', 'exception'.

3. SHOPIFY & WOOCOMMERCE SYNC ENGINE
Create Webhook endpoints to ingest new orders from Shopify (`/webhooks/shopify/orders-create`) and WooCommerce (`/webhooks/woocommerce/orders-create`).
Upon receiving an order:
- Validate webhook signature (HMAC-SHA256).
- Save order to PostgreSQL.
- Trigger automatic routing rules (e.g., if country == 'IT' use BRT/DPD, if international use DHL).
- Generate shipping label using the designated carrier adapter.
- Push tracking number and fulfillment status back to Shopify/WooCommerce via REST API.

4. TRACKING CRON WORKER
Implement a background worker (using BullMQ) that queries active shipments (not 'delivered' or 'cancelled') every 30 minutes, fetches tracking status from carrier adapters, updates PostgreSQL database, and triggers customer email notifications via Resend API on status transitions.

FAILURE MODES & OUT OF SCOPE:
- Out of scope: Physical printer network bridging (Zebra raw print daemons), cash on delivery (COD) handling, manual customs paper clearance, and freight carrier connections.
- Error handling: Handle carrier API downtime with exponential backoff retries. If carrier label generation fails, mark order as 'fulfillment_failed' and alert via webhook. Ensure encrypted storage for carrier API credentials using AES-256-GCM.

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