System Requirements Document for inventory-management-system

1. Introduction

Chamunda Inventory Management System is a modern, professional, responsive web application for a sweets shop / food business. It combines two accepted systems in one product: a customer-facing online shopping experience for browsing and buying mithai, kaju sweets, gift boxes, namkeen and related items, and a staff-facing inventory, order-processing and billing management system for running the shop behind the counter.

The product intent is to make Chamunda look and behave like a real production-ready business application rather than a basic demo: a premium sweets-shop storefront with appetite appeal, plus a serious operational back office with dense tables, live stock counts and automatic money math.

The audience is:

• Customers who browse, search, filter and sort sweets, manage a cart, check out with delivery and payment details, and track their own past orders.
• Admin who oversees the whole operation: dashboard analytics, inventory, products, orders, billing, customers, reports and settings.
• Manager who supervises inventory, products, orders and reports to keep stock and fulfilment healthy.
• Cashier who operates the billing/POS counter, builds a bill, applies discount and tax, selects a payment method, and generates, prints or downloads an invoice.

2. System Overview

The application is delivered as a first-party responsive web application with application-owned identity. Customers self-enroll through Register and return through Login; Admin, Manager and Cashier are business-provisioned staff roles that sign in through the same Login surface and are routed to the management areas their role permits. Forgot Password provides account recovery, and Logout ends a session.

The storefront is publicly reachable: Home, Products / Shop, Product details page, Categories, Cart, About and Contact can be used without signing in. Checkout, Order Success, Order History and Profile require an authenticated customer so that an order, its payment status and its history remain bound to the correct person.

The management side is role-restricted. Dashboard, Customers, Reports and Settings are Admin areas; Inventory, Products, Add Product and Orders are shared by Admin and Manager; Billing is the Cashier's counter workspace (and is also reachable by Admin, who has Billing in the accepted access set).

Accepted behaviour includes: full product CRUD with image upload, price, discount, category, minimum stock and enable/disable; an inventory dashboard with totals, available stock, low-stock and out-of-stock counts, total sales, today's orders and pending orders; a nine-step admin order/product processing flow; a POS billing system with automatic subtotal, discount, tax and grand total, four payment methods, and an auto-numbered printable/downloadable invoice; automatic order IDs; automatic stock decrement on successful order; blocking of orders when stock is unavailable; low-stock warnings on the dashboard; and a customer order history linked to the logged-in customer.

Narrow exclusions and boundaries:

• Online Payment is a placeholder only. Cash on Delivery is the functional payment path.
• Google Maps on Contact is a placeholder only.
• No adjacent capabilities are added beyond the accepted shopping, inventory, billing, order-processing, authentication and dashboard scope.

2a. Product Interpretation and Delivery Boundary

Chamunda is delivered as a single first-party web application. The storefront and the back office share one product, one catalog and one order record: a customer's placed order becomes an admin order to process, and a counter sale made in Billing produces an invoice from the same product and stock data.

Access ownership is split by lifecycle, not by convention:

• Anonymous storefront — Home, Products / Shop, Product details page, Categories, Cart, About and Contact are usable before any identity exists, because browsing and cart-building are the accepted first steps of shopping.
• Anonymous identity entry — Login, Register and Forgot Password are reachable without a session, because a protected destination cannot own the interaction that establishes access to itself.
• Protected customer state — Checkout, Order Success, Order History and Profile require a signed-in customer, because an order, its payment status, its history and the customer's own details must stay bound to the right person.
• Protected staff state — Dashboard, Inventory, Products, Add Product, Orders, Billing, Customers, Reports and Settings require a signed-in staff role, with Admin, Manager and Cashier seeing the areas their role permits.

Current versus future: everything in this document is current. Online payment and the map are current placeholders, not future features. No future-horizon requirements were accepted.

2b. Source Content Inventory

Not applicable — no reference directive with content_source was supplied.

2c. Page Content and Component Coverage

Home

• Information / state: Chamunda logo/name; hero section with sweets/products; Featured Products; Popular Sweets; New Products; Special Offers; quick category buttons; business highlights; customer-friendly shopping experience; footer with About, Contact, Login, policies and useful links.
• Primary actions: "Shop Now" button; quick category buttons; product card selection; footer navigation.
• Supporting actions: Header navigation to Products / Shop, Categories, Cart, Order History, Inventory, Billing, About, Contact, Login.
• Domain entities: Product, Category, Offer.
• Component responsibilities: Hero band with headline, Shop Now and Browse Categories; product rails for Featured / Popular / New / Offers; category quick-button rail; business highlights strip; footer.
• States: Loading skeletons for product rails; empty state per rail when no products qualify; error state with retry if catalog fetch fails; success state when rails populate.

