Carts Vs. Orders
ryanthompson - 1 week ago
I want to open an ecom discussion about the data structure and design around a cart and an order.
Currently the carts are their own namespace/streams. With items / adjustments / etc. The question is:
Should the cart build up cart items or should it build up an order in "cart" mode.
Couple things to consider is abandoned carts, cross over data (carts need far less information than an order). Carts are currently multi-instance so the cart can be saved as a wishlist for example (if desired).
However it means carrying a cart around and then upon checkout - spinning up an order. Or perhaps the order isn't spun up until the checkout is completed? We also have a checkout stream that helps build an order but idk if it's necessary. Perhaps at THAT point we'll start building an order object.
My personal opinion is such that we should keep carts separate from orders.. thoughts?
And I am keen to hear thoughts on the checkout process as far as where that data goes. Does a checkout start (after clicking checkout) start an order or should we use a checkout carrier object?
Let's hear it!