RequireX
Softworks
13 req · 1 need inputSoftworks Retail App — Brief
Softworks Retail App·Brief Version 2·13 requirements·shared for review
Summary
REQ-0001Approved
Softworks requires a mobile-first retail ordering application that enables store managers and sales staff to place, track, and fulfil product orders across multiple store locations from a single interface.
REQ-0002Approved
The system replaces the current spreadsheet-based workflow and must support offline operation for store staff with intermittent connectivity, synchronising automatically when connectivity is restored.
Goals
REQ-0003Approved
Reduce order processing time from an average of 45 minutes to under 5 minutes per order by eliminating manual spreadsheet entry and email-based approval chains.
REQ-0004Approved
Provide real-time inventory visibility across all store locations so that managers can make informed purchasing decisions without contacting head office.
Main Features
REQ-0005In review
Order management module: create, edit, and submit purchase orders with product search, quantity entry, and supplier selection; orders route through a configurable approval workflow before dispatch.
REQ-0006In review
Inventory tracking dashboard: real-time stock levels per SKU per store location, low-stock alerts configurable per product category, and one-click reorder from the dashboard.
REQ-0007In review
Reporting and analytics: weekly and monthly sales and order reports exportable to PDF and CSV; regional manager view aggregating data across assigned store clusters.
Functional Requirements
REQ-0008In review
Role-based access control with four roles — Store Staff, Store Manager, Regional Manager, and Admin — each with distinct permissions for order creation, approval, reporting, and user management.
REQ-0009In review
Offline mode: the application must function without network connectivity for order creation and inventory viewing, queuing changes locally and syncing to the server when connectivity is restored.
Non-Functional Requirements
REQ-0010Approved
All API responses must complete in under 2 seconds at the 95th percentile under a sustained load of 200 concurrent users. The application must achieve 99.5% uptime measured monthly.
Ambiguities
Q-0001In review
The client specified offline sync but provided no conflict resolution strategy. This will affect data integrity for shared inventory across store clusters.
Question
When two store devices modify the same inventory record while offline and then sync simultaneously, which record should take precedence — the most recent timestamp, the higher quantity, or should conflicts be flagged for manual resolution?
Q-0002In review
The voice note and WhatsApp summary reference both 'store inventory' and 'central warehouse stock' without distinguishing whether these are separate ledgers or the same pool.
Question
For multi-store inventory, does each store maintain its own independent stock count, or is there a shared pool that individual locations draw from?
Follow-up questions
Q-0003In review
The requirements deck mentions report exports but does not specify integration targets. Supporting a native connector vs. CSV export is a significant scope difference.
Question
Beyond PDF and CSV, are there specific BI tools (Power BI, Tableau, Google Looker) that regional managers currently use that the export format should be compatible with?
Diagrams1
FlowchartOrder Processing Flow
End-to-end order lifecycle from creation through approval and dispatch, including the offline queue path.