What is the problem ?
Now that standing order feature is released, there are some pressing flaws to fix on the user flow when multiple orders are made on a given open OC.
1- Customer who has a previous order for a given OC and make a new order can see in cart dropdown AND cart page the “items already ordered for that OC”
BUT the items are not appear below any order reference, and are not aggregated either, so it induces some confusing result when a given product is ordered in multiple previous orders.
2- When customer who has a previous order for an OC makes a new order, at checkout she can view the items previously ordered and can delete them while checkout out for the new order. If she clicks on “modify confirmed items” she is abruptly redirected to “account page” without any instruction on what to do.
3- When she makes a modification, either delete a confirmed product when checking out for the new order, or when modifying an order from “my account” access, she receives no notification.
Solution proposed to fix those problems
It seems technically complicated to aggregate already made orders into a single order for an OC, so my suggestion would be to TAKE IT SIMPLE and do 4 things:
1- Just consider that every order should be displayed separately so that user can reconcile and understand what was ordered where and why he has to go in this order to modify things, etc.
In cart dropdown:
In cart page:
2- I would move in cart page the “modify order” button on each order line and redirect directly to the relevant order so that it can be modified. (see cart page image above)
3- I would remove the possibility to delete items from previous orders, to avoid confusion and have a clear rule: modification is on the order page, that’s all. (see cart page image above)
4- If a modification is done on an existing order, I would trigger an email “Order modification” with content saying: order number #X has been modified, here is the updated content for that order (ideally in the same thread as first confirmation email…)
M (for the whole feature, the 4 points)
Previous discussions related
What do you think about that @sstead @danielle @Rachel @Kirsten @maikel ? If you are happy with it I’m happy to work as a PO, check with a dev that this solution is technically ok and get a quick estimate so that we can decide to prioritize or not. Then we can easily do the story map from there, it would clarify a lot the process.