New Update (2.0.1) – Cant edit product quantities

Hi @austriker27,

Do you mean ability to select a quantity on the product page(frontend) or change the quantity as an admin in the backend?

Is this still broken if you try with only WooCommerce, the Square plugin, and a default theme(Storefront, Twenty Nineteen)?

I tested both scenarios(frontend and backend) and didn’t see any issues myself.

@austriker27,

What do you have for the Product system of record setting within the WooCommerce->Settings->Square settings page?

If you have Square set for that option, any products that are synced with Square will have their stock quantity field disabled with a note that says, “synced with Square”.

This is because you’ve indicated that you want Square to be the “source of truth” for your inventory.

If you manage inventory through WooCommerce that setting should probably be WooCommerce.

I’m having the exact same problem as Austin. The system of record is showing WooCommerce. When the viewing quantities of products in Woocommerce, the text field is greyed out with the text Fetch stock with Square. When I check on Square’s side, current stock is also greyed out. Thankfully most of the quantities are correct, but for items that are incorrect with low stock, I’ve had to disable them.

I’ve tried disconnecting WooCommerce from Square and then reactivating it again, and got the same result.

Hopefully a fix can be found quickly…

I am having the same issue. I have set WooCommerce as the system of record yet on the Product Data tab I cannot change the “Manage Stock” check box nor can I edit “Stock quantity”.
This is a huge problem.
In the mean time how do I revert back to a previous version.
—- edit—
I have reverted back to 1.0.38.
More info the above happened to Product Bundles where the individual component stock status is tracked. – not at the bundle level.

• This reply was modified 5 years, 7 months ago by ntraines.

Hi guys!

We have taken note of this issue along with a few others, and are rolling back to 1.0.38 while we investigate this. Please roll back to 1.0.38 at this time, and when we are good to go with 2.0.1 we will let you know!

Very sorry about all of this, and thank you for all the feedback!

Thanks nixiack8! I really liked the new features added that did work; hope to see V2 back soon.

I’ll close this since the rollback should have resolved these issues. Let us know if you are still having problems after reinstalling and reconnecting 1.0.38.

I’m having this same problem, but I’ve read that others are also having problems with 1.0.38. Is the solution to still rollback to that version? And if so, where I can find that version?

I

• This reply was modified 5 years, 3 months ago by princealexi.