Current Problem
At present when a dispatch note is generated it can split a sku into multiple entries if it has been picked in several locations. This is unnecessarily confusing for the customer. |
|
Idea to resolve Problem | No single sku should be split into multiple lines on a dispatch note. |
Could not agree more with the previous comment!
So strange that there is not a separate despatch note to picking list - and if we want a custom despatch note it is £100pm.... madness
I think that the problem is Mintsoft's standard 'DespatchNote' format.
In my opinion, the system should be set up to produce a "picking note" and a "delivery note" for each order. The picking note (for use in the warehouse) should display different lines for each location a SKU is to be picked from, but the delivery note (to be sent to the customer) should show a single line for each SKU (unless they need to be split out for BBE/batch purposes).
The fact that these two documents are not a standard feature of a warehouse management system is very odd.
I agree with this too. We have had a few customers saying orders are wrong to then email back 10 mins later to say there were actually 2 or more entries on the list. If it is all the same SKU with no other information (batch etc) then it should be grouped together!
@Guest I can understand why it would be important for batches/BBE but for all other SKU it should really just be one entry.
At present we have a client complaining that they have customers who are thinking their orders are incorrect due to the current format.
I think this is particularly relevant for batch or date controlled products as you could have a customer receiving the same product with two different batches / BBE date which would make recalling the product more challenging.
Would it not be more sensible to ensure that if the product is controlled in this way, the line should be allocated to one location? If it's just a t-shirt or another 'basic' product it's not too bad (in my opinion) but I can see how it could be confusing.