Program supplies with the same discipline as commercial stock

Partly, and the boundary is worth knowing before you plan a distribution. Issuing stock and taking it back in both work offline on mobile, as do transfers between stores and asset movements — so day-to-day movement at a remote store stays in the system rather than on paper. A stock count and a purchase-order receipt are not offline, because both have to agree with a shared current state rather than simply recording what is in somebody's hands. Schedule counts for a day when the team has signal.

Yes — batches carry expiry dates, issue logic can enforce first-expiry-first-out, and expiring stock is flagged before it becomes a write-off.

Partly, and the distinction matters for a donor report. There is no beneficiary record in the product — no person, no household, no registration list — so you cannot report distributions per beneficiary or deduplicate a recipient across two distributions. What exists is the stock side: an issue out of a store carries a quantity, a date, a reason and the person who made it, and it can be coded to a project standing in for the programme and to the location it went out from. That gives you what left, from where, when and on whose authority, which is the evidence chain for the goods. Who received them is a beneficiary management system's job and we would rather you ran one than expected this to be one.

Adjustments require a reason from your configured list and an authorized user; large variances can require approval. Every adjustment is attributable and reportable.