Inventory Management: Last Mile Delivery
Last updated
Was this helpful?
v1.2
Last updated
Was this helpful?
This document describes the need and scope of adding a module for tracking resources till the last mile delivery within V2.0, explaining the module’s features, specifications, purpose, and functionality. It also provides the descriptive view of the application along with the specification of each element.
In health campaigns, it is crucial to keep track of the resources delivered to prevent stock mis-handlings and for maximising the coverage. The form helps to track the resource till the last mile delivery, that is, it captures the stock till it reaches the distributor, and the distributor can record the quantity of stock received along with other stock transactions.
This document is intended for the engineering and platform (tech teams), product management and implementation teams to agree on requirements for the Health Campaign Management Platform (HCM).
Tracking stock till the last mile
Capture stock details till the end user to keep a track of the transactions that take place
Enable actors to record the stock transactions during a campaign
Ensure the safety of stock
Keep a track of the stock count and verify from both ends (received versus issued) to prevent the misuse of stocks
Sr. No.
Theme
Assumption
1
Manage Stock
The distributor must record the stock details that is received, consumed, returned, or damaged/lost.
The distributor must enter the supervisor details in case the stock is issued by him/her.
For v2, stock used will be automatically calculated from the delivery transactions only if the SKU of the resource received from the warehouse is the same as the SKU distributed to the beneficiary. For example, if a field team received bed nets from the upstream and distributed the same unit (that is, bed nets), the app will automatically calculate the stock used. However, if the drug received from the warehouse is in a box and drug distributed are individual capsules/ tablets, the app will not automatically calculate usage.
Turning off the auto-calculation logic must be done during the implementation phase.
Field
Data type
Data validation
Required (Y/N)
Comments
Manage stock
Button
The user must record the stock transaction.
NA
Date of receipt
Date
The date is populated by the system and must be non-editable. Applicable for all transaction types.
Y
Administrative unit
String
The unit is populated by the system and must be non-editable.
Y
The user can change the boundary from the boundary picker.
Team identifier
String
The system must populate the identifier from the user’s profile and it must be editable.
Y
Select product
Dropdown
Y
Received from
Search-based dropdown
Y
Supervisor’s name
String
If the stock is received from a supervisor, enter his/her name.
Y
Quantity received
Numeric
Y
Comments
String
N
Find the mock-ups below:
After logging into the application, the user lands on this screen which displays daily performance (number of households registered). The progress bar must reset daily at 00:00 hours, and start from 0 registrations. The action buttons related to the beneficiary are present which include:
Beneficiaries
View Reports
Sync Data
Call Supervisor
File Complaint
Manage Stock
On the bottom, there is a card that shows how many records are unsynced for the user’s convenience to sync data. If all the records are synced, then the card must say “All records are synced”.
The help button is on every screen of the application, and by clicking on it, a user can get a walkthrough of the elements on that screen.
On the top right, the administrative area assigned to the user is displayed which will be based on the level of hierarchy.
The hamburger button on the top left corner covers some other actions mentioned further.
This includes all the stock transactions that can be captured by the distributor.
The transaction details are captured on this screen. The date and administrative unit fields are auto captured by the system and are non-editable. The team code/identifier is captured from the user profile and it must be editable.
The stock related details are captured on this screen. “Select product” is a dropdown field that includes the resource that has been received. “Received from” is a search-based dropdown field, clicking on which navigates the user to the search facility screen that includes the facilities along with ‘Supervisor’ as the value. If the user selects ‘Supervisor’ then he/she must enter the supervisor’s name. The user must enter the quantity received, and if any additional comments are needed, they can be added.
Once the user clicks on ‘Submit’, the confirmation pop-up appears. If the user clicks on the ‘Submit’ button, the acknowledgement screen appears and ‘Cancel’ takes the user back to the previous screen.
This screen includes all the fields except for the facility field.
