Let’s see the different options that the platform offers in order to apply this kind of constraints.
Maximum Number of Trips
This sets a hard limit on the number of trips permitted in the scenario, selecting only the most profitable trips. An use case could be when there are a limited number of transport vehicles available to perform the transfers.
By using this restriction, the algorithm will cancel the potential trips proposed until arriving at that maximum number of trips, maintaining the ones with the highest ESI.
For example, if, without the restriction, the system would have proposed 4 trips…
- Trip 1 with ESI of 150 euros
- Trip 2 with an ESI of 100 euros
- Trip 3 with an ESI of 50 euros
- Trip 4 with an ESI of 25 euros
…and the user would have set a maximum number of trips of two, Trip 3 and 4 would not be proposed in the transfer, as they are the ones with the lowest ESI.
Maximum Number of Units Received
Some retailers may have difficulty receiving large amounts of units to their stores as part of a store transfer scenario. To restrict this, a maximum amount of total units that each store can receive can be set.
⚠️This is set at platform level and applies to every store in the system - it is controlled by a property that the Nextail support team can enable for you.
⚠️This restriction is applied at scenario level so if you are submitting 2 or more scenarios at the same time you could exceed the limitation
Let’s see an example, where the maximum units to receive value is set at 1000 units (to all stores):
- Store A is sending 500 units to Store C
- Store B is sending 600 units to Store C
Since we are exceeding the cap for Store C by 100 units, those units will be taken out of the proposed trip to comply with the restriction. The units to eliminate will be selected based on their ESI, the ones with the lowest values, will be removed.
Maximum Number of Units Sent
Likewise, a restriction on the maximum amount of total units each store can send as part of a store transfer scenario can be set.
Just like in the maximum units to receive restriction, the units that will be removed from the proposal will be those with the lowest ESI.
⚠️This is set at tenant level and applies to every store in the system - it is controlled by a property that the Nextail support team can enable for you.
⚠️This restriction is applied at scenario level so if you are submitting 2 or more scenarios at the same time you could exceed the limitation
Both maximum sent and received restriction parameters can be used when store teams are not able to dedicate a significant amount of time to picking and packing duties or have limited space to receive stock.
Furthermore, by setting conditions on trips either via Min ESI per trip or maximum number of trips the user is able to account for limitations in delivering units from store to store whilst also allowing the platform to find the most worthwhile trips.
Minimum Number of Units per trip
This constraint allows the user to set a minimum of units that should be included in each trip in order for it to be worth proposing.
⚠️This is set at tenant level and applies to every store in the system - it is controlled by a property that the Nextail support team can enable for you.
For example, if, without the restriction, the system would have proposed these 4 trips…
- Trip 1 with 150 units
- Trip 2 with 100 units
- Trip 3 with 50 units
- Trip 4 with 25 units
..and the user would have set a minimum of 75 units, Trip 3 and 4 would not be proposed in the transfer, as they are the ones below that value.
