|
|
The design talks about "coupons". What about subscriptions? |
|
|
coupons here is generalization of discounts and subscriptions. Do you think it is better to use "Applied discounts/subscriptions" and "Issues discounts/subscriptions"? |
|
|
That's fine, as long as it is clear for the developers that both types are meant here. Related issue is probably that there could be multiple coupons needed (collect 10 coupons, get one product for free). I don't see a counter in the design. |
|
|
Oh, and what happens if coupons are to be combined? (Multiple inputs, multiple outputs?). The current design seems to limit to only 1 coupon. |
|
|
For multiple selection spa uses this design everywhere, and we can extend it to quantity. image.png (15,974 bytes) v1_search.jpg (35,650 bytes) |
|
|
order creation has input tokens and output tokens. applied coupons is for which of them? applied is in past, so those are applied to the order to be created, right? your design only shows discounts but you are saying that coupons also work for the suscription use case? how is this going to be rendered? |
|
|
Applied coupons = input tokens Issued coupons = output tokens Applied coupons were issued coupons in previous orders, so the buyer already has in his wallet these "applied coupons" and after purchase will receive "issued coupons" I just showed a search example on discounts; it works the same for subscription, but without quantity selection. |
- Anonymous
