From c4d2a1fa7c8a426f703219114104932817c05613 Mon Sep 17 00:00:00 2001
From: "Paul [Eraman Koop - CoopCycle]"
<77277854+Paul-Eraman-CoopCycle@users.noreply.github.com>
Date: Mon, 13 Nov 2023 22:27:04 +0100
Subject: [PATCH] Update pricing.md
---
docs/_admin/deliveries/pricing.md | 36 +++++++++++++++++++++++++++++++
1 file changed, 36 insertions(+)
diff --git a/docs/_admin/deliveries/pricing.md b/docs/_admin/deliveries/pricing.md
index 5b7259b3..9d8a57e2 100644
--- a/docs/_admin/deliveries/pricing.md
+++ b/docs/_admin/deliveries/pricing.md
@@ -114,6 +114,42 @@ Once you have thought about these factors and created some zones, package lists,
9. After you've configured your custom pricing, click Save
+---
+## Example Rules
+
+1. **Old School Bike Messenger Pricing**
+
+ When to use When you have clients who have deliveries that may go to any place in the city in unpredictable ways, so you must default to km-based pricing rules. **Pros:** Simple, can't accidentally give a wrong price, easy for clients to understand
+
+ When **not** to use If you can avoid it, do. Do not use if you have any type of client other than that described above. **Cons:** This pricing rule is easy, but cannot be used for deliveries with multiple points since they will be charged more or less based on if they order the deliveries efficiently or not, which is not their concern. It also imagines you are only delivering their package, and not mixing with other clients in an effective way. Effectively, this is a pricing rule made for a type of delivery that is not longer common or strategically interesting for your business, creating unintended limitations long-term.
+
+2. **Very Complete But Complex Pricing** **Recommended if Possible**
+
+ When to use Clients who have many different types of deliveries, multiple pickup locations in different parts of the city. Bakeries, florists, other types of local commerce. **Pros:** Can be used to make a standard pricing rule that simplifies commercial capture and operations, is more "fair" and precise
+
+ A simple client who wants a simple price they understand and will be put off by math and large tables **Cons:** Can confuse small business owners and make the commercial process harder. The more complex a rule gets, the harder it is to modify later.
+
+
+
+
+
+
+
+
+
+
+
+3. **Multi-Dropoff Pricing** **Recommended if Possible**
+
+ When to use When you have a client with a clear set of possible deliveries, but they may change or be arranged differently in each delivery. Any one order may be between 2 and 10 points, and there is not a huge variation between the types of packages you are carrying, or the time slots in which they are being delivered. Ex. notifications, fruit boxes, moving stock between stores. **Pros:** Avoids clients getting annoyed at slowly making orders one at a time, clean and simple pricing rule you can explain to a client that covers a wide range of use cases.
+
+ When **not** to use If the client cannot use CoopCycle as they should, or if they have a very high volume of orders **Cons:** This pricing rule is still being developed and still cannot be used with pricing rules that are based on time like `Difference (hours)`, `Difference (days)` or `time range length (hours)` and in no circumstances can be used with rules based on kilometers of distance.
+
+4. **Last Mile At Volume**
+
+ When to use For clients who give you a high volume of standarized packages such as magazines, small last mile pacakges from a provider like DHL, or any other delivery that can easily have an "average" price. **Pros:** Simple for client and invoicing.
+
+ When **not** to use Any client with deliveries that cannot be "averaged" **Cons:** If your average is wrong, later you will have made less money than you hope. Maybe the client says they have a simple and easily averaged need, but then ask for special or different deliveries in specific moment that should be more expensive, but the rule charges the "cheap" option.
### Definitions of conditions
Brief description on each condition.