First delay notifications
When a quantity on an order line is delayed beyond the process buffer and within 30 days of the promised date, a first delay notification is sent to the customer.
The notification is sent a configured number of hours before the promised date. By default, this is 48 hours for orders with email addresses and 120 hours for orders without email addresses. This is achieved by defining the monitoring rules that raise events when a line does not have its entire quantity that is either shipped or canceled. The monitor rules that are used to handle these scenarios are described in the next paragraph. These events are consolidated at the order level. Therefore, the customer is notified only one time for all the lines on the same order with the same promised date and same type of delay. Notes are also added to each order line, stating that the customer was notified by email, or the customer must be notified by a user about the order not being shipped on time.
Each line, with the applicable quantity, is included in the notice to the customer, along with a second promised delivery date. The notice informs the customer that the order is not likely to be shipped by the first promised date. It also stipulates that if the customers do not reply, it is assumed that the delay is acceptable and therefore approved.
IF Order meets condition First FTC Notification Is Needed? and has not reached Order line completely shipped or canceled 48 elapsed hours before Actual First FTC Promise Date THEN raise Send First FTC Delay Email. IF Order meets condition First FTC Notification Is Needed? and has not reached Order line completely shipped or canceled 120 elapsed hours before Actual First FTC Promise Date THEN raise Create First FTC Delay Alert.