Penalties for not serving
A parameter that literally tells you how much it will cost you not to service / set up a particular jobs.
Basic settings
The price for not serving is set at 20 000 CZK in case the user wants to cancel all processed orders at any price. This is a basic setting of the program and in this case the setting does not play any role and does not favour the binding of certain jobs over others. The system simply tries to load everything without difference.
Settings in ScenarioImporter: <string>job;notservedpenalty</string>
Options for use - to implement or not to implement?
However, the parameter "Price for non-service" can be used to solve tasks where you are solving the question whether it is worthwhile to deliver a specific order by your own transport, delivery service (Czech Post, PPL, DPD, UPS, etc.) or not to deliver at all.
The principle is simple, in the field "Price for not serving" we set a real value, which can take several forms, depending on the problem we are solving, for example:
- how much I will earn by taking a job - margin,
- how much it would cost to implement a delivery service - price per package / pallet,
- total cost of the order - selling price.
Once the solution is started, the program will immediately evaluate the situation and suggest a solution that is as effective as possible. There are 3 levels of use:
- Priority
- To implement or not to implement
- Implement your transport or delivery service
Priority - excess of demand over distribution capacity
The "Price for not serving" setting for individual orders is high so that the system tries to serve all orders, but the price level varies depending on what priority you think the order has (often regular customers or customers with larger orders). A typical example is that there are two customers, with the same delivery time requirement (they both want the goods at 7am). If they have different prices set for non-service, the program will give priority in the calculation to the customer with the higher price and the other will either arrive at a different time or not at all.
If there are no collision situations, as shown in the example, the system tries to load all orders at any cost.
A typical user of this setting is the company JASO-Distributor spol. s r.o., which distributes beverages.
To implement or not to implement - an assessment of profitability
The "Price for not serving" setting is usually the actual profit value (margin), where the calculation evaluates the cost of serving the customer relative to the potential earnings. Such a setting may reveal locations that cost more to serve than the earnings. Such an output can serve as a basis for the sales team to focus on the unprofitable area or move the order to another day.
The difference from the previous example is that here the order may be purposely excluded from the plan due to the prevailing transport costs versus profit even if the customer is "serviceable" (does not violate capacity, time or work rules).
A typical user of this setup is the company Rekla, s.r.o. which deals with the collection of used oil.
Implement your transport or delivery service - E-shop
"Price for not serving" The price for non-service is set according to the actual price list of what it would cost if the order was delivered by a specific courier service. At this point, you have a unique tool at your disposal that will accurately evaluate the situation of whether to bind your transport or a courier service. However, you need to have the best possible pricing model for your own transport (exact price per km, or per hour of work, etc.). For more details see Courier module.
Sample scenario for download:
- Media:TAS_Situace_Zakazky_Penalizace_za_neobsloueniKombinace_PPL_DPD_GEIS.distances
- Media:TAS_Situace_Zakazky_Penalizace_za_neobsloueniKombinace_PPL_DPD_GEIS.scenario
- Media:TAS_Situace_Zakazky_Penalizace_za_neobsloueniLayoutSettings.zip