I understand how to programmatically create a product, as well as add to the basket. I know that this may seem silly, but you can create the product on the fly and add it to the cart / quote, but not really save it in the database.
We want to create a custom interface, and I thought that in the end he could add a package product with all the choices, but this package product would not actually exist in the backend.
I realized that while you can make sure that the quote and order have what it needs, from the point of view of the product, it would be good, but it’s obvious that there is probably a lot that is connected with finding material in db on a specific sku or ID. I know that if you uninstall the product, and then look at the order in the administrator that causes the problems, at least that was for this one scenario that I was dealing with.
I was thinking of creating a giant product with a package that had as many as 6 different items in the set, and each item could have about 500 products, and then, based on what the user selects, I programmatically add the package to the cart. But then I was not sure whether there would be a negative impact on the availability of such a giant bundle product.
UPDATE:
I don’t think this will work, it is obvious that the database has a lot of information related to the product, and we set up the test, and immediately get an error for $ item-> getProduct (). We are moving forward by creating a gigantic batch product, as well as a common product with the addition of user options on the fly, as Anda pointed out below. Any other suggestions would be much appreciated.
source
share