As stated earlier, in the Consummate Phase, a Customer attempts to apply one or more Coupon Proposals to a purchase, and the Shop must decide for each Coupon Proposal whether to accept the Coupon Proposal outright, accept it with alterations, or reject it.
Upon the Shop deciding for each Coupon Proposal presented, the result must be recorded in our System. Currently, that is done by the Customer marking which Coupon Proposals are accepted or rejected, though this may also be automated through the Shop's internal system in the future, if the Shop has internal systems that will support such capability.
At the time of purchase, it is the Customer's role to request that specific Coupon Proposals be applied to specific purchases. To do so, the Customer must view their Active Coupon Proposals and alert the Shop to which ones they wish to apply (though it may be possible for Shops to alert Customers to outstanding Active Coupon Proposals in the future).
The list of Active Coupon Proposals shows the Customer's Coupon Proposals that have not expired or already been accepted. However, Coupon Proposals that have already been rejected will still show as active until they expire or are accepted, as rejection is not a terminal state. Furthermore, a Coupon Proposal can be rejected multiple times.
For each Coupon Proposal presented, the Shop must decide whether to accept it as-is, accept it with-alterations, or reject it.
While it is fair for Customers to presume that most Coupon Proposals will be accepted, the Shop must have the final say in this matter, as they did not actually create the specific Coupon Proposals themselves. Requiring Shop approval provides the opportunity to filter out Coupon Proposals created via technical errors or unintended abuses.
For each Coupon Proposal presented, currently, the Customer must record the resulting acceptance or rejection.
For Accepted Coupon Proposals, the Shop will provide an Acceptance Confirmation Code, which the Customer will enter (along with any alterations) to mark the Coupon Proposal as accepted. Currently, the Customer is responsible for doing this PRIOR to the finalization of the purchase transaction, and the Shop is responsible for verifying this was done properly.
For Rejected Coupon Proposals, the Customer may simply mark the Coupon Proposal as Rejected. Our JustShopBy™ System and/or Team will then contact the Store to confirm the rejection, to identify the reason for rejection, and find ways to alter the Coupon Proposal so that it will be accepted in the future.
Regardless of whether the Coupon Proposal is accepted or rejected, upon our System confirming an acceptance or rejection, the Customer will be awarded with Bonus Points for their usage of our System.
Also, upon our System confirming an acceptance or rejection, the Shops Acceptance, Rejection, and Usage Metrics will be updated to reflect the result.
Finally, upon our System confirming an acceptance, the Shop will be rewarded with access to the Interaction Response data used to create the Coupon Proposal.
All information provided therein must be used only for its intended purpose (i.e. to support adoption and usage of the JustShopBy™ Platform).