| Table of Contents |
|---|
...
- String lotCode (required—if the shipment really does not have a code, and only has an expiration date, then users could paste that date into this code field)
- Date expirationDate (optional)
- Date manufactureDate (optional)
- reference to a TradeItem (required) — this object gives us access to the Manufacturer name, etc, which will be helpful for display. (in V2 this was a reference to a product)
- boolean active flag — potentially a future feature to be able to set a Lot as inactive after it has gone out of circulation; or maybe this is connected to how you archive the lot instead of a DELETE endpoint
- UUID will get assigned to the Lot in ReferenceData, but it won't be visible to the user
...
- Audit Log: ability to see the history of when a Lot was created, edited (when and by whom), de-activated. The would show us the life-cycle of each Lot. To our knowledge, this feature is not captured in the current Roadmap; it's just an idea.
- CSV uploads (we have other tickets in Roadmap for CSV uploads, but uploading Lots are not yet their own ticket)
- Potentially look into allowing allowing end users to add in lots/tradeItems. 3.1 aims to achieve lot management centrally.
Process to Configure Lot
...
Feature
Why we need lot feature?Lot feature provides
Being able to track lots provides us with two new
...
pieces of data: lot number and expiry date.
...
Other fields may be added, but for now we are focusing on these two. The lot number data allows decision makers to track orderables/products at
...
the lot
...
level and also allows warehouse managers to recall orderables if there is an issue for a
...
specific lot. The Expiry date data will not only
...
provide the storeroom managers
...
with the information on when orderables have or will expire (reduce wastage) but also allows the decision makers to implement the FEFO process.
How do we balance the usability and implementation custom?
...