Get Customers by Role-Department-Qty-Pct

This Dynamic List is used get customers who have purchased enough items from the defined departments to meet, or exceeded, the defined threshold in a single transaction to issue post transaction wallet credit based on the total amount of the items from the defined departments. This Dynamic List is often used to give incentive to shop specific departments, like the Produce department.

What are the parameters?
This Dynamic list actually has two different variations depending on the Task Schedule options.

If the task is a Recurring Task it has five parameters split between three fields:

• Role|Qty|Percent: [ role1|5|50 ]
  • The first field contains three different Parameters, each pipe separated ( | )
    • Role: This is the individual, or multiple (comma separated), role(s) that the list will look for in customer profiles. If multiple roles are defined, only one of the roles needs to be assigned to a customer wallet for them to be returned in the list. If a customer has more than one of the roles in their wallet, they will only be returned once in the list.
      • This parameter can support including all roles (including customers who have no role assigned) but using the asterisk ( * ) in place of the rolename
    • Qty: This is the quantity threshold of items a customer must have purchased in a single transaction from the defined department list. The number of items must meet or exceed this quantity threshold. If a zero quantity is defined, then wallet benefits will be issued on any purchase from the qualifying department(s)
  • Percent:What percent of the retail price of all items in the order from the defined department(s) will be issued as wallet benefits if the quantity threshold is met or exceeded.
• Department List: [ 39,40,101 ]
  • The Department list parameter defines what department(s) (comma separated) items purchased from count toward meeting or exceeding the quantity threshold. If the quantity threshold is met or exceeded, then the retail price of the items in the order from the defined department(s) will be multiplied by the defined percentage to issue wallet benefits.
• Household: [ unchecked ] or [ checked ]
  • If all roles ( * ) are defined, then all orders from all households will be included regardless if the Household flag is checked or unchecked. If a specific role is defined:
    • Unchecked: Only the orders from customers with one or more of the specified role(s) will be processed. If a secondary customer, the primary customer wallet will be credited the wallet benefits.
    • Checked: All orders, both primary and secondary customers, will be processed if anyone in the household has one, or more, of the defined roles.

If the task is a One Time task, the same parameters for recurring tasks are there, plus the addition of the Start Date and End Date parameters. These parameters define the time range the one time task will use for orders:

• Start Date: This is the date and time the task will use as the oldest possible order date. All customer orders used for this task must have a start date equal to or greater than this date, but less than the End Date.
• End Date: This is the date and time the task will use as the newest possible order date. All customer orders used for this task must have a start date less than or equal to this date, but greater than the Start Date.