Products / Shop

• Information / state: Product grid with image, name, description, price, discount price and stock availability; active search term, category filter and sort selection.
• Primary actions: Browse products; search products; filter by category; sort by price/name/popularity; open product details; add to cart.
• Supporting actions: Clear search/filter; paginate or load more.
• Domain entities: Product, Category.
• Component responsibilities: Search field; category filter control; sort control; product card grid; pagination/load-more control.
• States: Loading grid; empty state when search/filter returns nothing; error state with retry; success state with results.

Product details page

• Information / state: Product image; product name; description; price; discount price; stock availability; quantity selector.
• Primary actions: Add to Cart; Buy Now.
• Supporting actions: Quantity increment/decrement; return to Products / Shop.
• Domain entities: Product, Category, Inventory.
• Component responsibilities: Image panel; detail panel with price and discount; stock indicator; quantity selector; Add to Cart and Buy Now buttons.
• States: Loading; out-of-stock state that disables Add to Cart and Buy Now; error state when the product cannot be loaded; success state after add-to-cart with notification.

Categories

• Information / state: The sample categories Mithai, Kaju Sweets, Bengali Sweets, Milk Sweets, Dry Fruits, Namkeen, Cakes, Snacks, Gift Boxes, Special Items, each with its product count.
• Primary actions: Select a category to view its products.
• Supporting actions: Return to Products / Shop.
• Domain entities: Category, Product.
• Component responsibilities: Category tile grid with illustrated glyphs; product count badge.
• States: Loading; empty state if a category has no products; error state with retry; success state with tiles.

Cart

• Information / state: Product image; product name; quantity +/-; price; subtotal; discount; tax; delivery charges; grand total.
• Primary actions: Remove product; clear cart; continue shopping; proceed to checkout.
• Supporting actions: Quantity increment/decrement per line.
• Domain entities: Cart, Product, Inventory.
• Component responsibilities: Line-item list; quantity steppers; totals panel showing subtotal, discount, tax, delivery charges and grand total; Remove, Clear Cart, Continue Shopping and Proceed to Checkout controls.
• States: Loading; empty-cart state with a continue-shopping prompt; error state if a line's stock is no longer sufficient; success state with recalculated totals after every change.

Checkout

• Information / state: Customer name; mobile number; email; delivery address; city; state; PIN code; order notes; payment method; order summary; total amount.
• Primary actions: Select Cash on Delivery or the online payment placeholder; "Place Order".
• Supporting actions: Edit order summary quantities; return to Cart.
• Domain entities: Order, Order Item, Customer, Payment, Inventory.
• Component responsibilities: Delivery-details form with validation; payment-method selector; order summary panel; Place Order button.
• States: Loading during submission; validation error state on required fields; stock-unavailable error state that blocks placement and explains which item is short; success state that routes to Order Success; error state with retry on submission failure.

Order Success

• Information / state: Large success icon; "Order Placed Successfully!"; order ID; customer name; order date/time; ordered products; total amount; delivery information; estimated delivery information.
• Primary actions: Track Order; View Order; Continue Shopping.
• Supporting actions: None beyond the three accepted buttons.
• Domain entities: Order, Order Item, Payment.
• Component responsibilities: Success banner; order summary block; delivery and estimated-delivery block; three action buttons.
• States: Loading while the order record is fetched; error state if the order cannot be retrieved; success state as described. The order is saved in Order History at this point.

Order History

• Information / state: Order ID; order date; products; total amount; payment status; order status. Order status supports Order Placed, Confirmed, Processing, Ready, Out for Delivery, Delivered, Cancelled.
• Primary actions: Open an order's detail; track an in-progress order.
• Supporting actions: Filter or scroll the order list.
• Domain entities: Order, Order Item, Payment.
• Component responsibilities: Order list with status stepper; payment-status badge; order detail panel.
• States: Loading; empty state when the customer has no orders; error state with retry; success state with the customer's own orders only.

Profile

• Information / state: The signed-in customer's own account details and delivery information.
• Primary actions: View and update own profile details.
• Supporting actions: Logout.
• Domain entities: Customer, User.
• Component responsibilities: Profile form; save control; logout control.
• States: Loading; validation error state; success notification on save; error state with retry.

Dashboard

