Merchant label pilot

Before your session

• Use the agreed workspace and selected Merchant connection. The connection owner must authorize Google with the content scope and have the required Merchant access. Workspace, member, and connector permissions must allow writes.
• An operator checks the exact connection and the existing, exclusively managed supplemental source, linked to the intended primary source. Before enrollment, the operator must attest that our input is empty. The source is reserved for the agreed single-label input. A matching label value or visible tool name does not prove enrollment.
• Use the production connector in Claude Desktop with current workspace-bound Ad Superpowers authorization. This is separate from your Google connection. Confirm the workspace and Merchant account with reads before a preview.
• Reserve about 30 minutes with support. The operator checks for at least 45 minutes of actual remaining Google authorization before starting. Processing can take longer; this is a session estimate, not a guarantee.

No prices, stock, titles, other labels, primary feeds, feed rules, general disapproval fixes, or batches. Ordinary plan limits apply to successful tool calls, including previews and processing checks. Enrollment applies to the account in this workspace; other members with write access to it can also use the pilot, under the connection owner's Google identity. Support reviews that access with the owner before enabling it.

Preview, confirm, and check processing

1. Ask for merchant_prepare_writes on the agreed account and product, with a non-empty custom_label_4 value different from the current value. The preview does not write to Google.
2. Read the full preview: account, product, current and proposed label, source, and expiry. If correct, return that exact confirmation token yourself in a new message. The assistant must wait for your message.
3. Your assistant calls merchant_update_product once with the token. Accepted or pending does not mean Google has processed the change.
4. Use separate merchant_query calls with entity_type="label_operation". Wait for processed, the expected observed label, and other_attributes_match=true. While pending, only read status.

Previews expire after 30 minutes; a new preview replaces the previous one for that user and account. An expired or changed preview needs a fresh preview and your new confirmation before an otherwise permitted attempt. Keep tokens private. A confirmation is not reusable approval for another value, product, or revert. Status checks do not write to Google, but can update our record of the latest processing state.

Remove our label input

1. After processing is verified, request a new merchant_prepare_writes preview with revert=true. It proposes deleting only our own supplemental single-label input.
2. Review that separate preview and return its new token yourself. The earlier apply confirmation does not authorize revert.
3. Your assistant calls merchant_revert_product once. Read label_operation until reverted, then verify the observed fallback and unchanged other attributes.

Revert lets the current fallback supply the label. It does not restore every product field. If processing cannot be distinguished from the existing label value, the result stays pending. The empty supplemental source and its link remain; removing those needs separate coordination. Workspace activity records accepted attempts. The latest operation status records processing. Acceptance alone is not proof of completion.

When Google authorization expires

This pilot currently needs guided reauthorization. Automatic account-token renewal does not renew the authorization used by the label flow. Pause attempts and status checks during reconnect. The existing connection owner must use the normal Merchant connection route in the dashboard, in the same workspace and with the same Google identity. Another team member must not substitute their Google login. Complete reconnect and account selection just before the agreed session so the operator can verify the required 45 minutes of remaining validity.

Support compares the connection, authorization, selection, and complete operation record before and after. Any binding change means stop. Do not disconnect, replace credentials, or reset the operation to make it fit. Successful reconnect permits only the next action allowed by the current state: pending still allows reads only, and UNKNOWN stays closed.

Stop and contact support

Stop on UNKNOWN, a timeout or uncertain write outcome, changed source ownership, or unexpected changes to other attributes. Do not retry, reset, take over, or delete manually. A later matching label does not resolve an unknown write. Paused-default workspace mode refuses this flow, including revert; do not change the mode to bypass a refusal.

Contact support through the dashboard with the operation ID if returned, time, phase, and error category in a private channel. Do not post tokens, credentials, or product data publicly. Support investigates with reads first. Any further write needs a separate concrete decision. Rolling back application code does not remove a label already sent to Google. If no operation ID was returned or status reads are unavailable, support can locate the operation record privately using the workspace and time.