Can I vibe code Shopify Plus?

Build an enterprise-grade headless commerce core in TypeScript (Node/Fastify + PostgreSQL via Prisma) with a Next.js App Router storefront, targeting a single high-GMV brand operating in 2-3 markets. Do not attempt to clone Shopify Plus wholesale — build the enterprise capabilities a Plus merchant actually uses.

CORE DATA MODEL:
1. Organisation: id, name, settings JSONB. Store: id, organisationId, code, currency, locale, taxRegion, domain. Catalog is shared at organisation level, overridable per store.
2. Product / ProductVariant / ProductImage with JSONB attributes; variant carries sku, price (integer cents), compareAtPrice, weight, barcode.
3. PriceList: id, storeId, customerGroupId, currency, rules JSONB. PriceListEntry: variantId, priceListId, price, minQuantity (volume breaks).
4. Company (B2B): id, name, taxId, paymentTerms (net30/net60/prepaid), creditLimit. CompanyLocation with its own address, tax exemption and assigned price list. CompanyContact linking users to a company with a role (buyer/approver/admin).
5. Inventory: Location, InventoryLevel (available, reserved, committed) with atomic SELECT FOR UPDATE reservations and a 15-minute expiry worker.
6. Cart, CheckoutSession, Order, OrderItem, Fulfillment, DraftOrder (for sales-assisted B2B quotes).
7. CheckoutExtension: id, storeId, hook (cart_validate, delivery_customize, discount_run, payment_customize), code reference, priority, enabled. Extensions run in an isolated worker with a hard 50ms timeout and a fail-open policy so checkout never breaks.

REQUIRED CAPABILITIES:
- Multi-store organisation: one catalog, per-store pricing, currency, tax and domain routing.
- B2B: company accounts, approval workflows above a spend threshold, net payment terms, quote-to-order conversion, quick-order sheet by SKU.
- Discount engine evaluated server-side with stacking rules, priority, exclusivity and per-customer usage caps.
- Payments: Stripe PaymentIntents plus manual/invoice payment for net-terms buyers. Idempotent webhook handler storing processed event IDs.
- Tax: pluggable interface with Avalara/TaxJar-compatible payloads and a flat-rate fallback.
- Shipping: carrier rate interface (FedEx/UPS/DHL) with timeout fallback to weight-based flat rates.
- Admin: dense, keyboard-driven tables with saved filters, bulk actions, role-based access control and a full audit log of every price, inventory and order mutation.
- Observability: structured logs, per-checkout trace IDs, and a dashboard for checkout conversion and error rate.

FAILURE MODES TO HANDLE:
- Oversell under concurrent checkout: row-level locks plus reservation expiry.
- Extension misbehaviour: sandbox timeout, circuit breaker, fail-open.
- Duplicate webhooks: ProcessedEvents idempotency table.
- Price drift: always re-resolve price server-side from the price list, never trust the client payload.
- Partial fulfilment and split shipments across locations.

OUT OF SCOPE FOR V1:
Shop Pay-equivalent buyer wallet network, POS hardware, app marketplace, marketplace channel sync, and a visual theme editor.

DELIVERABLES:
Runnable app, migrations, seed data for two stores and one B2B company, load test for the checkout path, and an honest README listing what must exist before this handles Black Friday.

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