• Information / state: Sales overview; orders overview; inventory overview; revenue; pending orders; completed orders; low-stock alerts; recent orders; recent transactions; sales chart; product performance chart.
• Primary actions: Open a recent order; open a low-stock product; navigate to Inventory, Orders, Products, Billing, Customers, Reports or Settings.
• Supporting actions: Change chart range if offered by the chart control.
• Domain entities: Order, Payment, Invoice, Product, Inventory.
• Component responsibilities: KPI cards for revenue, pending orders, completed orders and low-stock count; sales chart; product performance chart; recent orders list; recent transactions list; low-stock alert list.
• States: Loading; empty state when there is no sales or order data yet; low-stock warning state that highlights the low-stock card and list; error state with retry; success state with populated analytics.

Inventory

• Information / state: Total products; available stock; low stock products; out of stock products; total sales; today's orders; pending orders. Inventory table with product ID, product name, category, price, stock quantity, minimum stock, status, last updated, edit and delete.
• Primary actions: Update stock; edit product; delete product; add product.
• Supporting actions: Filter or search the inventory table.
• Domain entities: Inventory, Product, Category, Order.
• Component responsibilities: Summary tiles; inventory table with sticky header; row-level Edit and Delete actions; stock-update control.
• States: Loading; empty state when no products exist; low-stock and out-of-stock row states; confirmation dialog before delete; success/error notification after stock update or delete; error state with retry.

Products

• Information / state: The product catalog with name, SKU, category, price, discount, final price, stock quantity, minimum stock, weight, unit, availability and image.
• Primary actions: Add product; edit product; delete product; update stock; upload product image; set product price; set discount; set category; set minimum stock; enable/disable product.
• Supporting actions: Search or filter the product list.
• Domain entities: Product, Category, Inventory.
• Component responsibilities: Product list/table; row actions; enable/disable toggle; delete confirmation dialog; link to Add Product.
• States: Loading; empty state when no products exist; validation error state on edit; confirmation dialog before delete; success/error notification; error state with retry.

Add Product

• Information / state: Product name; product SKU; category; description; product image upload; price; discount; final price; stock quantity; minimum stock level; weight; unit; product availability.
• Primary actions: Save Product.
• Supporting actions: Cancel and return to Products.
• Domain entities: Product, Category, Inventory.
• Component responsibilities: Product form with validation; image upload control; computed final-price display; availability control; Save Product button.
• States: Loading during save; validation error state on required fields; success notification and return to Products on save; error state with retry.

Orders

• Information / state: Order queue with order ID, customer, items, total, payment status and current order status. Processing flow: New Order, Confirm Order, Check Inventory, Prepare Products, Update Order Status, Generate Bill, Mark Ready, Delivery, Complete Order.
• Primary actions: Confirm order; check inventory; prepare products; update order status; generate bill; mark ready; dispatch for delivery; complete order.
• Supporting actions: Open an order's detail; delete an order with confirmation.
• Domain entities: Order, Order Item, Inventory, Invoice, Payment, Customer.
• Component responsibilities: Order list; order detail panel; nine-step processing control; status stepper; Generate Bill action; delete confirmation dialog.
• States: Loading; empty state when no orders are pending; stock-shortage warning state during Check Inventory; confirmation dialog before delete; success/error notification on each status change; error state with retry.

Billing

• Information / state: Product search results; running bill lines with product, quantity, price and line total; subtotal; discount; tax; grand total; selected payment method; generated invoice with Chamunda name/logo, shop information, invoice number, date/time, customer details, product list, quantity, price, discount, tax, total, payment method and thank-you message.
• Primary actions: Search products; add products to bill; change quantity; remove products; apply discount; select payment method (Cash, UPI, Card, Other); Print Bill; Download Invoice; New Bill.
• Supporting actions: Clear the current bill via New Bill.
• Domain entities: Invoice, Product, Payment, Customer, Inventory.
• Component responsibilities: Product search grid; running bill panel; discount and tax controls; payment-method selector; live totals; invoice preview; Print Bill, Download Invoice and New Bill buttons.
• States: Loading during product search; empty bill state before any product is added; validation error state on discount or quantity input; success state with auto-generated invoice number and automatically calculated totals; error state with retry.

Customers

• Information / state: The customer records associated with orders and accounts.
• Primary actions: View a customer's details and their orders.
• Supporting actions: Search or filter the customer list.
• Domain entities: Customer, Order, User.
• Component responsibilities: Customer list; customer detail panel with order references.
• States: Loading; empty state when no customers exist; error state with retry; success state with populated records.

Reports

