Cross docking to specific location per transfer-to-warehouse.

The cross dock template header query is only on items, not on demand.

If the supplied item fits in query of the cross dock template header, the logic checks if the supplying order fits the supply source query.

If not, there is no further validation for the next cross dock template (although there is a sequence number which suggests that it behaves like location directives).

The work template for cross dock can filter on the To warehouse in the temp work transactions, but unfortunately it does not support a directive code to determine the to location directive. The directive code comes from the cross dock template which is the wrong place because the logic does not traverse multiple cross dock templates.

As far as I remember, the to-warehouse was not even filled in the temp work transactions for cross docking.

I raised a case, but it was declined. The advice from MS:

when you want to cross dock to multiple warehouses, use the commerce cross docking.

But this would require a totally different setup and will create transfer orders through a push mechanism instead of using a pull mechanism.

My suggestion is to enable a directive code on the work template (to be filtered on the temp work transactions to-warehouse which should be filled for cross docking as well).

And align the sequence numbering for cross dock templates with the traversing sequence numbering logic on location directives, work templates etc.