Hello Square team,
We are a retailer using Square’s built-in Google Free Local Product Listings, configured through Square Dashboard. We have not built a custom application or Square API integration. Square Support directed us to this forum.
Could a human team member help route this to the team responsible for the native Google listings connector?
On September 5, 2026, Square showed the channel as Connected and inventory as Verified. Some product updates were reaching Google. However, Google Merchant Center’s API diagnostics, filtered to Last 7 days, showed:
productstatuses.get: notFound, 100% failure rate.accountstatuses.get: invalid_destination / destination, 100% failure rate.products.insert: quota/too_many_items, 1.9% failure rate.localinventory.insert: notFound, 16.2% failure rate.
These are Google API operations shown in Merchant Center, not requests from code we control. The percentages refer to API calls, not unique products.
The local-products source was populated, while an Online source was empty. We have not established duplication and have not removed any source. A sample product had matching price and availability in Square and Merchant Center.
There is also a separate Merchant Center policy restriction. We understand that it needs its own review; we are not requesting a bypass or assuming that these API errors caused it.
Could the connector team investigate:
- Whether status and inventory requests use the correct complete product identifiers, item variations, local/online channel, language and country/feed label.
- The destination values used in account-status requests.
- The effective product quota, including any parent/platform limit if applicable.
- The intended roles of the local and Online sources, and why the latter is empty.
- The connector’s Merchant API migration status. The operations were labeled Content API, but we observed no
410 Gone or content_api_sunset error, so we are not asserting that migration is the cause.
Please identify the responsible team and advise a private support channel for account IDs, screenshots and detailed diagnostics. We have omitted account/product IDs, contact details and business figures from this public post.
We want to preserve the existing catalog and working updates. Please do not disconnect/reconnect the integration, remove or recreate sources, or change products or account settings without our approval.
Thank you.
Hi, I’m sorry you are being bounced around! Your original request to square support is the correct channel since you are not using any APIs or building an app yourself. You can followup there and link this thread and this support article and they should be able to help out. Set up Google free and local product listings | Square Support Center - United States
My team unfortunately does not know much about this particular setup/support. If you get more pushback on the support side post back here and I’ll see what I can do!
Hi @zacstlouis, thank you for offering to help if we encountered further difficulty with Support.
We followed your September 8 guidance and replied to our original Square Support conversation with the link to your response and the support article you recommended. Today, September 16, Peggy from Square Customer Success replied that the escalation process had changed and again directed us to Developer Forums, explaining that developer inquiries are not supported by email. We are summarizing that reply here rather than posting the private email or account details.
We still use only Square’s built-in Google Free Local Product Listings, configured in Square Dashboard. We have no custom app or integration code to migrate. Both channels have now referred us to the other, and we still need the team responsible for this native connector.
There is also a current Google notice: Merchant Center says Content API support ended on August 18, with increased error rates starting September 1, and calls for migration to Merchant API. Google’s documentation, titled “Deprecation and sunset | Content API for Shopping”, states that ecommerce platform partners manage the migration for their merchants.
Our September 16 check of API diagnostics for September 9-15 still showed Content API calls. The product-status and product-insertion details examined showed notFound and quota/too_many_items, not 410 Gone or content_api_sunset. We are therefore not attributing those errors to the retirement without evidence.
Could you please help coordinate internally with the owner of Square’s native Google Listings connector so we can obtain:
- A responsible team and a private support route/case reference for the account-specific investigation.
- Confirmation of the connector’s Merchant API migration status and completion date; if it still uses Content API, whether its Google Cloud project has an approved extension and until when.
- Investigation of the original product-ID/channel, destination and quota errors, plus clarification of the local and empty Online sources, separately from the migration. When should we expect a technical update?
The separate Google policy restriction remains a separate issue; we are not requesting a bypass. Please preserve the existing catalog and working updates, with no disconnection/reconnection, source deletion/recreation or product/account changes without our approval.
Thank you for helping us reach the team that maintains this Square feature.
I’m sorry you’re getting a back and forth here. I’ll see if I can find the right channel and escalate internally! I appreciate your patience, I’ll update when I know more.
We shipped a change that isn’t directly linked to the case I opened for you, but looked to be the same resolution path. Can you verify if you are still having the same issue?