• Information / state: Sales, order and product performance reporting derived from accepted order, payment and product data.
• Primary actions: Review sales and product performance reporting.
• Supporting actions: Change the reporting range if offered by the report control.
• Domain entities: Order, Order Item, Payment, Invoice, Product.
• Component responsibilities: Report tables and charts; range control.
• States: Loading; empty state when no data exists for the range; error state with retry; success state with populated reports.

Settings

• Information / state: Business and application settings for the shop.
• Primary actions: View and update settings.
• Supporting actions: Save or discard changes.
• Domain entities: User, business configuration.
• Component responsibilities: Settings form; save control.
• States: Loading; validation error state; success notification on save; error state with retry.

About

• Information / state: About Chamunda; Our Story; Our Products; Our Mission; Quality & Freshness; Customer Satisfaction.
• Primary actions: Navigate to Shop or Contact from within the page.
• Supporting actions: None beyond navigation.
• Domain entities: None beyond brand content.
• Component responsibilities: Content sections for each accepted topic; navigation links.
• States: Static content; no data-loading states required.

Contact

• Information / state: Business address; phone number; email; business hours; contact form with name, email, phone and message; Google Maps placeholder.
• Primary actions: Send Message.
• Supporting actions: None beyond form submission.
• Domain entities: Contact Message.
• Component responsibilities: Business-details block; contact form with validation; Send Message button; map placeholder.
• States: Loading during submission; validation error state on required fields; success notification on send; error state with retry.

Login

• Information / state: Credential entry for returning customers and for Admin, Manager and Cashier staff.
• Primary actions: Sign in; navigate to Register; navigate to Forgot Password.
• Supporting actions: None beyond the accepted authentication links.
• Domain entities: User, Customer.
• Component responsibilities: Login form with validation; links to Register and Forgot Password.
• States: Loading during verification; validation error state; invalid-credential error state; success state that routes the customer to the storefront and the staff role to its permitted management area.

Register

• Information / state: Self-service enrollment form for customers who independently begin shopping.
• Primary actions: Create a customer account.
• Supporting actions: Navigate to Login.
• Domain entities: User, Customer.
• Component responsibilities: Registration form with validation; link to Login.
• States: Loading during creation; validation error state; duplicate-account error state; success state that signs the customer in and continues the shopping journey.

Forgot Password

• Information / state: Account-recovery entry for a forgotten credential.
• Primary actions: Request recovery for the account.
• Supporting actions: Navigate back to Login.
• Domain entities: User.
• Component responsibilities: Recovery form with validation; link back to Login.
• States: Loading during submission; validation error state; success state confirming the recovery request; error state with retry.

3. Functional Requirements

FR-01 — Branded responsive storefront (explicit) As a Customer, I should see a modern, professional, responsive Chamunda storefront that works on mobile, tablet and desktop, so that I can shop comfortably on any device.

• Trigger: I open the application.
• Observable result: The storefront renders with the Chamunda logo/name, easy navigation, smooth animations and transitions, attractive product cards and proper icons.
• Failure/recovery: If the page fails to load, I see an error state with retry.
• Continuation: I navigate to Home, Products / Shop, Categories, Cart, Order History, Inventory, Billing, About, Contact or Login from the main navigation.

FR-02 — Home page content (explicit) As a Customer, I should see a professional homepage with the Chamunda logo/name, a hero section with sweets/products, a "Shop Now" button, Featured Products, Popular Sweets, New Products, Special Offers, quick category buttons, business highlights and a customer-friendly shopping experience, so that I can immediately understand the shop and start shopping.

• Trigger: I open Home.
• Observable result: All accepted home sections render, and the footer shows About, Contact, Login, policies and useful links.
• Failure/recovery: If a product rail fails to load, that rail shows an error state with retry while the rest of the page remains usable.
• Continuation: I press "Shop Now" or a quick category button to continue shopping.

FR-03 — Browse, search, filter and sort products (explicit) As a Customer, I should browse products, search products, filter products by category and sort products by price, name or popularity, so that I can find the sweets I want.

• Trigger: I open Products / Shop or Categories and enter a search term, choose a category filter or choose a sort order.
• Observable result: The product grid updates to match my search, filter and sort selection.
• Failure/recovery: If no product matches, I see an empty state and can clear the search or filter; if the catalog fails to load, I see an error state with retry.
• Continuation: I open a product's details page or add a product to the cart.

FR-04 — Product details and purchase actions (explicit) As a Customer, I should view a product's image, name, description, price, discount price and stock availability on a product details page, choose a quantity, and use Add to Cart or Buy Now, so that I can decide and buy.

