Probably one of the most frustrating issues we currently have is that of single line backorders sent separately by post. They are time consuming and inefficient to handle for both retailer and distributor and as a consequence are a high priority for us to resolve.
Progress to date – we closed a significant gap back in mid January where stock was allocated to backorders but they were not shipped for a short period of time. A number of these backorders combined with normal orders in the usual manner, however a significant portion did not (as previous blog posts relate) and continue not to do so. However with better visibility of the specific causes we have made good progress in pinpointing the reasons and seeking a solution. There are around seven possible and largely related scenarios of which the following is an example concerning Synergi orders as follows:
· Place a Synergi order for 30 articles and select “Don’t send backorders with this order”
· Your order arrives with 25 of the 30 articles and no backorders. So far so good.
· However – the 5 outstanding backorders are each being created in SAP with the same effective instruction – “Don’t send backorders with this order”
· So when you place your next order and we now have stock for say backorder A, SAP triggers backorder A to be released, but as it carries the instruction “Don’t send backorders with this order” it sends Backorder A separately from your stock order.
In practice the logic is more complex as in SAP the setting is: Can this order (or backorder) be combined with another order, which is not the same concept of backorders as we currently understand them.
In order to minimise the incidence of creating single line backorders under this scenario you may wish to avoid using the “Don’t send backorders with this order” option in Synergi. We realise this has operational implications, which are not perfect so you will need to judge the benefits for your store. We are also exploring the possibility of amending backorders already created in this manner for your store.
We will update on progress as soon as we have a solution in place.