PW Merchant API
PW Merchant API is a WooCommerce integration that allows merchants to connect their own Google Merchant Center account and manage product data directly from the WordPress administration panel. It creates a controlled connection between a WooCommerce store and Google Merchant Center through Google OAuth and the Google Merchant API.
The application is designed for merchants who want to manage their Google Merchant Center product operations without relying solely on manually prepared product feeds. After completing the Google authorization process, the merchant can select an accessible Merchant Center account, review WooCommerce product information, submit eligible products to Google, update previously submitted products, and view processing results returned by Google.
PW Merchant API does not connect to a Google account without the user’s knowledge. The Google connection begins only when the merchant explicitly selects the Google connection option from the plugin’s administration screen. The user is then redirected to Google’s official OAuth authorization interface, where Google displays the requested access and asks the user to approve or decline it.
Purpose of PW Merchant API
The primary purpose of PW Merchant API is to provide WooCommerce merchants with a practical way to manage product data sent to Google Merchant Center. WooCommerce stores may contain many products, variations, prices, images, availability values, brands, identifiers, descriptions, categories, and other attributes required for product listings.
Managing this information manually can become difficult as a store grows. Product information may also change frequently. Prices can be updated, products can become unavailable, new images can be added, and product descriptions or identifiers can be corrected. PW Merchant API helps the merchant submit and update this information through the WordPress administration panel.
The application does not guarantee that a product will be approved or displayed by Google. Google independently evaluates submitted products according to its technical requirements, policies, account settings, destination eligibility, and product data quality rules. PW Merchant API provides the technical integration and displays available processing information, but final approval and publication decisions remain under Google’s control.
How the Google connection works
A merchant starts the connection from the PW Merchant API administration screen in WordPress. The application redirects the user to Google’s OAuth authorization process. Google may ask the user to select an account, sign in, review the requested permission, and explicitly grant access.
After authorization, Google redirects the user through the registered callback address. PW Merchant API processes the authorization response and completes the connection. The plugin can then request a list of Google Merchant Center accounts that the authenticated user is permitted to access.
If more than one Merchant Center account is available, the merchant selects the appropriate account inside the plugin. PW Merchant API does not silently choose an unrelated Merchant Center account. The selected account becomes the destination for the product operations initiated by the merchant.
The user may disconnect the Google connection from the plugin when the connection is no longer required. The user can also manage or revoke application access through their Google Account settings.
How Google access is used
PW Merchant API uses the https://www.googleapis.com/auth/content scope to provide its user-facing Google Merchant Center integration features. This access is used to identify Merchant Center accounts available to the authenticated user, submit WooCommerce product information to the account selected by the user, update product data, and retrieve processing statuses or issues that Google makes available to the application.
Read access is necessary because the plugin must identify accessible Merchant Center accounts and display product or account information returned by Google. Write access is necessary because the user may request that WooCommerce product data be created or updated in the selected Merchant Center account.
A narrower scope is not sufficient for this workflow because the application needs both read and write capabilities to provide the product synchronization and Merchant Center management functions requested by the merchant. PW Merchant API does not request this access for unrelated purposes.
The requested access is used only after the user has initiated the Google connection and granted permission through Google’s authorization interface. The application does not obtain the user’s Google password. Google authentication is completed on Google’s own authorization pages.
Product submission and updates
PW Merchant API reads relevant product information from the merchant’s WooCommerce store. Depending on the product and store configuration, this information may include the product title, description, link, image link, availability, price, brand, product identifiers, condition, category information, and variation details.
The merchant can review product information and start an available submission or synchronization operation from the WordPress administration panel. The application sends the selected product information to the Merchant Center account chosen by the user.
When WooCommerce product data changes, the merchant can use the application’s available synchronization features to update the corresponding information in Google Merchant Center. This helps reduce inconsistencies between the store and the product information submitted to Google.
The plugin may also display synchronization progress and transaction information. Processing may not always be immediate because Google may require additional time to evaluate newly submitted or updated product information.
Product statuses and issues
Submitting a product does not mean that Google has approved it. Google may accept the request for processing and later return a status, warning, rejection, policy issue, missing attribute notice, or another processing result.
PW Merchant API retrieves available product processing information and displays it within the WordPress administration panel. This allows the merchant to review results without treating every submitted product as automatically approved.
When Google reports an issue, the merchant remains responsible for reviewing the product, store, website, Merchant Center account, and applicable Google policies. The application can display information made available through the API, but it cannot override Google’s decisions or remove policy requirements.
Possible product issues may relate to missing or inconsistent product data, invalid values, unavailable landing pages, image problems, account configuration, policy requirements, destination restrictions, or other conditions determined by Google.
User control and account selection
PW Merchant API is intended to act only on the Merchant Center account selected by the authenticated user. The merchant controls when the Google connection is initiated, which available Merchant Center account is selected, and when product submission or update operations are started.
The application does not use Google access to manage unrelated Google services. It does not use Merchant Center information to build advertising profiles or perform unrelated tracking. Access is limited to providing the integration features described on this page and requested through the plugin interface.
Merchants should connect only Google accounts and Merchant Center accounts that they are authorized to manage. If access permissions change or the connected Google account no longer has the required Merchant Center permissions, some plugin operations may stop working until the user reconnects with an appropriate account.
Google user data and privacy
Google user data obtained through the authorized scope is used only to provide the Merchant Center functionality explicitly requested by the user. This includes completing the Google connection, identifying accessible Merchant Center accounts, carrying out product operations initiated by the merchant, and displaying available processing statuses or issues.
Google user data is not sold. It is not used for unrelated advertising, and it is not shared with unrelated third parties. The application does not request access for purposes outside the operation of its Google Merchant Center integration.
Users can review additional information about data handling, user choices, and applicable practices in the PW Feed Privacy Policy. The use of PW Merchant API is also subject to the published Terms of Service.
Security and authorization
PW Merchant API uses Google OAuth so that users can grant access without providing their Google password directly to the plugin. Authentication and consent are handled through Google’s official authorization screens.
Users should review the permission displayed by Google before approving access. If a user does not agree with the requested permission, they can decline the authorization request. In that situation, features requiring Google Merchant Center access will not be available.
Authorization information must be handled securely, and users should protect access to their WordPress administration panel. Administrators should use strong passwords, maintain WordPress and WooCommerce updates, restrict administrator access, and follow appropriate website security practices.
Disconnecting the integration stops the plugin from using the active connection for new operations. Users may also revoke access from their Google Account permissions page when they no longer want the application to access their authorized Merchant Center information.
Who can use PW Merchant API
PW Merchant API is intended for merchants and authorized store administrators who operate a WooCommerce website and have access to a Google Merchant Center account. The user must have the appropriate permissions for the Merchant Center account they want to connect.
The plugin is not a replacement for a Google Merchant Center account. It does not create ownership rights for an account and cannot provide access to Merchant Center accounts that the authenticated Google user is not authorized to manage.
Before using the integration, merchants should ensure that their WooCommerce store contains accurate product information and that their website provides the public pages and business information required for their own operations and applicable Google policies.
What PW Merchant API does not do
PW Merchant API does not guarantee product approval, advertising performance, free listing eligibility, impressions, clicks, sales, or placement in Google services. These outcomes depend on Google’s systems, policies, account status, product data, website quality, competition, and other factors outside the application’s control.
The application does not bypass Google Merchant Center rules. It does not conceal product information from Google or attempt to override policy enforcement. Merchants remain responsible for the accuracy of their product data, their business information, their website, and their compliance with applicable laws and Google policies.
PW Merchant API also does not access a user’s Merchant Center account until the user completes the Google OAuth process and grants the requested permission.
Support and additional information
Users who need assistance with PW Merchant API can review the available documentation or contact the PW Feed support channel. Support requests should not include Google passwords, OAuth client secrets, access tokens, API keys, license keys, or other confidential credentials.
For information about data handling, review the Privacy Policy:
For the conditions governing use of the application, review the Terms of Service:
For product assistance, visit the Support page:
PW Merchant API provides a user-controlled connection between WooCommerce and Google Merchant Center. Its purpose is to help authorized merchants submit and update product information, monitor available processing results, and manage the connection from within WordPress while keeping the Google authorization process transparent and under the user’s control.
