Multichannel Sales Center This event occurs when certain payment information needs to be updated, added, or deleted from an order when a change is made to a release after release to fulfillment and before actual shipment (after the reservePayment event but before the finalizePayment event). This type of edit can be thought of as a last-chance edit because it enables an order or order item to be changed one last time before the order ships. Because it is a last-minute change that most likely involves support representatives having to contact warehouse or shipping personnel, this event can be considered expensive for the business and should not be taken lightly.
A release edit occurs when:
- The change involves the addition, deletion, or changing of order item quantities and amounts in payment instructions change (increase or decrease)
- Payment methods or payment instructions are incorrect and need to be changed
The purpose of this event is to ensure that the event-driven payments subcomponent is aware of changes in a release, so that any reserved amounts are rebalanced. Anything in the release that can be reversed is reversed, and a new reservePayment request is issued.
The possible payment actions associated with this event are: Approve, Deposit, and ReverseApproval.
Ticklers can be created when deposits already occurred and the amount changes below the deposit level.
Example: A customer places an order and changes his mind about the order and calls a Customer Service Representative to change the order, but the order has already been released to fulfillment. The Telesales Service Representative obtains approval to roll back the release to fulfillment and then attempts to roll back the order release to change the order. If the order can be changed, the Customer Service Representative changes and submits the edited order.