Can I vibe code Metapack?

Build a multi-carrier shipping allocation and tracking engine in Node.js and PostgreSQL.

1. DATA MODEL
Create tables for:
- `orders` (id, destination_address, weight_grams, dimensions_cm, status)
- `carrier_accounts` (id, carrier_code, api_credentials_json, is_active)
- `shipping_rules` (id, priority, condition_json, target_carrier_account_id)
- `shipments` (id, order_id, carrier_account_id, tracking_number, label_url, zpl_data)
- `tracking_events` (id, shipment_id, raw_status, normalized_status, payload, occurred_at)

2. CARRIER ALLOCATION LOGIC
Implement a service that takes an `order_id` and evaluates active `shipping_rules` sorted by priority. Rule evaluation matches weight ranges, destination postal zones, or transit time requirements. If a rule matches, assign the designated `carrier_account_id`.

3. LABEL GENERATION MODULE
Implement a unified interface with mock drivers for UPS and FedEx REST APIs. Send order details to the selected carrier endpoint, retrieve the tracking number and raw ZPL string, store them in the `shipments` table, and update order status to `fulfilled`.

4. TRACKING NORMALIZATION ENDPOINT
Create a POS webhook route `/webhooks/carrier-tracking` that receives incoming delivery updates. Map raw carrier delivery codes (e.g., 'DL', 'DELIVERED', 'IN_TRANSIT') to a strict unified Enum (`CREATED`, `IN_TRANSIT`, `OUT_FOR_DELIVERY`, `DELIVERED`, `EXCEPTION`). Log events to `tracking_events` and emit an internal event on status change.

5. RESILIENCE & FAILURE HANDLERS
Add exponential retry backoff (up to 3 attempts) for carrier API timeouts. If primary carrier API calls fail continuously, failover to a default secondary carrier account and flag the shipment with a `carrier_failover_occurred` warning.

OUT OF SCOPE: Paperless customs declarations, thermal printer queue hardware management, legacy EDI file generation.

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