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.

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 all works fine until the below scenario

Scenario

• Let's say on a SO there are 2x BOM skus (or pretend you are picking multiple orders per round where there are multiple BOM skus)
• Let's say 1 of the BOM skus on the Sale Order, was physically created ahead of time, via the Production > Assembly. The staff member has made the BOM kit in advanced, by collecting and packaging all the items together, and has put the BOM SKU / barcode on it, and scanned it into a bin location.
• Let's say the other BOM sku on the Sale Order, was from an Auto-Assembly created job.

The Issue

• In the above scenario, we would want to scan/pick the already physically made BOM sku
• In the above scenario, we would need to individually pick/scan each item for the auto-assembly/electronically made BOM sku
• In the current implementation of the Expand / Collapse button this is 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.

Potential solution

• My initital thought was in the WMS Pick, for the Expand/Collapse button - to only apply to not already picked items. This would then not ‘undo’ the BOM that was picked.
• My secondary thought, is that perhaps the WMS should simply list the individual items for a BOM sku (as it could know that the BOM was created by the system/an auto-assembly job) and just list the BOM sku for when the BOM was created manually/physically by a user on the web platform. This would also make sense because we'd have scanned a bin location for the physically made BOM sku. But the sales platform is expecting the BOM sku and barcode, so I'm not entirely sure if this secondary thought/suggestion would work.