Removing Inventory items when Lost/Damaged.
Hello,
Wondering how people properly deal with inventory items that are Lost/Damaged.
If an item is damaged we typically mark it as OOC and remove it from our physical inventory. However, we never delete the item (serialized or not) from the inventory database. Should we be doing that? I mean the item is damaged/no longer usable so why am I keeping it as an inventory item?
For Example, I have an inventory Item model: Amplifier, Qty:2. One gets damaged beyond repair, so I mark that serial number/barcode OOC. At what point should I delete that serial/barcode from my inventory?
I know about the OOC and Presumed Missing Reports, but when do you physically delete those items from inventory? More so for OOC Items as Presumed Missing items may come back one day.
Thanks
-
Official comment
Hey Justin,
I generally recommend running the OOC commission report as often as you feel is necessary, maybe once per quarter or once per year, storing the report either digitally or physically, and then deleting those OOC Units. Deleted Units can always be recovered through the Inventory Manager if need be, but that method will allow you to keep records within particular timeframes as well as clean up your Inventory Units.
Thanks,
Nick Nazario - Customer Success Manager
Comment actions -
Hi Justin!
I feel like we developed our own strategy based on Flex's own training videos/streams that they used to do.We do everything in our inventory via "Maintenance Procedures", never having people directly create OOC records (only via the maintenance procedures).
If we're taking something from OOC into a decommissioned state, we have a maintenance procedure that is called "To Be Decommissioned", that our team runs and recommissions the fixture at the same time. We then edit the serial unit, and decommission the product there.
That way, OOC is "things we expect to be able to repair at sometime" and Decommissioned is "things we're not going to repair AND/OR things we're not going to use anymore"
Hope this helps!
Please sign in to leave a comment.
Comments
2 comments