so I have 10 products, they are all clones of product #1, but I decide to change pricing, description or other attributes of the variants on product 2, I want to have a reference back to product 1 (parentId) so that I can reset the altered variants attributes back to the original product’s attributes, and maintain that kind of relationship all the way down (clone product 2, alter product 3’s variant attributes, I should be able to override all the way down the chain starting at product 1, or product 2.
maybe nesting them would make sense if they were truly “options”, but there are other use cases, think “bundled” products -> where a product is comprised of multiple variants -> not just one, or configurable products like a computer (Hdd, ram, screen).
actually a variant doesn’t have an option
you only check out with a variant, the variant is the product
so when you stock inventory, you don’t stock an “option”, you stock a “Sku"
maybe I shouldn’t have called that field a “parentID”, but really all it does is indicate the hierachy -> if you removed the “parentId” -> it would just “move up a level” visually, but the functionality is the same
now-> all that said… @aldeed and I have discussed a couple times if variants should really be their own collection, or if we even need the product “wrapper"
ie, we could move descriptions,etc into the variants as well… and just have the “product” be a array of variants.. there might be some ways to rethink that...
so in the grid you see multiple different “Brooks"
but those are actually “variants"
because if you look at the product detail page
they are the same products that are in the grid
when you choose options
so, that would be simple functionality to add to our product grid, instead of just showing the “product" (which uses the first variant for details, pricing) - we could show all variants, or just the most popular variants (which is what zappos does)
and we already do this, but each variant gets its own url as well
and yes -> that’s why I kept the descriptions in the “wrapper”, but at some point, I think we’ll add them to variants as well,and just cascade from the wrapper if the field is empty
@evliu -> all this said -> I do want to add the ability to add additional depth (and maybe that would be where we do actually embed another array of variants within the variant), as well as “add ons” and “related/upsells"
GridFS parses everything down into small chunks, so actually not that bad -> but yeah -> when we had the videos we were using ink file picker. (which is great), but I’d probably setup the S3 module for video storage
much of the order workflow is still under-development - you can place an order, etc but the order management screens are very rudimentary - so you’d either need to work on enhancing those, or write your own screens to manage refunds
I’ve got them on the roadmap though
and of course, you’d want to hook that into the payment methods as well
@aaronjudd After populating the orders collection with the data from /private/Orders.json, it displays the red circle with a 9 in it. The orders dashboard app doesn't have new data. (0 pending, processed, etc.) Is there something I'm missing?