You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My client has a lot of big stock, transformers, generators, big electrical/construction stuff. It's common for one inventory item to have many locations (wherever it fits pretty much), so in it's current form, the package doesn't work for my situation.
Inventory can be big, or it can be extremely big, so the "locations" of where stock can be are pretty much endless.
Rather than re-write any code, one thing I have been toying with is generating a unique location per a stocks aisle, row, and bin. Stock can span over one single aisle, or can span over multiple.
So if I have a 10x Item 1 at row 1, section A-B (we call aisle section), it'll generate a new location with the name of: 1A-B. That way we could check to see if location 1A-B is free, and if it's not, then throw a StockAlreadyExistsException
The only downside that I can foresee is that if there's stock on Row 1 A-B and a user tries to add stock on Row 1 A, then it wouldn't consider Row 1 A-B as an existing location. But maybe I can just leave that up to the client take those precautions.
Do you have any ideas that may help?
Cheers, Steve!
The text was updated successfully, but these errors were encountered:
Hey Steve,
Great package!
My client has a lot of big stock, transformers, generators, big electrical/construction stuff. It's common for one inventory item to have many locations (wherever it fits pretty much), so in it's current form, the package doesn't work for my situation.
Inventory can be big, or it can be extremely big, so the "locations" of where stock can be are pretty much endless.
Rather than re-write any code, one thing I have been toying with is generating a unique location per a stocks
aisle
,row
, andbin
. Stock can span over one single aisle, or can span over multiple.So if I have a
10x Item 1
atrow 1
,section A-B
(we call aisle section), it'll generate a new location with the name of:1A-B
. That way we could check to see if location 1A-B is free, and if it's not, then throw aStockAlreadyExistsException
The only downside that I can foresee is that if there's stock on Row 1 A-B and a user tries to add stock on Row 1 A, then it wouldn't consider Row 1 A-B as an existing location. But maybe I can just leave that up to the client take those precautions.
Do you have any ideas that may help?
Cheers, Steve!
The text was updated successfully, but these errors were encountered: