VegMove

Inventory drives most of the order flow. Checkout uses database transactions and row locks to recheck warehouse stock, current quantity, expiry, and sellable-until rules before creating an order.

Shelf and cabinet inventory track physical quantity separately from reserved quantity. Each movement writes a ledger record with before and after balances plus an idempotency key, so a retry does not count the same movement twice.

The system also blocks common inventory mistakes, including negative shelf balances, reserved stock above physical stock, blocked cabinet locations, mismatched product assignments, and moving reserved units during relocation.

Warehouse picking is tied to the inventory ledger. Staff must belong to the right warehouse, the order must be in the right state, the cabinet QR code must match the shelf, and the scanned barcode must match the product or variation.

A successful scan updates the picked quantity, records the scan, and applies the shelf movement in the same transaction. The physical warehouse action and the stock accounting stay together.

The warehouse apps and admin screens support inventory batches, shelf allocation, expired stock handling, refund and exchange returns, barcode lookup, and live order updates.

VegMove supports online payments and cash collection. Razorpay orders and UPI QR payments are used during checkout and delivery collection, with webhooks updating the related order records.

The payment code handles repeated payment requests, cancelled orders, QR closure, partial refunds, late QR payments after cash collection, and refund records for returns or exchanges.

Delivery workflows cover driver assignment, delivery routes, location tracking, delivery PIN confirmation, cash collection, warehouse cash receipt, and outstanding driver-balance calculations.

Operations teams need current order information. VegMove uses Redis-backed server-sent events for order, staff, driver, refund, and exchange updates, with heartbeat handling for long-running connections.

BullMQ handles background work such as order-created side effects, payment timeouts, delivery extensions, delay alerts, low-stock alerts, first-order welcomes, refund reminders, search logging, and scheduled notifications.

Several jobs re-read the current order state before acting. For unpaid online orders, a timeout cancels the order only if it is still pending and unpaid.

The admin dashboard is the central operating workspace. Catalog management covers products, variations, categories, brands, prices, banners, and home sections. Commercial controls include coupons, promotions, reward tiers, and points redemption.

Fulfillment tools cover warehouse-filtered orders, delivery and payment status, inventory batches, barcodes, expiry and sellable-until dates, shelf grids, cabinet mapping, and stock entries. Driver management, delivery slots, cash deposits, refunds, and exchanges connect fulfillment to the finance and support workflows. Reports cover sales, category revenue, customer signups, orders, and stock changes; PostgreSQL queries also support cohorts and repeat-purchase reporting.

Sensitive areas use role and permission checks, TOTP, CAPTCHA verification, Redis-backed attempt controls, blocked-device checks, and expiring customer phone-access grants.