Situation
An operational inventory system has grown through urgent patches. Stock adjustments are difficult to trace, warehouse staff use spreadsheets beside the application, and the original deployment process is no longer understood.
Review milestone
The first milestone reproduces the application, maps stock-changing actions and reconciles a controlled sample of inventory records. Permission boundaries, database constraints and deployment dependencies are documented before feature work begins.
Stabilisation milestone
- Add idempotent stock movement records
- Introduce clear adjustment reasons and audit history
- Repair the highest-risk queries and missing constraints
- Create repeatable deployment and rollback notes
- Add tests around receive, dispatch, transfer and adjustment flows
Expansion milestone
A focused UniApp client supports scanning, receiving and dispatch. The mobile client uses the same backend rules rather than creating a second source of inventory truth.
Acceptance evidence
The delivery is accepted against reproducible stock scenarios, permission tests, failed-request behaviour and a documented release rehearsal—not against invented percentage improvements.