Waste API - Create API to support the creation of a Waste Adjustment

Add support to create a Waste Adjustment using the API

• Scan item
• CFA send item code to InFORM
  • Note: We will NOT be sending a list of items that are available for Waste, as all items are available for waste within the MxC application
    • The only exception is DwarfHouse items, that should NOT be available at NON DH restaurants
• InFORM returns item detail/list of items
• User manipulates data on HHD (incl Reason Code)
• CFA sends adjustment to InFORM

Support selection of Raw & Finished Items

HLE assumes that there will be some work required to change the API

So I don’t recall the exact use case for this functionality because we talked about several but here are some of the ones I recall and the net result.

1. We talked about covering inventory “adjustments” via an external app through some kind of counts API. For example, if we start using RFID and create an app that allows team members to walk through the back of the restaurant and just scan areas, we would upload the counts for all items scanned at once via an API. This wouldn’t necessarily be by item but, supposing they only scan one item, it could. Regardless, it should be some kind of count.
2. We also discussed decrementing by item as it’s consumed or introduced as WIP. For example, as a team member starts to use a bag of chicken, we thought it would be good to deplete the inventory based on some kind of scan at the prep table. We decided this was nonsense (my words) because it would result in “double depleting” the inventory.
3. We discussed the ability to scan an item as waste. The use case here was similar to #2 but, instead of depleting inventory due to consumption, we would be depleting based on an item being considered waste and would want to track it as such. The best example I can give for this would be a bag of thawed filets that has exceeded its expiration date. When an team member puts a bag of filets on prep table, we would scan it somehow. If our system shows that it’s past the expiration date, we’d let the team member know they need to toss it. We’d want to let Inform know we wasted that bag.
4. We discussed the ability to reverse a depletion transaction. I think we decided this could likely be handled by other means but it was one of the use cases we discussed.

#3 is likely the main use case for this functionality and I would expect it to get used with the PDC PoC. Shelf life on the chicken is going to be really short by the time we get it to the restaurant. We want to make sure we track expiration dates really closely and provide the team member immediate feedback prior to using the product. If we can also keep them from having to manually go and update Inform with what they are tossing, that would be optimal.