Can I vibe code Shopify?

Build a production-ready E-commerce Storefront and Order Management MVP in Node.js (Fastify), TypeScript, PostgreSQL (Prisma), and Next.js App Router (Tailwind CSS).

CORE DATA MODEL & ENTITIES:
1. Product & Variants: Product (id, title, handle, description, status: draft/active), ProductVariant (id, productId, sku, price, compareAtPrice, inventoryQuantity, options JSON), ProductImage (id, productId, url, altText, position).
2. Customer & Address: Customer (id, email, passwordHash, firstName, lastName, phone), Address (id, customerId, line1, line2, city, state, postalCode, country, isDefault).
3. Inventory & Locations: Location (id, name, address), InventoryLevel (id, variantId, locationId, available, reserved, committed).
4. Cart & Checkout: Cart (id, customerId nullable, sessionToken, status: active/completed), CartItem (id, cartId, variantId, quantity), CheckoutSession (id, cartId, paymentIntentId, shippingAddress JSON, billingAddress JSON, taxAmount, shippingCost, totalAmount, status: pending/completed/failed).
5. Orders & Fulfillment: Order (id, orderNumber, customerId, total, subtotal, taxTotal, shippingTotal, paymentStatus: pending/paid/refunded, fulfillmentStatus: unfulfilled/partial/fulfilled), OrderItem (id, orderId, variantId, quantity, unitPrice), Fulfillment (id, orderId, trackingNumber, carrier, status).

TECHNICAL REQUIREMENTS & CORE LOGIC:
1. High-concurrency Atomic Inventory Reservation: Implement atomic database updates for inventory during checkout. When a checkout session is initiated, decrease `available` inventory and increase `reserved` inventory using PostgreSQL transaction locks (`SELECT FOR UPDATE`). If inventory drops below 0, roll back immediately with a 409 Conflict error. Set a 15-minute background expiration worker to release expired reserved inventory back to `available`.
2. Stripe Payments Integration: Use Stripe PaymentIntents API. Create a PaymentIntent on checkout submission. Register a Stripe Webhook handler (`/api/webhooks/stripe`) that verifies signature, handles `payment_intent.succeeded`, converts CheckoutSession to Order, marks paymentStatus as `paid`, and shifts inventory from `reserved` to `committed`.
3. Multi-location Shipping Calculation: Implement a fallback shipping service that calculates flat-rate or weight-based shipping rules based on shipping address postal codes.
4. Next.js Storefront: Server-side rendered product listings, variant selector, cart drawer with persistent state via HttpOnly cookies, and responsive checkout page with Stripe Elements.
5. Admin Dashboard: Manage products, update stock across locations, view order stream, mark items as fulfilled with tracking numbers, and view sales performance metrics.

OUT OF SCOPE:
Do not build native mobile apps, POS card reader hardware integrations, multi-channel marketplace sync (Amazon/Etsy), complex multi-currency translation layers, or full-featured app store plugin architecture.

FAILURE MODES TO HANDLE:
1. Double-spending/over-selling during parallel checkouts: Solved via explicit database row locking on variants.
2. Webhook idempotency: Store Stripe event IDs in a `ProcessedEvents` table to ensure duplicate webhooks do not generate duplicate orders or double-deduct stock.
3. Cart item price mutation drift: Always pull price directly from `ProductVariant` table during server-side checkout initialization, never trusting payload prices sent from client frontend.

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