While the default implementation of the Abandoned Order Services module enables you to identify both abandoned and lost orders, some sites may require more granularity. For example, you may want to differentiate between high-priced and low-priced abandoned orders in order to respond differently to each type via scenarios and other campaigns. This section describes how to customize the module in this way, using this very example of high-priced and low-priced abandoned orders. You could use the same process to define and manage additional types of lost orders.
First, configure an instance of atg.commerce.order.abandoned.AbandonedOrderTools
for each type of abandoned order you want to manage. The AbandonedOrderTools
component stores the definitions of abandonment states, including the default states. In this example, you’ll need to configure two instances, one for high-priced abandoned orders and a second for low-priced abandoned orders. The following table describes how to configure each component:
Component | Description of Configuration |
---|---|
| Set the Set the HIGH_ABANDONED, LOW_ABANDONED, LOST Configure the remaining properties as necessary. |
| Set the Set the HIGH_ABANDONED, LOW_ABANDONED, LOST Configure the remaining properties as necessary. |
Then, configure an instance of atg.commerce.order.abandoned.AbandonedOrderService
for each type of abandoned order you want to identify and manage. Again, in this example you’ll need to configure two instances, one for high-priced abandoned orders and a second for low-priced abandoned orders. The following table describes how to configure each component:
Component | Description of Configuration |
---|---|
| Set the Set the Set the Configuring the remaining properties as necessary. |
| Set the Set the Set the Configuring the remaining properties as necessary. |