Notification of near expiry


As a storeroom manager, I want to get notifications for when a product is near expiry so that I can make sure to use it/distribute it first and be attentive to its expiration date.

Acceptance criteria
Verify That:
*Close to expiry notification for a product is 6 months away from expiration (formula: expiration date - Today's date = 6 months)
*Recipient #1 is the user with "Edit stock inventories" right for the facility/program
*Recipient #2 is the user at the next level up who oversees that facility's stock.
*Notification shows Product Name, lot information, date of expiry
*When the user receives a notification, they can click on a link to view the bin card for the close to expiry product.
*Clicking on the second link takes them to an emergency requisition form pre-selected with the facility and program that has no stock
*Email body text appears as follows:
Email Template
Subject: CLOSE TO EXPIRY Attention Required: <Facility name>, <Product name>
Dear <user_name>:
This email is informing you that the product <Product Name> with lot number <Lot number> in <program name> at <facility name> will expire in 6 months. Its expiration date is <expiration date>.
Login to view the bin card for this product.
View bin card for <orderable name>: <URL to View BIN CARD>
Thank you
– END –


Joanna Szymańska
March 19, 2019, 2:45 PM

I see, so everything works correctly.

Chongsun Ahn
March 19, 2019, 2:43 PM

Yes, it is configured on the test server to check and potentially notify every minute for testing. A normal production server would configure it to check once a day, but I assume you would not want to wait a day to see if this ticket was correct for QA purposes.

Joanna Szymańska
March 19, 2019, 2:40 PM

But I just noticed that it receives the same message every minute:

Joanna Szymańska
March 19, 2019, 2:21 PM

You're absolutely right, I'm checking it again.

I checked it on the UAT and the test server, everything works correctly, I receive notifications. I apologize for this mistake.

Chongsun Ahn
March 19, 2019, 2:12 PM

Thanks. Did you update the lot, using PUT /api/lots/af804501-ef41-4367-9733-83b73e7c0a4b, and include the same id? It looks like the id in the screenshot you provided is different. Also, which server did you test on?

I notice the expiration date is in the past, rather than six months from today? It will not send an email if the lot has already expired.



Chongsun Ahn


Rachel Powers