Clear, authoritative answers regarding the SRS scope, business logic, offline behaviour, GPS check-in rules, and platform constraints.
Under SRS Section 2.4 and Section 14.1 (Exclusions), the agreed MVP release focuses exclusively on an Android salesman mobile application and a responsive web administration portal. Distributor-side status updates are entered internally by authorized operators. Additional platforms like iOS or external portals can be introduced in subsequent phases without disrupting the core order schema.
The app calculates the distance between the device fix and the stored shop coordinates using the spherical Haversine formula (FR-GPS-002). Standard check-in requires distance ≤ 50–100m (configurable) and reported accuracy ≤ 30m. If road repairs or waterlogging prevent reaching within the radius, the salesman submits a geo-tagged Exception Request with a mandatory operational reason. A Sales Manager or Super Admin must review and approve this exception before the visit is verified (BR-03).
No. SRS Requirement FR-GPS-009 & Section 13.3 explicitly state that the system shall not represent GPS as foolproof proof against all forms of location spoofing or simulated device mocks. The platform validates distance and device-reported accuracy flags as standard operational guardrails rather than a dedicated anti-fraud hardware layer.
No. In strict accordance with Business Rule BR-08 and FR-PROD-006, inventory counts are manually entered or adjusted by authorized operations staff. Stock is explicitly labeled as "Manually Maintained Stock (Indicative Only)" with the exact last-updated timestamp and updater identity. It must never be represented to sales reps as guaranteed live warehouse inventory.
The Android app caches the salesman's assigned shop routes and product catalogs locally (FR-OFF-001). Draft orders can be prepared offline and stored in secure device storage. Under BR-09, offline drafts remain local and are never reported as submitted orders. Upon regaining connectivity, the app synchronizes drafts, and the server validates current prices and distributor mappings before final submission.
Never. Under Requirement FR-ORD-011, submitted orders preserve immutable snapshots of unit prices, applied discounts, and GST tax percentages at the moment of submission. Future adjustments to master product catalog prices will never rewrite historical order records.
No. Business Rule BR-10 enforces an explicit finite state machine. The order lifecycle proceeds only along permitted transitions: Draft → Submitted → Accepted → Processing → Dispatched → Delivered. Terminal states (Delivered, Rejected, Cancelled) cannot be transitioned. Cancellations and rejections require documented reasons and authorized role credentials.
A Node.js / Express REST API backed by a PostgreSQL database, served over HTTPS (NFR-SEC-01). The same API powers the web administration portal and the Android field-sales app. The server is the single authority for prices, taxes, permissions and order status, and it ships with versioned database migrations, a Docker deployment and published API documentation.
Our technical architecture team can review your distribution workflow and route structure.