Feature Request - WMS Pick - Expand Collapse BOM behaviour
Hi Guys,
This is in regards to the Expand / Collapse button on the WMS during the PICK process, and why I believe it needs a total overhaul / rework.
Current Implementation
- For BOM sku's, we have Auto-Assembly/Kit enabled, in order to display the available/possible quantities for the BOM sku on Shopify
- When an order is made, the system auto-creates and completes the assembly job, and the BOM sku in the On Hand quantity increases
- In real life, this is not made in advanced into the BOM/Kit, its only electronically.
- On the WMS > Pick, we use the Expand Button, and we can scan/pick the invididual items that make up the BOM sku.
- This works somewhat OK but it has problems.
Scenario
Picking a single Sale Order or Multiple Sake Orders per pick round
- Let's say on a single Sale Order, there are 2x BOM skus
- 1x BOM → Manually created via Production > Assembly. The staff member has made the BOM kit in advanced, by collecting the individual items and packaging all the items together in a bag and has applied the BOM sku / barcode on it, and scanned it into a bin location.
- 1x BOM → Electronically created via the Auto-Assembly function
The Issue in Pick
- In the above scenario, we would want to scan and pick the already physically made BOM sku
- In the above scenario, we would need to individually pick and scan each item for the auto-assembly / electronically made BOM sku
- In the current implementation of the Expand / Collapse button, this is simply not possible.
- This is because if you pick the BOM sku, and then you press the Expand button for the BOM that was auto-assembled, the current implementation of the WMS will undo the pick of the first BOM sku.
- The issue becomes amplified when you're picking multiple orders per round as there may be more BOM skus.
The Issue in Pack
Electronically Created BOM
- For electronically created BOM via the Auto-Assembly function, these are picked individually
- In the PACK stage, it only lists the 1x BOM SKU
- We're unable to scan any of the individual items, that would make up the BOM sku.
- Currently, we're copy/pasting the BOM sku on the WMS Pack screen.
- Its not good.
Potential Solution
Therefore, I think the right path going forward is this;
System to distinguish the type of BOM
- The system can could distinguish between BOM that were made “electronically” vs “manually” simply by the user name
- “System” user → Auto-Assembly
- Every other user name → Manual-Assembly
For any Auto-Assembly / electronically created BOMs
- The WMS → Pick → Should list the individually items to pick
- The WMS → Pack → Should list the individually items to pack
For any Manual-Assembly / manually created BOMs
- The WMS → Pick → Should list the BOM item/s to pick
- The WMS → Pack → Should list the BOM item/s to pack
Removal
- Remove → The expand / collapse button could then be removed entirely
Notes
- Electornically created BOMs → Individual items that make up the bundle, will most likely need to reference the BOM sku, ie - Part of BOM xxxxx, which is then used to fulfill the sales platform bom sku.
Summary
Basically this fixes quite a few problems.
- Pick → Currently, the WMS user has to decide whether to expand or collapse. This does not really make sense, as how would the user know what they're supposed to do, unless they have checked all BOM in advance on the web platform.
- Pick → Currently, the WMS you cannot pick both types of BOM on a single order (electronic and manually created), because pressing the button, after collecting the first BOM, will undo the other BOM.
- Pack → Picking items individually via the expand button in the Pick task, but then only seeing the BOM sku in the pack task results in not being able to scan the items individually. We're literally copy/pasting the BOM sku on the WMS, there's no validation of the items in this stage.
Related to
Comments
1 comment
Following… We also have “fun” with the balancing act of stock availability on the storefront (Shopify) vs picking, stock control, etc.
Please sign in to leave a comment.