-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REQUEST] Bundle products QTY value #210
Comments
Second question would be: while importing the bundle product order back into magento, is the plugin so smart to actually decrease the stock levels of both simple products? |
I have proven this statement to be true by a test import. |
Hello @Kroellie appreciate you bringing up this concern. These product types currently feature only an |
I know this is an older thread, but I just wanted to mention we're in the exact same situation. |
We did the same, modifying Helper/Product.php to treat the lowest quantity of any of the child products as 'the stock' of the bundle product. |
@Kroellie @MaxiAxi-Jorn Thank you for reaching out and for your patience. We wanted to let you know that this issue is still on our backlog. While it hasn’t been prioritized yet, it remains on our radar, and we’ll provide updates as soon as there’s progress. |
Hi, we have your plugin to be used to upload our products to Amazon. Everything is working fine for simple products. Our bundle products however have a problem, because the QTY field is null for those and Amazon is rejecting the feed items. Our use-case is quite simple: we have a product, with an optional extra, so it would become a 'pro' product. Both items in this 'pro' bundle are separate, visible, simple products in our shop. Joined however, it is a 'new' product with its own EAN, price etc.
In my perception, the QTY value of the bundle product should reflect the least QTY value of any of the child products.
Or am I going about this all wrong, and should I fix this in Channable rules?
The text was updated successfully, but these errors were encountered: