Currently if a bin has a [Blank] warehouse class code, then only items with a [Blank] warehouse class code can be moved into it.

It would be useful in many scenarios if BC instead treated [Blank] on either an Item or a Bin as a wildcard.

Say we may have a production facility where we are combining frozen and ambient products, we never want the frozen products put in the 'Ambient' store, and vice-versa, so we'll set the Warehouse Class Code on storage Zones, Bins and Items to 'Frozen' or 'Ambient' as appropriate.

Now we have a problem: what Warehouse Class Code do we put on our Receipt Bin, To-Production Bin, or Shipment Bin (etc)? It's valid for both frozen and ambient items to be moved into these areas. (We can't do much production if they're never in the same place at the same time!) Neither 'Ambient', nor 'Frozen' nor [blank] will work.

Moreover, there's not an 'OnBeforeCheckWarehouseClassCode(var handled)' event to allow us to easily extend this behaviour for customers.

I would suggest a good solution would be adding a 'Bin Class Code policy' to the Location, analogous to the 'Bin Capacity Policy' field, to allow users to switch between the current 'strict' handling to e.g. a 'permissive' mode where [Blank] is treated as a wildcard on both the Item and Bin (i.e. [blank] item can go anywhere, [blank] bin code can store anything.) Why not even add a 'None' option so warehouse class code can then be used for information only? (also for consistency with Capacity) If the default were 'Strict' then this would maintain backward compatibility.