I'm seeing some very strange behaviour in the bulk order form's quantity selector for products that have minimum quantities and quantity steps (in this case, 6).
In the video, I'm using the 'Cream' Order Form Theme, styled with some custom CSS, but I've tested Classic and Indigo, and also with default themes like Blocksy and Twenty Twenty-Five, and the issue persists.
This looks like it could be a conflict with another plugin or something else on the site that's affecting the min/max/step values on the quantity input. My guess is that something is overriding or setting unexpected values (like max=-1 or similar).
Could you try right-clicking on one of the quantity fields that has the issue and selecting "Inspect" to check the actual HTML? Specifically, look at the `min`, `max`, and `step` attributes on the input element - I'm guessing something there won't look right and that should help us narrow down the cause.
Also, could you share a link to that page so I can test it directly? Even better, if you can share admin access to the site (or a staging clone), I can investigate in more detail.
The max="38" is pulled from the quantity in stock for the specific variation. There's no max quantity actually set. One thing I have noticed, is that the lower the stock, the more likely the bug is to happen.
I've tested with all plugins deactivated except WooCommerce and B2BKing, and it still happens. I've also tested with Blocksy and Twenty Twenty-Five themes.
I'll set you up an admin account on our site and send you the details privately.
I also tried various things like switching groups and even temporarily setting a variation (Ipanema Yellow) to stock qty 24, same as in your video with the issue, but still not seeing it on my end: https://www.loom.com/share/52b47bc9719e4011a77c45c05c208dac
Very strange. Could you try this please when you see the issue:
1. Go to Breeze -> Purge All Cache (to clear any cached scripts)
2. Do a hard refresh on the page with CTRL + Shift + R (or Cmd + Shift + R on Mac)
I'm thinking this might be a cached script issue - perhaps an old value got stuck in the cache somewhere.
3. Have you tried doing this with a different browser or in incognito mode?
I tried all those things, and the problem persisted, but it seems the issue is limited to my own admin account. I tried using my non-admin account and the errors didn't happen. I created a new admin account to see if it was only happening on admin accounts, and that was also fine.
I think we're safe for now. I did try deleting my main admin account to recreate it and see if that clears the issue, but that deleted all the pages etc that I'd created! Currently recovering from a backup, and I won't make that mistake again.
Thanks for the update. Let's keep an eye on it for now - hopefully that's the end of it.
If you do notice the issue popping up again, one thing I'd want to look into is the object cache. It's possible there's a cached value somewhere for the min/max/step that's getting stuck for that account, though I'm just speculating at this point.
The issue came back, with a non-admin account, when I was testing building a large order.
I think I've found the cause. The products that had the issue had 'Show Tiered Pricing Table' and 'Sum Up Variations' selected, even though they don't have tired prices. Unchecking those seemed to fix the issue.
If it does come back, the most helpful thing would be knowing which account and product/situation triggers it, so I can reproduce it on my end and troubleshoot properly. Without being able to catch it in action, it's tricky to pin down.
My suspicion is it could also be caching-related (e.g. a stale value getting served for a specific account), but that's hard to confirm without seeing it happen live.
Hi.
I'm seeing some very strange behaviour in the bulk order form's quantity selector for products that have minimum quantities and quantity steps (in this case, 6).
See video here: https://www.dropbox.com/scl/fi/9x1rta67c16a3mett0eqg/Screen-Recording-2026-02-25-at-09.45.30.mov?rlkey=sw1mdep15z3salj2vaz9en7bh&st=ewmujz6t&dl=0
In the video, I'm using the 'Cream' Order Form Theme, styled with some custom CSS, but I've tested Classic and Indigo, and also with default themes like Blocksy and Twenty Twenty-Five, and the issue persists.
Any ideas?
Hi Danny,
Thanks for reaching out,
This looks like it could be a conflict with another plugin or something else on the site that's affecting the min/max/step values on the quantity input. My guess is that something is overriding or setting unexpected values (like max=-1 or similar).
Could you try right-clicking on one of the quantity fields that has the issue and selecting "Inspect" to check the actual HTML? Specifically, look at the `min`, `max`, and `step` attributes on the input element - I'm guessing something there won't look right and that should help us narrow down the cause.
Also, could you share a link to that page so I can test it directly? Even better, if you can share admin access to the site (or a staging clone), I can investigate in more detail.
Kind regards,
Stefan
Hi Stefan.
Thanks for the response.
Here's the entire div html from the frontend:
<div class="b2bking_cream_input_group">
<button type="button" class="b2bking_cream_input_minus_button b2bking_cream_input_button">-</button>
<input type="number" min="6" max="38" class="b2bking_bulkorder_form_container_content_line_qty b2bking_bulkorder_form_container_content_line_qty_indigo b2bking_bulkorder_form_container_content_line_qty_cream" step="6" value="6">
<button type="button" class="b2bking_cream_input_plus_button b2bking_cream_input_button">+</button>
</div>
The max="38" is pulled from the quantity in stock for the specific variation. There's no max quantity actually set. One thing I have noticed, is that the lower the stock, the more likely the bug is to happen.
I've tested with all plugins deactivated except WooCommerce and B2BKing, and it still happens. I've also tested with Blocksy and Twenty Twenty-Five themes.
I'll set you up an admin account on our site and send you the details privately.
Hi Danny,
Thanks for the detailed info,
Yes, it would be great if we could troubleshoot directly - please use [email protected] for the account.
Kind regards,
Stefan
Hi Danny,
Thanks for the follow-up on this. I've been trying to reproduce the issue on my end but haven't been able to so far, which is a bit puzzling.
I tried both the order builder and the product page as you described, using the plus and minus buttons on variations with stock between 6-30, but I can't get it to happen: https://www.loom.com/share/eb8b3c6028a74b678a7af1b089df7706
I also tried various things like switching groups and even temporarily setting a variation (Ipanema Yellow) to stock qty 24, same as in your video with the issue, but still not seeing it on my end: https://www.loom.com/share/52b47bc9719e4011a77c45c05c208dac
Very strange. Could you try this please when you see the issue:
1. Go to Breeze -> Purge All Cache (to clear any cached scripts)
2. Do a hard refresh on the page with CTRL + Shift + R (or Cmd + Shift + R on Mac)
I'm thinking this might be a cached script issue - perhaps an old value got stuck in the cache somewhere.
3. Have you tried doing this with a different browser or in incognito mode?
Kind regards,
Stefan
Hi Stefan.
I tried all those things, and the problem persisted, but it seems the issue is limited to my own admin account. I tried using my non-admin account and the errors didn't happen. I created a new admin account to see if it was only happening on admin accounts, and that was also fine.
I think we're safe for now. I did try deleting my main admin account to recreate it and see if that clears the issue, but that deleted all the pages etc that I'd created! Currently recovering from a backup, and I won't make that mistake again.
Hi Danny,
Thanks for the update. Let's keep an eye on it for now - hopefully that's the end of it.
If you do notice the issue popping up again, one thing I'd want to look into is the object cache. It's possible there's a cached value somewhere for the min/max/step that's getting stuck for that account, though I'm just speculating at this point.
Kind regards,
Stefan
Hi Stefan.
The issue came back, with a non-admin account, when I was testing building a large order.
I think I've found the cause. The products that had the issue had 'Show Tiered Pricing Table' and 'Sum Up Variations' selected, even though they don't have tired prices. Unchecking those seemed to fix the issue.
I'll get back to you if it happens again.
Hi Danny,
Thank you for the update,
If it does come back, the most helpful thing would be knowing which account and product/situation triggers it, so I can reproduce it on my end and troubleshoot properly. Without being able to catch it in action, it's tricky to pin down.
My suspicion is it could also be caching-related (e.g. a stale value getting served for a specific account), but that's hard to confirm without seeing it happen live.
Kind regards,
Stefan