Can I vibe code Odoo?

Build an enterprise-grade ERP inventory management engine in Node.js and PostgreSQL using Knex.js or Prisma, tailored for multi-channel e-commerce operations.

DATABASE SCHEMA & CORE ENTITIES:
1. Product & Variants: Product catalog supporting parent-variant relationships, SKUs, barcodes (EAN/UPC), and unit of measure (UoM) conversions.
2. Warehouses & Bins: Multi-location structure (Warehouse -> Zone -> Aisle -> Shelf -> Bin) with support for virtual locations (Vendor, Customer, Inventory Loss, Transit).
3. Stock Moves & Ledger: Immutable stock ledger (`stock_move`) tracking every physical transfer. Mandatory fields: `product_id`, `source_location_id`, `dest_location_id`, `quantity`, `uom`, `state` (draft, waiting, assigned, done, cancelled), `reference_doc`.
4. Inventory Valuation: Support Perpetual Inventory Accounting with Automated Costing Methods (FIFO and Moving Average Cost / AVCO). Store unit cost on each stock move and maintain continuous stock valuation logs linked to general ledger account entries.
5. Purchase Orders & Goods Receipts: Complete PO workflow (Draft -> Confirmed -> Received -> Invoiced). Receiving goods must generate inbound stock moves to destination bins and compute new AVCO/FIFO inventory valuations.
6. Sales Orders & Delivery Orders: Order lifecycle management syncing with external e-commerce webhooks (Shopify/WooCommerce). Reserving stock must lock inventory at specific bin locations without moving it until pick/pack/ship operations finish.

TECHNICAL INTEGRATIONS:
- Shopify REST/GraphQL Admin API: Webhook receivers for `orders/create`, `orders/fulfilled`, and `products/update`. Bidirectional inventory sync engine with optimistic locking and queue-based execution (e.g., BullMQ + Redis) to handle rate limits and prevent overselling.
- Carrier APIs: Abstracted integration layer for Shippo or EasyPost to generate shipping labels and update tracking numbers on delivery orders.

FAILURE MODES & EDGE CASES TO HANDLE:
- Race Conditions: Concurrent order reservations for the same stock balance must use database-level pessimistic locks (`SELECT ... FOR UPDATE`) or atomic inventory decrement operations.
- Negative Stock Prevention: Strictly block stock transfers where source location available balance (`quantity_on_hand` - `quantity_reserved`) is less than requested quantity, unless explicit allow-negative flag is set per location.
- Inventory Recount Adjustments: Unscheduled stock counts must route through a dedicated virtual `inventory_loss` location to enforce double-entry auditability. Direct raw SQL updates to inventory balance columns are strictly forbidden.

OUT OF SCOPE:
- Full HR, CRM, marketing automation, or native e-commerce storefront website builders. Focus solely on Core ERP (Inventory, Order Routing, Purchasing, Basic Double-Entry Financial Ledger).

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