I keep having issues with commited inventory since its launch, every so often something gets stuck. I report it here and someone eventually syncs my inventory or I duplicate the item and delete it and create a new one which is not ideal as i lose sales history.
Normally they are associated with invoices that have been cancelled. However I see one here that is assigned to an open cart that I do not have.
Please advise if I am missing a simple fix on this one but I can't find an open cart for this
Thank you for your response. While I appreciate the follow-up, I’m disappointed by the suggestion to disable the committed stock feature rather than investigate the underlying issue. This feature is an integral part of Square’s inventory management system, and I rely on it to streamline my operations.
I’ll follow up by opening a support ticket with Customer Success as recommended, but I’d hoped for a more proactive approach given that this seems to be a recurring issue. I trust that Square values its customers enough to address this matter thoroughly rather than suggesting workarounds that undermine the system's intended functionality.
I look forward to hearing from the team with more insights.
I have emailed support:
For your reference this is Case #: 101447531
Dear Square Support Team,
I am writing to report a recurring issue with the committed inventory feature that has been causing disruptions in my operations since its launch.
Every so often, inventory items become "stuck" in the committed status, preventing me from managing them effectively. In the past, I have either relied on support to sync my inventory manually or resorted to duplicating and recreating the affected items to work around the issue. However, this workaround is far from ideal as it results in the loss of valuable sales history, which is crucial for my business.
Typically, I’ve noticed this issue occurs with items associated with cancelled invoices. However, in this instance, I see an item stuck in committed inventory status that appears to be tied to an open cart—one that I do not have in my system.
I’d appreciate your guidance on resolving this issue. Am I overlooking a simple fix, or is this indicative of a deeper issue within the system? I’m looking for a permanent resolution to this recurring problem as it continues to add unnecessary complexity to my inventory management process.
I look forward to your assistance and any insight you can provide. Please let me know if you require further details from my end.
@isabelle @maxpete @Summer2024
Still no resolution to this matter, tomorrow I will again duplicate an item and delete the orginal to resolve a issue with square getting stuck.
This is just like my promo items getting stuck that I reported a few weeks ago here: https://www.sellercommunity.com/t5/Square-Online-Discussion/BUG-Timed-sales-are-still-showing-as-fil...
Which is again happening as seen here:
How do i get some real investigation into what is a recurring issue on my account of things getting "stuck"
There are items on my website currently affected by the sale glitch. For a quick example you can just go to this url and see all my items from black friday that are still listed as "on sale" as seen in the url that have no promo attached to them: https://www.jtpets.ca/s/shop?page=1&limit=60&sort_by=name&sort_order=asc&item_deals=on_sale
Alcott Adventure Collar - Pink
CAD$13.49 - CAD$15.49
Alcott Adventure Visibility Leash - Orange
CAD$18.49 - CAD$21.99
I appreiciate the attention to detail and to understand the situation, I do not always articulate myself well.
These items were on promo for black friday as a timed special from X date to Y date
The promo ended
When searching the site for items marked "on sale" these are showing up as still having a sale attached to them, but the promo is over, and also deleted from the discounts section of the page.
This is the second time in a short period of time that i ran a timed promo and the items did not all remove themself from the sale site filter afterward.
This is an issue over an above the "open check" error that this thread started as.
