Example customisation
To dive deeper in the concepts of process manager and listeners please see the following real life example.
A customer is using the below flow to when an order comes in.
Task definition | Description |
|---|---|
Locus order sync | Synchronise orders to the Locus WMS system if the channel is set to web. |
ORP stock | Deduct stock from the ORP stock database |
AccountView order sync | Send the orders to AccountView ERP |
Slim4 order sync | Send the orders to Slim4 stock management |
Yellowfin order sync | Send the orders to YellowFin BI |
Update ORP status | Update the order status so it is visible that the order propagated through the whole pipeline. |
New requirements
The customer that is using the above flow had a new requirement that came up during the Corona lockdown. The customer wanted to fulfill orders directly from stores. To fulfill from store the order needs to meet two criteria.
The store should be within a certain distance from the delivery address.
The store should have at least 80 percent of the items in stock.
Another important requirement is that the order should not be sent to Locus if the order is fulfilled by the store.
Finally the stock needs to be deducted from the store where the order is fulfilled.
New software and change in flow
To satisfy the requirements a new listener was introduced in the above flow. See below table:
Task definition | Description |
|---|---|
Sync store | Check if a store can fulfill the order, if so change the channel and order type. |
Locus order sync | Synchronise orders to the Locus WMS system if the channel is set to web. |
ORP stock | Deduct stock from the ORP stock database |
AccountView order sync | Send the orders to AccountView ERP |
Slim4 order sync | Send the orders to Slim4 stock management |
Yellowfin order sync | Send the orders to YellowFin BI |
Update ORP status | Update the order status so it is visible that the order propagated through the whole pipeline. |
As can be seen above a new task definition Sync store was added. This component will check if the shipping address of the order is within a set distance of a store that can fulfill the order. The Sync store listener will also check if more than a set percentage is in stock. If both criteria are met the order is manipulated. The channel will be set to the matching store and the order type will be changed to store fulfillment.
After the Sync store step the order will continue as normally through all process steps. Locus order sync will not create a Locus order because the channel is not web anymore. The ORP stock step will deduct the stock now from the store the order was placed because of the channel change. The rest of the steps will continue as normal.
As can be learned from the case above adding an extra step to the processmanager can be a very powerful tool and can make complex scenario’s possible.
copyright wolfpack DCS b.v. 2020