OMS-AURA System Requirements Document

1. Introduction

The OMS-AURA project aims to develop a comprehensive SaaS platform named AARA Exchange Order Management System. This system is designed to streamline the order processing of jerseys and sports merchandise by integrating with a WordPress WooCommerce website. The platform will provide a centralized dashboard for managing various aspects of the order lifecycle, including customers, dealers, production, shipping, returns, and future accounting modules.

2. System Overview

OMS-AURA will serve as a robust order management system that automatically syncs orders from a WooCommerce website. It will offer real-time updates and a centralized dashboard to manage the entire order process efficiently. The system will cater to different customer types, support dealer-specific functionalities, and integrate with multiple shipping partners. Additionally, it will be built on a scalable architecture to accommodate future modules and integrations.

3. Functional Requirements

• As a Regular Customer, I should be able to place orders on the WooCommerce website.
• As a Regular Customer, I should be able to track my order history and manage returns and replacements.
• As a Partner Customer, I should be able to access dealer-specific pricing and manage bulk orders.
• As a Partner Customer, I should be able to track credit (future module) and view dedicated order history and performance.
• As an Admin, I should be able to view and manage all orders through a centralized dashboard.
• As an Admin, I should be able to modify product-to-dealer assignments from settings.
• As a Dealer, I should be able to log in to a separate portal to view assigned orders and update production status.
• As a Dealer, I should be able to upload proof images, mark completed orders, and update shipping details.
• As a User, I should receive automatic notifications via WhatsApp, Email, and SMS for various order events.
• As an Admin, I should be able to integrate with shipping partners for automatic AWB generation and tracking updates.
• As an Admin, I should be able to view live dashboard KPIs and export reports to Excel/PDF.
• As a Developer, I should be able to add future modules without affecting existing functionality.

4. User Personas

• Regular Customer: Individual customers purchasing at standard retail pricing.
• Partner Customer: Dealers or wholesale customers with specific pricing and bulk order management needs.
• Admin: Users with full access to manage orders, customers, dealers, and system settings.
• Dealer: Users responsible for handling production and shipping of assigned orders.

5. Core User Flows

• Regular Customer places an order -> Payment completed via Razorpay -> Order syncs to OMS-AURA -> Customer tracks order history.
• Partner Customer places a bulk order -> Order syncs to OMS-AURA -> Partner Customer tracks order performance.
• Admin views order dashboard -> Modifies dealer assignments -> Manages shipping and returns.
• Dealer logs in -> Views assigned orders -> Updates production status -> Marks orders as completed.

6. Visuals Colors and Theme

• primary: #1A73E8 (Deep Blue)
• primary_light: #E8F0FE (Light Blue)
• secondary: #FF6F61 (Coral)
• accent: #FFD700 (Gold)
• highlight: #FFA500 (Orange)
• bg: #FFFFFF (White)
• surface: rgba(240, 240, 240, 0.8)
• text: #333333 (Dark Gray)
• text_muted: #777777 (Gray)
• border: rgba(200, 200, 200, 0.5)

7. Signature Design Concept

The OMS-AURA landing page will feature an interactive 3D sports arena using @react-three/fiber and @react-three/drei. Users can navigate through different sections of the arena, each representing a feature of the platform. As users hover over sections, detailed information will animate into view, providing an immersive experience. The arena will dynamically adjust lighting and colors based on user interactions, creating a vibrant and engaging first impression.

8. Interaction Model & Motion Direction

The landing page will utilize a "parallax" interaction model, with layered depth effects as users scroll through the page. Decorative elements will move at different speeds to create a sense of depth, while key content remains in the natural flow. Internal pages will adopt a "static" model for clarity and ease of navigation.

9. Non-Functional Requirements

• The system must support real-time updates using WebSockets.
• The architecture should be modular to allow for future scalability.
• The platform must ensure secure access control using JWT and role-based authentication.

10. Tech Stack

• Frontend: React.js / Next.js
• Backend: Node.js / NestJS
• Database: PostgreSQL
• Real-time Updates: WebSockets / Socket.IO
• Authentication: JWT + Role-Based Access
• Integrations: WooCommerce API, Razorpay API, WhatsApp API, Shipping APIs, Google Analytics, Power BI

11. Assumptions and Constraints

• The system will initially integrate with specified shipping partners: Shiprocket, Delhivery, DTDC, and Xpressbees.
• Future modules will be developed as per business needs and integrated seamlessly into the existing architecture.

12. Glossary

• AWB: Air Waybill, a document for tracking shipments.
• KPI: Key Performance Indicator, a measurable value that demonstrates how effectively a company is achieving key business objectives.
• JWT: JSON Web Token, a compact, URL-safe means of representing claims to be transferred between two parties.
• API: Application Programming Interface, a set of functions and procedures allowing the creation of applications that access the features or data of an operating system, application, or other service.