• Trigger: I open a product from the shop, a category or a home rail.
• Observable result: The product details page shows the image, name, description, price, discount price and stock availability with a quantity selector and Add to Cart and Buy Now actions.
• Failure/recovery: If the product is out of stock, Add to Cart and Buy Now are unavailable and the stock state is shown; if the product cannot be loaded, I see an error state with retry.
• Continuation: Adding to cart shows a success notification and updates the cart; Buy Now proceeds toward checkout.

FR-05 — Sweets categories (explicit) As a Customer, I should see the sample categories Mithai, Kaju Sweets, Bengali Sweets, Milk Sweets, Dry Fruits, Namkeen, Cakes, Snacks, Gift Boxes and Special Items, so that I can shop by the kind of sweet I want.

• Trigger: I open Categories or use a quick category button.
• Observable result: The accepted categories are listed and selecting one shows its products.
• Failure/recovery: If a category has no products, I see an empty state; if categories fail to load, I see an error state with retry.
• Continuation: I open a product from the selected category.

FR-06 — Cart management and totals (explicit) As a Customer, I should manage a cart showing product image, product name, quantity +/-, price, subtotal, discount, tax, delivery charges and grand total, with remove product, clear cart, continue shopping and proceed to checkout, so that I can control exactly what I am buying and what it costs.

• Trigger: I open Cart after adding products.
• Observable result: Each line shows its image, name, quantity control and price, and the totals panel shows subtotal, discount, tax, delivery charges and grand total, recalculated automatically after every change.
• Failure/recovery: If a line's stock is no longer sufficient, the cart shows an error state for that line; if the cart is empty, I see an empty state with a continue-shopping prompt.
• Continuation: I proceed to checkout, continue shopping, remove a product or clear the cart.

FR-07 — Checkout with delivery and payment details (explicit) As a Customer, I should complete checkout with customer name, mobile number, email, delivery address, city, state, PIN code, order notes and a payment method, review the order summary and total amount, and press "Place Order", so that my order can be delivered.

• Trigger: I press Proceed to Checkout from the cart.
• Observable result: The checkout page collects the accepted fields, offers Cash on Delivery and the online payment placeholder, shows the order summary and total amount, and places the order on "Place Order".
• Failure/recovery: Required fields are validated with clear messages; if stock is unavailable for an item, placement is blocked and the short item is identified; if submission fails, I see an error state with retry.
• Continuation: A successful placement routes me to Order Success and saves the order in Order History.

FR-08 — Order success confirmation (explicit) As a Customer, I should see a professional success page with a large success icon, "Order Placed Successfully!", the order ID, my name, the order date/time, the ordered products, the total amount, delivery information and estimated delivery information, with Track Order, View Order and Continue Shopping buttons, so that I know my order was received.

• Trigger: My order is placed successfully.
• Observable result: The success page shows all accepted confirmation details and the three accepted buttons, and the order is saved in Order History.
• Failure/recovery: If the order record cannot be retrieved, I see an error state with retry.
• Continuation: I track the order, view the order, or continue shopping.

FR-09 — Order history linked to the logged-in customer (explicit) As a Customer, I should see my own orders in Order History with order ID, order date, products, total amount, payment status and order status, so that I can follow my purchases.

• Trigger: I open Order History while signed in.
• Observable result: Only my orders are listed, each showing order ID, order date, products, total amount, payment status and order status.
• Failure/recovery: If I have no orders, I see an empty state; if the list fails to load, I see an error state with retry.
• Continuation: I open an order's detail or track an in-progress order.

FR-10 — Order status lifecycle (explicit) As a Customer, I should see my order move through Order Placed, Confirmed, Processing, Ready, Out for Delivery, Delivered and Cancelled, so that I know exactly where my order stands.

• Trigger: A staff member advances or cancels my order.
• Observable result: The order's status reflects one of the accepted values and is visible in Order History.
• Failure/recovery: A cancelled order is shown as cancelled rather than as a completed step.
• Continuation: I continue to track the order until it is delivered or cancelled.

FR-11 — Admin order/product processing flow (explicit) As an Admin, I should process each order through New Order, Confirm Order, Check Inventory, Prepare Products, Update Order Status, Generate Bill, Mark Ready, Delivery and Complete Order, so that every order is fulfilled correctly.

• Trigger: A new order appears in the Orders queue.
• Observable result: Each step records its outcome on the order, the order status advances accordingly, and the customer's Order History reflects the new status.
• Failure/recovery: If Check Inventory finds insufficient stock, the shortage is surfaced and the order cannot advance until it is resolved.
• Continuation: The order proceeds to Generate Bill, Mark