Order Processing - handling multiple orders through the checkout flow

[reduxdj]

Is there a plan to support this use-case?

[aaronjudd]

Can you give a use case to describe the functionality you are looking for?

[reduxdj]

OK, the use-case is that we manage multiple brands (or vendors) products. We are looking for the ability to have a parent order that contains child orders, and each child order can support multiple products from that brand/vendor. When we determine shipping we need to determine for each brand/vendor as well. This is kind of the most basic requirement for e-comm needs.

Thanks.

[aaronjudd]

Ok, yes - the underlying architecture and data schema is designed to handle this kind of "drop shipping / multiple vendor / multiple shipping" scenario. This was a core scenario (and actually where I came from design wise). We've not spent a lot of time on the order fulfillment UI -> so it's not ready for this yet, but will absolutely be part of it. The goal would be to handle fulfillment for individual products/variants separately, and not as a complete order (though the overall order wouldn't be completed until all items had shipped).

[boboci9]

Hi all,
I was considering and prototyping out a second solution for multi vendor solutions, one where there is a parent order created from multiple shops and in the same time several suborders for the individual shops containing only the items from their shops, and the shipping selected for their shop, this way each seller can view their orders having access only to the suborders (which have the same schema in the same collection only an additional field parentOrderId is set, while the parent order has a flag suborders true). There would be a super admin which would have access to the parent orders containing data form multiple shops while each shops admin having access to only their data.
This way the multi vendor setting could flawlessly work together with the current reaction core version. What do you think?

[aaronjudd]

In #287 I was thinking that you'd need to be able to give the user, in the checkout flow, the functionality to edit qty, group shipping methods, edit shipping , etc in a more detailed checkout review stage. This would be easier if the cart document was intact during checkout. But I can see a lot of advantages to breaking the order up like this when we copyCartToOrder, but I'd probably create the "suborders" as subdocuments of the order, rather than a copy, to maintain the order integrity. Is that what you're doing? Gladly take a pr.

[boboci9]

Righ now I keep the original order untouched so that it contains all the information and I have the suborders as standalone orders just to be sure that every seller will have access only to those orders which have their shopId, while the super admin of the main shop would have access to all orders. Do you consider any drawbacks for having these suborders as standalone documents?

[aaronjudd]

Closing for #798