Trigger
circumstance where Deal is on, get cheaper tier price or maxed out
The Trigger determines when a deal is On based on different criteria, such as reaching a specific amount of money raised, a certain number of tickets or a specific number of complete packages/bundles.Each Trigger is explained, including guidelines on when to use them.
The example below highlights the similarities and differences that can occur within the same set of reservations, providing insights into the circumstances where each type of Trigger should be used.
You can consider a Trigger as a success criteria that determines how the minimum requirement, tier price, maximum limit, and item availability are achieved through reservations.
The fee charged to the participant is not determined by the Trigger used, but rather by the total cost of their reservations.
Let's explore how each Trigger behaves in the same setting with the same reservations. The settings:- 2 items: 3 x Square @ $.50 / item, 10 x Triangle @ $1 / item.
- minimum requirement: 5, maximum limit: 10.
- unit: 42 points, tolerance: 12 points (only applicable to Capacity Trigger).
- unit: 47 points, tolerance: 8 points (only applicable to Segment Trigger).
- 50 Square reservations.
- 5 Triangle reservation.
- 45 Triangle reservations.
- 150 Squares and 150 Triangles reservations.
pin Count Trigger: is triggered when the total number of items purchased reaches a certain target.
This is suitable for deals that have a count target, such as a store sale or bulk purchase.
The deal's minimum requirement, tier price, and maximum refer to the total item count, with the number next to each item indicating the item's maximum limit.
This is suitable for deals that have a count target, such as a store sale or bulk purchase.
The deal's minimum requirement, tier price, and maximum refer to the total item count, with the number next to each item indicating the item's maximum limit.
If there is no item limit, it is set as zero, meaning unlimited (only bound to the Deal's maximum).
The Platform only counts the number of items reserved, regardless of their cost for triggering Count Trigger.
Initially there are 50 Square reservations but there are not enough reservations that can be used, as there is a limit of 3 items for Square, it can only fulfill 3 items, which is below the Deal's minimum requirement of 5, resulting in the Deal being Off.
Next, there are additional 5 Triangle reservations, which is below the item limit for Triangle, resulting in a total of 3 Squares and 5 Triangles, or 8 items, which exceeds the minimum requirement, the Deal is considered On.
Next, there are 45 additional Triangle reservations, even though the item limit for Triangle is 10, but the Deal limit is set at 10, only 7 item reservations will be used (3 Square + 7 Triangle = 10 items), reaching the Deal's maximum limit.
Further reservations of 150 Square and 150 Triangle items won't make a difference, as there are waiting list for Square and Triangle.
Why doesn't the Platform prioritize more expensive (Triangle) reservations first?
The Platform tries its best to allocate reservations each time they are approved. Once Allocated, reservations cannot be moved back to the In-Queue, as this applies to all Triggers. More expensive does not necessarily mean more profit. The fairer approach is to prioritize based on the earliest approval time first.
The Platform tries its best to allocate reservations each time they are approved. Once Allocated, reservations cannot be moved back to the In-Queue, as this applies to all Triggers. More expensive does not necessarily mean more profit. The fairer approach is to prioritize based on the earliest approval time first.
attach_money Money Trigger: is triggered when the total money raised reaches a certain target.
It is suitable for deals that have a money target, such as crowdfunding campaigns, purchasing a house/factory, or scenarios where you need to divide something but the exact quantity of each item is uncertain, such as livestock.
The minimum, tier price, and maximum requirements for the deal refer to the total money raised, while the number next to each item refers to the item's maximum limit based on stock availability.
It is suitable for deals that have a money target, such as crowdfunding campaigns, purchasing a house/factory, or scenarios where you need to divide something but the exact quantity of each item is uncertain, such as livestock.
The minimum, tier price, and maximum requirements for the deal refer to the total money raised, while the number next to each item refers to the item's maximum limit based on stock availability.
If there is no item limit, it is set as zero, meaning unlimited (only bound to the Deal's maximum).
It does not matter how many items are reserved; the Platform only calculates the total reservations cost for triggering the Money Trigger.
Initially there are 50 Square reservations totaling $25 (50 x $0.50 = $25), but there are only 3 Square item limits (totaling 3 x $0.50 = $1.50), and the Deal's minimum requirement is $5, the Deal will be Off, but for a slightly different reason than the Count Trigger.
Note: All Triggers, including the Money Trigger, will use the item's initial price (not the tier price) to calculate if the participant has enough funds. In Money Trigger, the initial price is also used to determine if the Deal has reached the minimum, tier price, or maximum requirements.
Next, there are 5 Triangle reservations below the item limit for Triangles, and there are already 3 Square reservations and 5 Triangle reservations (totaling 3 x $0.50 + 5 x $1 = $6.50), which exceeds the minimum requirement, the Deal will be On, but for a slightly different reason than the Count Trigger.
Next, there are 45 additional Triangle reservations, even though the item limit for Triangles is 10, and the Deal limit is $10, having 3 Square reservations and 10 Triangle reservations would exceed the limit (3 x $0.50 + 10 x $1 = $11.50). Therefore, only 8 item reservations will be used (3 x $0.50 + 8 x $1 = $9.50), resulting in a different outcome from the Count Trigger.
Adding another 150 Square and Triangle reservations won't make a difference because there is a waiting list for Squares and Triangles.
Why doesn't the Platform select 10 Triangles, which amount to a maximum of $10?
Similar to Count Trigger; once Allocated, reservations cannot be moved back to the In-Queue, and more expensive does not necessarily mean more profit.
Similar to Count Trigger; once Allocated, reservations cannot be moved back to the In-Queue, and more expensive does not necessarily mean more profit.
extension Bundle Trigger is triggered when a certain target number of bundles is reached. A bundle consists of multiple items, each item may require multiple quantities, all of which must be reserved in order to be counted as a complete bundle.
This Trigger is suitable for package deals (e.g., buy 2, get 1 free), buying parts in a set (e.g., chicken parts), sharing space, timeshare, and similar scenarios.
The minimum, tier price, and maximum limits of the deal refer to the total number of bundles, not individual items within the bundle (e.g., chicken breasts). The number next to each item represents the required quantity of that item to create a complete bundle.
In the example that we are exploring, a bundle consists of 3 Squares and 10 Triangles. The cost or quantity of individual items reserved does not matter for this Trigger - the Platform only counts the number of complete bundles that can be created from the reservations.
This Trigger is suitable for package deals (e.g., buy 2, get 1 free), buying parts in a set (e.g., chicken parts), sharing space, timeshare, and similar scenarios.
The minimum, tier price, and maximum limits of the deal refer to the total number of bundles, not individual items within the bundle (e.g., chicken breasts). The number next to each item represents the required quantity of that item to create a complete bundle.
In the example that we are exploring, a bundle consists of 3 Squares and 10 Triangles. The cost or quantity of individual items reserved does not matter for this Trigger - the Platform only counts the number of complete bundles that can be created from the reservations.
Initially there are 50 Square reservations but not enough Triangle reservations to create any bundles, the Deal will be Off, but for a different reason than the Count or Money Triggers.
Adding 5 more Triangle reservations will not be sufficient to trigger the bundle, as these reservations can only create 1 complete bundle. However, the minimum requirement for triggering the bundle is 5 complete bundles, which has not been met.
Next, there are 45 additional Triangle reservations, along with 15 Squares, which can create 5 bundles, the Deal will be On as the minimum requirement has been met.
Next, there are 150 additional reservations each of Squares and Triangles, and there are enough of each to create 10 bundles, the Deal will have reached its maximum limit.
Note: Bundles may contain items with zero cost, but they must be reserved in order to be counted as complete bundles, just like other items.
group_work Capacity Trigger is triggered the number of filled units reaches the minimum limit but does not exceed the maximum limit. The points are assigned to each reservation based on the specific item reserved. A unit is considered filled when it accumulates a certain number of points from reservations, allowing for a tolerance of total unused points.
The deal minimum, tier price, and maximum refer to the overall quantity of unit, such as how many liter of perfume, box of apples, or buses. The numbers accompanying each item indicate the points assigned to it, such as 20 points for 20ml of perfume, 1 point for a single apple, or 3 points for 3 bus seats. Additionally, two new limitations are introduced: the unit size measured in points (e.g., 1000 points for 1000ml (1 liter) of perfume, 12 points for a dozen apples, or 70 points for a 70-seat bus) and the total tolerance represented by a specific point value (e.g., 100 points for 100ml leftover, 1 point for 1 apple leftover, or 2 points for 2 empty seats).
The deal minimum, tier price, and maximum refer to the overall quantity of unit, such as how many liter of perfume, box of apples, or buses. The numbers accompanying each item indicate the points assigned to it, such as 20 points for 20ml of perfume, 1 point for a single apple, or 3 points for 3 bus seats. Additionally, two new limitations are introduced: the unit size measured in points (e.g., 1000 points for 1000ml (1 liter) of perfume, 12 points for a dozen apples, or 70 points for a 70-seat bus) and the total tolerance represented by a specific point value (e.g., 100 points for 100ml leftover, 1 point for 1 apple leftover, or 2 points for 2 empty seats).
The Platform can take up to 1 decimal point, for example 5 or 5.5, but not 5.55 - you need to multiply it yourselves TODO.
It does not matter how many items are reserved or how much each item cost; the Platform only focus on the total number of units. Each unit should not exceed a certain number of points (referred to as unit size, which is 42 points in this case) and may have a certain amount of total leftover points (referred to as tolerance, which is 12 points in this case). The tolerance allows for a certain amount of points to go unused or wasted.
Let's consider an example scenario where you plan to go on a vacation by bus. Each bus has a seating capacity of 42 people, and you want to ensure that at most 12 empty seats (or least 30 seats are occupied) are present on each bus to make the trip financially viable. In this case, the Count Trigger can be used. The minimum requirement for the deal would be 30 points (seats), while the maximum would be set at 42. If you decide to use 2 buses, the minimum and maximum values would be doubled accordingly, resulting in a minimum of 72 and a maximum of 84 reservations.
However, in this case, a limitation of the Count Trigger is that the number of buses must be predetermined. Consequently, if the minimum requirement is set to 42 and the maximum to 84, there may be a situation where only 43 seats are reserved, thus requiring 2 buses despite the low number of seats. Money Trigger would have the same limitation.
If there are multiple buses involved, a better option would be the Bundle Trigger. In this case, the item count for each bundle would be set to 42, aligning with the bus's seating capacity. However, in this case, the limitation with using the Bundle Trigger is that the number of participants must be a multiple of 42, which may not always be feasible or practical.
In this scenario, the Capacity Trigger is more appropriate, as it allows the organizer to specify the size of each bus (42 points) and the tolerance for empty seats (12 points). With the Capacity Trigger, the platform can allocate seats within the range of 30-42 (for 1 bus), 72-84 (for 2 buses), 114-126 (for 3 buses), and so on, ensuring the desired occupancy while accommodating any potential total unsold seats. Additionally, the Count, Money, and Bundle Triggers present another challenge. Participants may reserve multiple seats, but they may not necessarily receive all the seats they reserved. For example, a family aiming to travel together may reserve 4 seats but end up receiving only 2. This can create inconvenience and dissatisfaction.
When the goal is to obtain either all or none of the reservations, the Capacity Trigger serves as a more suitable choice. The minimum and maximum values for the Capacity Trigger can be set to correspond to the number of buses or units available. In our example, let's assume the minimum is 1 and the maximum is 7, signifying the number of buses. Each bus has a capacity of 42 seats, and a wastage tolerance of 12 points is allowed, meaning that up to 12 seats can remain unused. To facilitate collective seat reservations, you can create new items with varying point values. For instance, you can assign 1 seat to be equivalent to 1 point with a corresponding price, 2 seats as 2 points with a corresponding price, 3 seats as 3 points, and so on.
If there are multiple buses involved, a better option would be the Bundle Trigger. In this case, the item count for each bundle would be set to 42, aligning with the bus's seating capacity. However, in this case, the limitation with using the Bundle Trigger is that the number of participants must be a multiple of 42, which may not always be feasible or practical.
In this scenario, the Capacity Trigger is more appropriate, as it allows the organizer to specify the size of each bus (42 points) and the tolerance for empty seats (12 points). With the Capacity Trigger, the platform can allocate seats within the range of 30-42 (for 1 bus), 72-84 (for 2 buses), 114-126 (for 3 buses), and so on, ensuring the desired occupancy while accommodating any potential total unsold seats. Additionally, the Count, Money, and Bundle Triggers present another challenge. Participants may reserve multiple seats, but they may not necessarily receive all the seats they reserved. For example, a family aiming to travel together may reserve 4 seats but end up receiving only 2. This can create inconvenience and dissatisfaction.
When the goal is to obtain either all or none of the reservations, the Capacity Trigger serves as a more suitable choice. The minimum and maximum values for the Capacity Trigger can be set to correspond to the number of buses or units available. In our example, let's assume the minimum is 1 and the maximum is 7, signifying the number of buses. Each bus has a capacity of 42 seats, and a wastage tolerance of 12 points is allowed, meaning that up to 12 seats can remain unused. To facilitate collective seat reservations, you can create new items with varying point values. For instance, you can assign 1 seat to be equivalent to 1 point with a corresponding price, 2 seats as 2 points with a corresponding price, 3 seats as 3 points, and so on.
The Capacity Trigger is suitable for situations where it is necessary to divide a homogeneous element into individual item while allowing for the possibility of unsold items within a specified tolerance. A homogeneous element refers to a uniform item that can be divided or measured consistently.
This is applicable in various scenarios, such as repackaging milliliters of perfume sold by liter, dividing grams of chocolate sold by kilograms, reselling individual apples sold by the case, or assigning travelers to available bus seats while accommodating leftover capacity (in terms of perfume, chocolate, apples, or seats).
It is also suitable for ensuring that a specific quantity of products (counted as points) are bought together as a package or none at all, as seen on the bus example above. It can also be used to offer a certain discount when a particular quantity of points is reserved. For example, purchasing 20ml of perfume would be cheaper per ml compared to buying just 10ml of perfume.
This is applicable in various scenarios, such as repackaging milliliters of perfume sold by liter, dividing grams of chocolate sold by kilograms, reselling individual apples sold by the case, or assigning travelers to available bus seats while accommodating leftover capacity (in terms of perfume, chocolate, apples, or seats).
It is also suitable for ensuring that a specific quantity of products (counted as points) are bought together as a package or none at all, as seen on the bus example above. It can also be used to offer a certain discount when a particular quantity of points is reserved. For example, purchasing 20ml of perfume would be cheaper per ml compared to buying just 10ml of perfume.
There are no strict rules on how to price each item.
Difficulty in fulfilling the reservation
The price per point for each item reflects the level of difficulty in fulfilling the reservation.
For instance, on a 42-seat bus, it is relatively easier to find 3 available seats compared to finding just 1 seat. Therefore, the price per seat can be the same or even cheaper, incentivize people to reserve multiple seats at once. On the other hand, on a 10-seat car, it is relatively more challenging to find 3 available seats compared to finding just 1 seat. In this case, the price per seat should be higher to incentivize people to reserve multiple single seat if possible.
Ultimately, the pricing depends on factors such as the unit size, tolerance size, and the deal's minimum and maximum requirements.Cost associated with the reservation
The price per point for each item takes into account the added cost associated with the reservation.
For instance, while a perfume container might be costly, the price for a 10ml or 20ml container might be minimal. Therefore, the cost per ml for the 20ml container should be lower.
Initially, there are 50 Square reservations made. However, the total points accumulated of 150 (50 items x 3 points) from these reservations fell short of the requirement to fill 5 units (5 units x 42 points = 210 points). As a result, the Deal couldn't proceed, but this reason differs from the Count, Money, or Bundle Triggers.
Next, there are 5 Triangle reservations made, resulting in a combination of 50 Squares and 5 Triangles. The points accumulated from these reservations amounted to 200 points (50 Squares x 3 points + 5 Triangles x 10 points). Although this still didn't reach the minimum requirement of 210 points (5 units), considering a permissible tolerance of 12 points, the Deal became On.
Next, there are an additional 45 Triangle reservations. Since the maximum reservation allowed was 10 units (10 units x 42 points = 420 points), only 27 Triangles could be accommodated due to the presence of 50 Squares (50 Squares x 3 points + 27 Triangles x 10 points = 420 points). Thus, the Deal reached its maximum capacity.
Even with the addition of 150 Square and 150 Triangle reservations, it wouldn't have made any difference as the maximum limit had already been reached.
Even with the addition of 150 Square and 150 Triangle reservations, it wouldn't have made any difference as the maximum limit had already been reached.
Why doesn't the Platform prioritize more expensive (Triangle) first?
Similar to Count Trigger; once Allocated, reservations cannot be moved back to the In-Queue.
Similar to Count Trigger; once Allocated, reservations cannot be moved back to the In-Queue.
donut_small Segment Trigger triggered when the number of filled units reaches the minimum limit. The points are assigned to each reservation based on the specific item reserved. A unit is considered filled when it accumulates a certain number of points from reservations, allowing for a tolerance of unused points within each unit. Each item should not be divided into more than one unit.
Similar to Capacity Trigger, the deal minimum, tier price, and maximum refer to the overall quantity of unit, such as how many buses, spool of rope. The numbers accompanying each item indicate the points assigned to it (how many seats in a bus, meter of rope). Additionally, two limitations: the unit size measured in points and each unit tolerance represented by a specific point value.
The Platform can take up to 1 decimal point, for example 5 or 5.5, but not 5.55 - you need to multiply it yourselves TODO.
It does not matter how many items are reserved or how much each item cost; the Platform only focus on the total number of units. Each unit should not exceed a certain number of points (referred to as unit size, which is 47 points in this case) and may have a certain amount of leftover points (referred to as tolerance, which is 8 points in this case) per unit. The tolerance allows for a certain amount of points to go unused or wasted.
Let's reconsider an example scenario where you plan to go on a vacation by bus. While the Capacity Trigger is suitable for reservations based on the total number of seat, it may not ensure that all seats are allocated together in the same bus.
For instance, if a participant books three seats for himself and his two children, the Capacity Trigger might assign one seat in one bus and two seats in another bus creating undesired circumstance, leading to an undesired seating arrangement.
In this scenario, the Segment Trigger is more suitable. By utilizing the Segment Trigger, the participant can choose a three-seat reservation, indicating that all three seats must be allocated together on the same bus.
The tolerance for the Segment Trigger is set per unit (in this case: bus), allowing for a certain number of empty seats in each bus.
When the Deal ends successfully, the system will provide suggestions on how to allocate the seats in buses, ensuring that the participants' reservation requirements are met. The Segment Trigger is ideal for scenarios where an item consists of a single continuous item, such as cutting a rope, chain, or pipe. It ensures that a reservation for a specific length, like 3 meters of rope, cannot be divided into multiple segments or accepted in smaller lengths, like a combination of 2 or more 3-meter ropes or just 2 meters of rope.
Similarly, the Segment Trigger can be used for bus seat reservations, where all the seats must be assigned on the same bus or none at all.
For instance, if a participant books three seats for himself and his two children, the Capacity Trigger might assign one seat in one bus and two seats in another bus creating undesired circumstance, leading to an undesired seating arrangement.
In this scenario, the Segment Trigger is more suitable. By utilizing the Segment Trigger, the participant can choose a three-seat reservation, indicating that all three seats must be allocated together on the same bus.
The tolerance for the Segment Trigger is set per unit (in this case: bus), allowing for a certain number of empty seats in each bus.
When the Deal ends successfully, the system will provide suggestions on how to allocate the seats in buses, ensuring that the participants' reservation requirements are met. The Segment Trigger is ideal for scenarios where an item consists of a single continuous item, such as cutting a rope, chain, or pipe. It ensures that a reservation for a specific length, like 3 meters of rope, cannot be divided into multiple segments or accepted in smaller lengths, like a combination of 2 or more 3-meter ropes or just 2 meters of rope.
Similarly, the Segment Trigger can be used for bus seat reservations, where all the seats must be assigned on the same bus or none at all.
Similar to Capacity Trigger, it is recommended that the price per point for each item reflects the level of difficulty in fulfilling the reservation and/or cost associated with each reservation.
Initially, there are 50 reservations for Squares, the total number of reserved points is not enough to fill 5 units even if each unit is filled to the minimum requirement. With a calculation of 47 points - 8 points for wastage, the minimal requirement per unit is 39 points. Thus, only almost 4 units can be filled with the available 50 Squares, as each unit can accommodate a maximum of 13 Squares (39 points / 3 points per Square). Consequently, the deal is Off due to insufficient points, representing a different reason compared to Count, Money, or Bundle Triggers.
Next, adding 5 reservations for Triangles to the existing 50 reservations for Squares provides a solution to fill 5 units, albeit with significant wastage. The allocation results in the first 3 units being filled with 13 Squares each, accounting for 39 points (13 Squares x 3 points) and 8 points wasted. The fourth unit includes 11 Squares and 1 Triangle, totaling 43 points (11 Squares x 3 points + 1 Triangle x 10 points) with 4 points wasted. The fifth unit contains 4 Squares, resulting in 40 points (4 Squares x 10 points) with 7 points wasted. Despite the wastage, the deal becomes On, but with a total of 36 points wasted.
Next, with an additional 45 reservations for Triangles, the total reservations for Squares and Triangles reach 50 each, enabling the filling of 10 units with minimal tolerance.
The first 5 units consist of 2 Squares and 4 Triangles each, totaling 46 points (2 Squares x 3 points + 4 Triangles x 10 points), with only 1 point wasted. The next 3 units are filled with 9 Squares and 2 Triangles each, amounting to 47 points (9 Squares x 3 points + 2 Triangles x 10 points) without any wastage. The ninth container contains 5 Squares and 3 Triangles, resulting in 45 points (5 Squares x 3 points + 3 Triangles x 10 points), with 2 points wasted. The tenth container comprises 8 Squares and 2 Triangles, totaling 44 points (8 Squares x 3 points + 2 Triangles x 10 points), with 3 points wasted.
Although there are 3 remaining points that could be filled with Squares, no additional Squares are available. Consequently, the deal has reached its maximum number of units with a total of 10 points wasted.
The first 5 units consist of 2 Squares and 4 Triangles each, totaling 46 points (2 Squares x 3 points + 4 Triangles x 10 points), with only 1 point wasted. The next 3 units are filled with 9 Squares and 2 Triangles each, amounting to 47 points (9 Squares x 3 points + 2 Triangles x 10 points) without any wastage. The ninth container contains 5 Squares and 3 Triangles, resulting in 45 points (5 Squares x 3 points + 3 Triangles x 10 points), with 2 points wasted. The tenth container comprises 8 Squares and 2 Triangles, totaling 44 points (8 Squares x 3 points + 2 Triangles x 10 points), with 3 points wasted.
Although there are 3 remaining points that could be filled with Squares, no additional Squares are available. Consequently, the deal has reached its maximum number of units with a total of 10 points wasted.
Next, an additional 150 Square reservations and 150 Triangle reservations are made. With the inclusion of these new Square reservations, the last unit can now accommodate one more Square. The Deal remains at its maximum number of units, but with a reduced wastage of 7 points instead of 10.
The 10th unit consists of 9 Squares and 2 Triangles, totaling 47 points without any wastage.
The 10th unit consists of 9 Squares and 2 Triangles, totaling 47 points without any wastage.
Why doesn't the Platform allocate the 10 units with 140 Squares (14 Squares each) and 0 points of waste, if there will be 200 Squares eventually?
Similar to Count Trigger; once Allocated, reservations cannot be moved back to the In-Queue.
Similar to Count Trigger; once Allocated, reservations cannot be moved back to the In-Queue.
While allocating reservations based on reservation time ensures fairness and follows a first-come, first-served principle, there are cases, such as the Segment Trigger example, where this approach can lead to inefficient allocation and point wastage.
In scenarios like the segment example where points are wasted, Approve Manually can be employed as a solution. By using Approve Manually, reservations are not immediately allocated upon qualification.
This allows for a more deliberate evaluation of the reservations, considering factors beyond just the reservation time. Once you think a sufficient reservations have been received, all reservations can be approved simultaneously, regardless of their reservation time.
The inefficiency can also affect the Capacity Trigger and Money Trigger, although to a lesser extent than the Segment Trigger.
more on Approval
In scenarios like the segment example where points are wasted, Approve Manually can be employed as a solution. By using Approve Manually, reservations are not immediately allocated upon qualification.
This allows for a more deliberate evaluation of the reservations, considering factors beyond just the reservation time. Once you think a sufficient reservations have been received, all reservations can be approved simultaneously, regardless of their reservation time.
The inefficiency can also affect the Capacity Trigger and Money Trigger, although to a lesser extent than the Segment Trigger.
more on Approval
There are no strict guidelines dictating the choice of Trigger when splitting a Deal. If the Deal is relatively straightforward, any Trigger can be utilized. For instance, if you wish to split a "buy 3 get 2 free" Deal where you purchase 5 items at a discounted rate, different Triggers with specific configurations can be employed.
If you use Count or Money Trigger, raising the maximum to 10 is not possible as the Deal could end up with 7 item reservations, which doesn't meet the required purchase multiple of 5 for the discounted price.
On the contrary, you can increase the maximum limit for Bundle, Capacity, or Segment Trigger to 2, and the platform will automatically allocate either 5 or 10 item reservations.
- Count or Money Trigger: Minimum and maximum limits are set to 5, with no item limit (limit = 0) or an item limit of 5.
- Bundle Trigger: Minimum and maximum limits are set to 1, with a item size of 5.
- Capacity or Segment Trigger: Minimum and maximum limits are set to 1, with each item assigned a value of 1 point, a unit size of 5, and no wastage (wastage = 0).
If you use Count or Money Trigger, raising the maximum to 10 is not possible as the Deal could end up with 7 item reservations, which doesn't meet the required purchase multiple of 5 for the discounted price.
On the contrary, you can increase the maximum limit for Bundle, Capacity, or Segment Trigger to 2, and the platform will automatically allocate either 5 or 10 item reservations.
To determine the most suitable Trigger for a Deal, it is important to consider the specific requirements and nature of the Deal:
- If the Deal involves purchasing multiple items together as a bundle, the Bundle Trigger is more appropriate.
- If the Deal is structured around a specific quantity of items to be bought, the Count Trigger is more appropriate.
- For Deals that rely on achieving a certain monetary target, the Money Trigger is more appropriate.
- For Deals involving a homogeneous element where leftovers are allowed or a specific number of elements must be reserved together, either the Capacity or Segment Trigger can be used.
A homogeneous element refers to a uniform item that can be divided or measured consistently. In this context, participants can reserve a certain quantity as a group, and it must be fulfilled entirely or not at all (referred as collective reservation).- The Segment Trigger is particularly suitable when dealing with a single continuous item, such as a rope, where it involves dividing the item into smaller sections.
- The Capacity Trigger is more suitable for non-continuous items like those measured by weight or volume.