Zapier Product Location Bug — Square Integration

Overview

A recurring bug has been observed where product location assignments in Square are silently switched for a subset of products. Square support has identified Zapier as the only mechanism capable of triggering this kind of change via the API. This article documents the pattern, diagnosis, and remediation steps based on the La Marie Beauty project experience.

Symptom

A batch of products (~12 in the observed case) have their Square location assignment switched without any deliberate action by the team.
The change is silent — no error is thrown and no notification is sent.
The affected products may need to be corrected manually; in some cases, items cannot be recovered and must be recreated.

Root Cause

Square support confirmed that Zapier is the only external mechanism that could trigger location changes of this kind via the API. The likely cause is a lingering Zapier integration that was not fully disabled when a prior team member (or prior project phase) concluded.

This pattern has appeared at least twice on the La Marie Beauty project:
1. Shortly after initial Square credentials were shared — all services were switched to the "Mequon" location.
2. A second occurrence affecting ~12 products, reported in December 2025.

In both cases, the team believed Zapier had been removed from the workflow, but an active Zap may have remained in a connected account.

Diagnosis Steps

Audit all Zapier accounts associated with the project — including accounts belonging to former team members or contractors. Do not assume a Zap is inactive just because it is no longer in active use.
Check Square's API activity logs (via Square's eCommerce/developer support) to identify which API key triggered the location change and when.
Request the original Square support email detailing the affected products and the suspected trigger — this provides a paper trail for further investigation.
Confirm whether WooCommerce→Square communication is direct (native plugin) or still routed through Zapier. If the WooCommerce Square plugin is in use, Zapier should not be needed for product sync.

Remediation

Disable or delete all Zaps in every account that has ever been connected to the project's Square or WooCommerce instances.
Manually correct the location assignment for affected products in Square. If a product can no longer be found, it may need to be recreated.
Rotate or revoke any Square API keys that were shared with former team members or third-party integrations no longer in use.
Document which Zapier accounts exist and their status (active/disabled) so future team transitions include an explicit offboarding checklist item for integration cleanup.

Prevention

When offboarding a team member or contractor who managed integrations, explicitly verify that all Zaps in their personal and workspace accounts are disabled or transferred.
Maintain a registry of all active third-party integrations (Zapier, webhooks, API keys) as part of the project's technical documentation.
Prefer direct plugin-to-plugin integrations (e.g., WooCommerce ↔ Square native plugin) over Zapier middleware where possible, to reduce the number of active integration surfaces.

^[1]
^[2]
^[3]
^[4]