Can I vibe code Orderlytics?

Build a production-ready Order Routing and Fulfillment Engine in Node.js/TypeScript using Express, BullMQ, Redis, and PostgreSQL with Prisma ORM.

1. DATA MODEL & SCHEMA:
- Stores: id, name, platform (SHOPIFY, WOOCOMMERCE, CUSTOM), api_credentials (encrypted JSON), created_at.
- Suppliers: id, name, integration_type (REST_API, SFTP_CSV, EMAIL), config (encrypted JSON).
- SKU_Mappings: id, store_id, supplier_id, store_sku, supplier_sku, price_markup.
- Orders: id, store_order_id, status (PENDING, PROCESSING, FULFILLED, FAILED), raw_payload (JSONB), supplier_id, tracking_number, carrier, failure_reason.
- IntegrationLogs: id, order_id, status_code, log_level, request_payload, response_payload, created_at.

2. INGESTION & ROUTING LOGIC:
- Expose POST /api/v1/webhooks/orders receiving payload. Validate platform HMAC signatures.
- Deduplicate incoming orders by checking existing store_order_id in DB to guarantee idempotency.
- Match order items against SKU_Mappings to determine target Supplier. Split multi-item orders into sub-orders if items belong to different suppliers.
- Persist order record as PENDING and enqueue job into BullMQ queue ('order-fulfillment').

3. WORKER FULFILLMENT DISPATCH:
- Consume 'order-fulfillment' jobs. Convert internal order object into supplier-specific schema.
- If Supplier is REST_API: Execute HTTP POST request using Axios with a 15-second timeout.
- If Supplier is SFTP_CSV: Format order as a CSV file and upload to supplier SFTP server directory.
- On success: Update order status to PROCESSING and store supplier reference ID.

4. TRACKING SYNCHRONIZATION:
- Create a recurring BullMQ cron job running hourly to check PROCESSING orders.
- Query supplier API or read inbound tracking CSV folder for assigned tracking codes.
- Upon finding tracking code, call storefront platform REST API (e.g., Shopify Fulfillment API) to mark store order as fulfilled with tracking details.
- Update local order status to FULFILLED.

5. ERROR HANDLING & RETRIES:
- Retry failed supplier API calls up to 5 times using exponential backoff inside BullMQ.
- Send persistent failure events to a Dead Letter Queue (DLQ) and log details in IntegrationLogs.
- Expose POST /api/v1/orders/:id/retry to manually trigger execution of failed orders.

6. OUT OF SCOPE:
- Browser web automation/scraping for non-API suppliers.
- Frontend UI dashboard (API only).
- Real-time stock sync.

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