Can I vibe code VTEX?

Build an enterprise headless Distributed Order Management System (OMS) and Marketplace engine in Node.js/TypeScript using Fastify, PostgreSQL (Prisma ORM), and Redis.

DATA MODEL:
1. Organization & Stores: Account, Store (id, org_id, channel_type [B2C, B2B, Marketplace], currency, region_code).
2. Catalog & Inventory: SKU (id, code, attributes_json), InventoryLocation (id, store_id, address, type [Warehouse, PhysicalStore, 3P_Vendor]), StockLevel (sku_id, location_id, physical_qty, reserved_qty, available_qty).
3. Orders & Fulfillment: Order (id, store_id, buyer_id, total, status), OrderItem (id, order_id, sku_id, qty, unit_price, seller_id), FulfillmentGroup (id, order_id, location_id, status, tracking_code, split_reason).
4. Multi-Vendor Marketplace: Seller (id, name, commission_rate, payout_account_id), CommissionLedger (id, order_item_id, seller_id, gross_amount, platform_fee, net_payout, status).

CORE WORKFLOWS:
1. Distributed Inventory Routing Logic:
   - Implement an order placement endpoint POST /api/v1/orders/route.
   - When an order arrives containing multiple SKUs across different locations/sellers, fetch real-time available stock from Redis (synced with PostgreSQL).
   - Execute an optimal fulfillment-routing algorithm:
     a. Group items by Seller ID (3P Marketplace items split into dedicated FulfillmentGroups).
     b. For 1P items, select the single InventoryLocation that can fulfill the largest subset of items to minimize package splits.
     c. Fallback to physical stores if primary warehouse stock < requested qty.
   - Atomically deduct available_qty and increment reserved_qty in Redis using Lua scripts to prevent overselling under high concurrency.

2. Marketplace Settlement Engine:
   - Implement an async worker (BullMQ/Redis) triggered upon FulfillmentGroup status changing to "DELIVERED".
   - Calculate platform take-rate based on Seller.commission_rate.
   - Generate entries in CommissionLedger with status "PENDING_PAYOUT".
   - Expose endpoint POST /api/v1/sellers/:id/payouts to finalize clearing and calculate net remittance.

3. External System Integrations:
   - Provide clean Webhook interfaces for ERP updates: POST /api/v1/inventory/sync (bulk inventory payload with idempotent processing).
   - Mock integration with external Tax and Payment gateways (Stripe Connect setup for multi-seller splitting).

FAILURE MODES & OUT OF SCOPE:
- Out of scope: Visual storefront UI, drag-and-drop page building, live shopping video streams, and proprietary mobile app builders.
- System must handle race conditions where multiple orders claim the last stock item simultaneously; transactions must rollback safely if Redis-to-DB sync fails.
- Out of scope: Regional tax calculation rules (e.g., Brazilian ICMS/ST tax engines). Abstract via generic interface hooks.

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