Can I vibe code Cegid?

Build an enterprise retail inventory and omnichannel POS engine in Node.js, PostgreSQL, and React.

The system must handle three core entities: Stores (physical brick-and-mortar locations and e-com fulfillment nodes), Inventory Units (SKUs with matrix variants like Color/Size, tracked by Lot and Serial Number per Store), and Orders (POS cash-register transactions and e-commerce orders).

Core Requirements:
1. Inventory Engine: Implement real-time inventory allocation across stores with 4 state categories per SKU/Location: On-Hand, Allocated (unfulfilled web order), In-Transit (store transfer), and Available-to-Promise (ATP). Support matrix SKUs (Style-Color-Size grid).
2. Omnichannel Order Management:
   - Ship-from-Store algorithm that selects the optimal physical store based on current ATP, proximity, and store picking capacity.
   - Click-and-Collect (BOPIS) state machine: Created -> Inventory Reserved -> Picked -> Ready for Customer -> Collected / Returned.
3. Pricing & Promotion Rules Engine: Build a pipeline that evaluates cart items against layered rules: Tiered Volume Discounts, Mix-and-Match (e.g., Buy 2 items from Category A, get 1 from Category B at 50% off), and Store-Specific Price Overrides.
4. Offline-First Register POS API: Expose a REST/WebSocket local sync service that allows a POS client to operate offline using an IndexedDB cache, enqueueing sales receipts with cryptographic sequence hashes (simulating basic fiscal chaining) and auto-flushing to the server on reconnect.
5. Reporting & Ledger: Build an audit log of all inventory movements using double-entry ledger bookkeeping (Debit Inventory Account, Credit COGS or Sales Account on register tender).

Database & Models:
- `products` (id, style_code, name, brand)
- `variants` (id, product_id, sku, color, size, barcode_gtin)
- `stores` (id, code, name, timezone, store_type [physical/warehouse/ecom])
- `inventory_levels` (variant_id, store_id, on_hand, allocated, in_transit, updated_at)
- `promotions` (id, priority, conditions_json, actions_json, valid_from, valid_to)
- `orders` (id, store_id, register_id, sequence_number, status, total_amount, fiscal_hash, previous_fiscal_hash)
- `order_items` (order_id, variant_id, qty, unit_price, discount_amount)
- `stock_ledger` (id, timestamp, origin_store_id, target_store_id, variant_id, qty, transaction_type [sale, return, adjustment, transfer])

Out of Scope:
- Physical hardware driver interfaces (OPOS, JavaPOS).
- Full legal country-specific tax certification modules (NF525, TicketBAI).
- Payroll or complex HR scheduling modules.

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