Can I vibe code Tiendanube / Nuvemshop?

Build a self-hosted e-commerce platform core inspired by Tiendanube / Nuvemshop, using TypeScript + Node.js + PostgreSQL, with a pluggable local-PSP adapter layer.

DATA MODEL:
1. Product: id, sku, title, slug, description, status (draft|active|archived), tax_class, brand_id, created_at.
2. Variant: id, product_id, option_values (jsonb), price_cents, compare_at_cents, currency, weight_grams, barcode, inventory_item_id.
3. InventoryItem: id, sku, location_id, on_hand, reserved, incoming, reorder_point.
4. Category: id, parent_id, slug, name, position, seo (jsonb) — materialised path for fast tree queries.
5. Customer: id, email, password_hash, accepts_marketing, default_address_id, tags (text[]).
6. Cart: id, customer_id nullable, currency, items (line_item[]), discount_codes (text[]), totals (jsonb), expires_at.
7. Order: id, number, customer_id, status (pending|paid|fulfilled|cancelled|refunded), payment_status, fulfilment_status, totals (jsonb), addresses (jsonb), placed_at.
8. Payment / Fulfilment / Refund: append-only rows linked to Order, never mutated in place.

CORE FUNCTIONALITY:
1. Storefront read API (products, collections, search, cart) with SSR-friendly caching and stale-while-revalidate.
2. Cart engine: line-item pricing, tax-inclusive and tax-exclusive modes, promotion stacking rules, currency rounding per ISO 4217 exponent.
3. Checkout state machine: address → shipping rate → payment intent → capture → order. Idempotency keys on every mutating call.
4. Payment adapter interface with a Stripe implementation (payment intents, 3DS redirect, webhooks for async capture, refunds).
5. Inventory reservation on checkout start with TTL release, oversell protection via row-level locking.
6. Admin API + minimal admin UI: catalog CRUD, order search, refunds, manual orders, discount rules.
7. Webhook/event bus (order.created, order.paid, inventory.low) with retries and exponential backoff.
8. A payment adapter interface that models instalments as first-class: display price, buyer-paid interest, merchant fee and settlement date all resolved before checkout renders.

FAILURE MODES TO HANDLE:
- Duplicate payment webhooks: dedupe by provider event id, store processed ids.
- Concurrent checkout on the last unit: pessimistic lock or reserve-then-confirm, never optimistic-only.
- Price drift between cart creation and payment capture: re-price server-side before capture and fail loudly.
- Tax and currency rounding: compute in minor units, never floats.
- Traffic spikes: cache catalog reads at the edge, keep cart/checkout uncached.

OUT OF SCOPE:
- A third-party app marketplace and extension sandboxing.
- Multi-tenant SaaS billing for other merchants.
- Payment processing licences: build on a PSP, never become one.

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