Tree Volumes (Tree ACRs)

Tree Volumes sum each person's downline volume. <Volumes> don't reference a tree; they assign values to individuals.

The majority of the time you'll use the standard TreeVolume:

    <TreeVolume Volume="PS" Tree="Enrollment" Name="TS" />

What you do is you name it just like everything else. The example is named "TS". Then you declare a Tree. This example is using the Enrollment Tree, but you could use Binary, Unilevel, Matrix, etc. For this example, we're going to assign the <VA_RetailRollup> Volume named "PS" that looks like this:

<VA_RetailRollup Name="PS">
        <DefVolType VolumeGroup="QV" />

What our Tree Volumes example is going to do is for each person in the Enrollment tree below an Associate (but doesn't include the Associate), it gets all of their "PS", sums up this volume, and puts that number as "TS". So this becomes your Group Volume.

A very common Condition that goes along with this is GVCondition that you can call "TS":

<GVCondition PersonalVolume="PS" MaxPersonal="-1" IncludeCompressed="True" CompressRule="" Level="-1" MaxPerLeg="-1" Max="-1" Min="1000" TreeVolume="TS" />

In this example, you need a 1000 "TS" to get this option.

Or in a GroupVolumeTree:

<GroupVolumeTree TreeVolume="TS" />

So for example, we have a <VA_Personal> Volume Accumulator, Tree Volume would walk down an Associate's entire organization, whatever Tree defined, and give them the total of everybody below's personal volume. You can pass in any Volume Accumulator you want.

You could do <VA_RetailRollup>, which would basically give an Associate everyone's volume below them in the Tree that's a Distributor with all their customer volume included.


Use <GVGenerationsTreeVolume> when you don't want the entire Tree, just the first X levels.


<PersonalTreeVolume> will include you (as in you the Associate). It's the same as the <TreeVolume> but this one can add in your personal volume, as well. One thing you'll notice is that almost every condition that takes a Tree volume also asks for your personal so you can add it in on the condition level most of the time.


In a binary structure, you have a Left and your Right Leg. So, an Associate may have a Left Leg volume of 100,000 and Right Leg volume of 200,000. This Associate personally has 500 volume from customers.

<AddVolumeToLeg> adds this personal volume to an Associate's Weak Leg. For example, if an Associate's Weak Leg is 1000, it adds that 500 personal customer volume to it. So, in the compensation plan later on, if anything asks, "what is my weak leg volume?" It would say 1500 because the customer volume was added to the Weak Leg.