Overview

Although the distribution solution talks mostly about replenishment to stock buffers, sometimes we will need to make replenishment to orders.

Let's take a simple example, in which a customer enters a shop and places an order for an SKU. three different scenarios can occur:

The easiest one will be if this SKU is kept as MTA. In this situation, we will supply to the client the quantity he desires from our Stock Buffer. As a result, the inventory at the shop will decrease, and Symphony will issue a replenishment in order to fulfill the buffer.
But, what if the quantity that this client wants is relatively large? Let's assume that we keep a buffer of 100 units that are supposed to be sufficient for the replenishment time. Now, we have a single client who asks for 80 of those units. Should we supply him with this quantity from our stock? By doing that we are taking the risk of Stock Outs. Therefore, in the situation described above, we would want to order this large quantity, outside our normal buffer, meaning that instead of replenishing to stock as we usually do, we will replenish to the specific order.
The last scenario is when a client desires something that we don't keep in stock. In this situation, we will order from the previous links in the chain his order.

In the last two scenarios described, we would want to give the client an estimated time that it will take us to deliver him his request.

The Client Order Life Cycle

First, the user will enter the Client Order to the system.
The system then identifies the supply route for that order.
The system will calculate the time needed for the client order to arrive at its destination, set a due date, and will set a time buffer for the Client Order.
The System will then continue to follow the Client Order and will update the order's buffer.